Home Man
Search
Today's Posts
Register

HP-UX (Hewlett Packard UniX) is Hewlett-Packard's proprietary implementation of the Unix operating system, based on System V.

Error when starting apache

Tags
hp-ux

Login to Reply

 
Thread Tools Search this Thread
# 8  
Old 09-05-2016
tcp 0 0 10.61.1.121.80 192.168.11.41.37274 CLOSE_WAIT
# 9  
Old 09-05-2016
Quote:
Originally Posted by anaigini45
tcp 0 0 10.61.1.121.80 192.168.11.41.37274 CLOSE_WAIT
That is NOT a process ID, it is the port number. "192.168.11.41.37274" is a "socket": a certain port on a certain IP address.

When we talk about "TCP connections" we are talking about something you can picture like a garden hose, where, instead of water, data can be pumped through (in both directions). This is also called a "virtual channel". The "sockets" are the end points at the two connecting systems where this garden hose is attached. In this case you have two systems connected: 10.61.1.121 and 192.168.11.41. The "garden hose" connects port 80 on the first system to port 37274 on the second.

You really should read the suggested book (or another, but i found this one to be the best to learn from) to understand basic networking concepts.

I hope this helps.

bakunin
The Following User Says Thank You to bakunin For This Useful Post:
RavinderSingh13 (09-05-2016)
# 10  
Old 09-05-2016
Finally, the solution for this was to kill the 2 httpd processes listed from the lsof command :
Code:
# /usr/local/bin/lsof -i ":80" | grep "LISTEN"
top     13106  www    3u  IPv6 0xe00000038137cac0      0t0  TCP *:http (LISTEN)
top     13179  www    3u  IPv6 0xe00000038137cac0      0t0  TCP *:http (LISTEN)
#

After killing these 2 processes, all the CLOSE_WAIT connections were gone.
Then, I could restart the apache process once again.
# 11  
Old 09-05-2016
Also check that
Code:
ndd -h tcp_time_wait_interval

is 1 minute (60000 miliseconds), not 4 or 10 minutes.
Still this can mean that when you stop a service like apache you must wait 1 minute until you can start it again.
# 12  
Old 09-05-2016
Quote:
Originally Posted by anaigini45
Finally, the solution for this was to kill the 2 httpd processes
[...]
After killing these 2 processes, all the CLOSE_WAIT connections were gone.
Then, I could restart the apache process once again.
This was exactly what i have told you in first place: the apache processes are named "httpd", not "apache".

bakunin
Login to Reply

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

More UNIX and Linux Forum Topics You Might Find Helpful
Thread Thread Starter Forum Replies Last Post
How to grep a line not starting with # from a file (there are two lines starting with # and normal)? Tanu UNIX for Dummies Questions & Answers 3 05-31-2016 04:33 PM
Error while starting Apache after compiling PHP and Curl sunnysthakur Red Hat 1 12-03-2013 09:47 AM
Starting an Apache Server bssandeshbs UNIX for Advanced & Expert Users 4 11-21-2009 01:00 PM
Problems starting Apache 2.0.54 mojoman Web Programming 1 01-14-2009 08:49 PM
Error about SSLProtocol when starting Apache moe2266 UNIX for Dummies Questions & Answers 3 11-03-2007 03:25 AM
error while starting SSH on AIX kmalla AIX 4 09-15-2006 11:07 AM
Problems starting apache 1.3 with mysql godspunk32 Solaris 1 08-25-2006 09:56 AM
starting with APR (Apache Portable Runtime) sumsin Programming 0 01-12-2006 07:29 AM
Starting Apache cstovall UNIX for Dummies Questions & Answers 4 12-04-2002 09:18 AM
starting Apache on Solaris 8 jskillet UNIX for Dummies Questions & Answers 5 07-20-2001 10:06 AM


All times are GMT -4. The time now is 03:20 PM.

Unix & Linux Forums Content Copyright©1993-2018. All Rights Reserved.
UNIX.COM Login
Username:
Password:  
Show Password