Throttling respawn due to port 9010

Question

Level 1

63 points

Throttling respawn due to port 9010

Hello All,

I am getting the following error every ten seconds on one of my web servers:
2/3/09 10:28:02 AM (48)Address already in use: make_sock: could not bind to address 127.0.0.1:9010
2/3/09 10:28:02 AM no listening sockets available, shutting down
2/3/09 10:28:02 AM Unable to open logs
2/3/09 10:28:02 AM (org.apache.httpd[46421]) Exited with exit code: 1
2/3/09 10:28:02 AM (org.apache.httpd) Throttling respawn: Will start in 10 seconds

In my httpd.conf file I have this:
#ServerName www.example.com
Listen 127.0.0.1:9010
DocumentRoot "/var/empty"
ErrorLog "/var/log/apache2/error_log"
<Directory "/var/empty">
Order Deny,Allow
Deny from All
</Directory>

Can I just comment this line??:
Listen 127.0.0.1:9010

Or would this cause problems with writing to the error_log?

Support all Mac machines, Mac OS X (10.5.5)

Posted on Feb 3, 2009 9:00 AM

Reply

Answer 1

Camelot

Level 9

58,527 points

Feb 3, 2009 10:16 AM in response to spraguga

The problem is likely bigger than that.

Your apache can't start up because some other process is listening to a port that it's trying to use.

One approach may be to not have Apache use that port, but a better solution would be to work out what process is using that port because it's certainly non-standard.

The easiest way to do this is via the command-line utility lsof:

sudo lsof -i :9010

This will identify any process that's using port 9010 on your system. You should identify what that is and decide whether it is appropriate or not.

Note that in many cases you may find that it's another copy of apache that's listening to that port - maybe one that didn't shut down cleanly, for example. That's why it's better to find out what is using that port rather than to just ignore the issue.

Reply

Answer 2

spraguga Author

Level 1

63 points

Feb 3, 2009 1:55 PM in response to Camelot

Apache on port 80 is up and running fine.

_www user is using the port in multiple processes. But when I go to kill them a new one is automatically created.

servermgr 48009 root 14u IPv4 0x13a0166c 0t0 TCP localhost:54359->localhost:9010 (CLOSE_WAIT)
httpd 54711 _www 3u IPv4 0x28b7ee64 0t0 TCP localhost:9010 (LISTEN)
httpd 54719 _www 3u IPv4 0x28b7ee64 0t0 TCP localhost:9010 (LISTEN)
httpd 61331 root 3u IPv4 0x28b7ee64 0t0 TCP localhost:9010 (LISTEN)

Reply

Answer 3

Camelot

Level 9

58,527 points

Feb 3, 2009 5:59 PM in response to spraguga

_www user is using the port in multiple processes. But when I go to kill them a new one is automatically created.

That's perfectly normal - Apache will spawn child processes to handle connections.

Therefore your issue seems to be a copy of Apache that's already running, preventing your new instance from running.

Reply

Answer 4

spraguga Author

Level 1

63 points

Feb 4, 2009 8:20 AM in response to Camelot

I had to restart the server and all is normal again.

Can no one tell me why this line is in my httpd.conf file, does anyone else have this as well?:
Listen 127.0.0.1:9010

Thanks!

Reply

Answer 5

Camelot

Level 9

58,527 points

Feb 4, 2009 4:46 PM in response to spraguga

Can no one tell me why this line is in my httpd.conf file, does anyone else have this as well?:
Listen 127.0.0.1:9010

I didn't realize that was your question.

Apache listening to 9010 is normal - it's setup that way so you can query the server status via a browser.

http://localhost:9010/server-status

Reply