- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Apache Connection problem in HP-UX11.0 N-class
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 01:31 AM
01-17-2002 01:31 AM
Apache Connection problem in HP-UX11.0 N-class
We are installing Oracle 9iAS, installed successfully , started the Apache webserver but not able to connect to the server through browser , when I check the error log it shows the following error,
[Thu Jan 17 13:34:53 2002] [error] (9)Bad file number: accept: (client socket)
[Thu Jan 17 13:34:54 2002] [error] (9)Bad file number: accept: (client socket)
please help i need it urgently.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 01:42 AM
01-17-2002 01:42 AM
Re: Apache Connection problem in HP-UX11.0 N-class
Could be a problem with permissions of the directory that your process is trying to access. You may like to check the permissions of your directories. Resolving it can be a matter of chmod'ing or chown'ing.
Hope this helps. Regards.
Steven Sim Kok Leong
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 01:48 AM
01-17-2002 01:48 AM
Re: Apache Connection problem in HP-UX11.0 N-class
Steve, thanks for the quick response, my server is NIS cluster (MC service Guard). and I'm able to connect to Apache web when i run in first node, when serever fail over to second I could not connect, its giving this error. Pls help.
thanks
SVTGanesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 01:51 AM
01-17-2002 01:51 AM
Re: Apache Connection problem in HP-UX11.0 N-class
It appears that your apache daemon was not started up successfully. The "bad file number" on closer look appears to relate to a failed connection to the socket. To verify, are you able to connect to the socket:
# telnet localhost 80
If not, check your MC/ServiceGuard package log for errors ie. /etc/cmcluster/pkg_name/pkg_name.log
Hope this helps. Regards.
Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 02:06 AM
01-17-2002 02:06 AM
Re: Apache Connection problem in HP-UX11.0 N-class
The Service startup was failed through package
but we have started manualy the server. after starting , I can see the message httpd started after that when I access the page its giving this error mesg.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 02:17 AM
01-17-2002 02:17 AM
Re: Apache Connection problem in HP-UX11.0 N-class
Which user did you use to startup the HTTPD process? Is it the usual apache or nobody or is it root?
What is the ownership and permissions of the DocumentRoot and DocumentRoot/index.html?
Hope this helps. Regards.
Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 02:24 AM
01-17-2002 02:24 AM
Re: Apache Connection problem in HP-UX11.0 N-class
The application installed in shared disk, and running fine in first node, when failed over
to second node with same disk I'm getting this error, I'm using apache1 to start and its belongs to same group of apache owner.
thanks
SVTGanesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 03:03 AM
01-17-2002 03:03 AM
Re: Apache Connection problem in HP-UX11.0 N-class
Which version of apache are you using. Some versions have related bugs such as Apache 1.3.12 on HP-UX 11.X.
Below bug report will help. It has the exact error message you got:
http://bugs.apache.org/index.cgi/full/7179
Hope this helps. Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 06:43 PM
01-17-2002 06:43 PM
Re: Apache Connection problem in HP-UX11.0 N-class
I refered the link but, could not find the solution since its not given any patch number or cause of the error. I checked in my server there some mismatch with patch sets,
Note: We have installed HP-UX QPK sep2001 release patches last week, is any isssues with this patch??
thanks
SVTGanehs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-17-2002 07:39 PM
01-17-2002 07:39 PM
Re: Apache Connection problem in HP-UX11.0 N-class
salvo.ciccia@st.com
This was the guy who posted the bug report. After all this while, he might already have it resolved and he might still remember the steps he took to resolve it.
How about emailing him for help? If not, try emailing apache for help. Afterall, since they received the bug report, they must have fedback a solution or workaround.
Hope this helps. Regards.