Problem running httpd service - lhr14s20-in-f7 already has port

DaFoot · #1 27th January 2013, 12:08 AM

I'm trying to run up the httpd service as I used to but it is failing with an error about the address/port already being used.

I tried lsof to see if/what was holding the port, which may be incorrect but having a go:

[root@bigfoot rc5.d]# lsof -P -i4 | grep :80
chrome 1681 dafoot 180u IPv4 1113057 0t0 TCP bigfoot:47220->m563-mp1-cvx1b.lan.ntl.com:80 (ESTABLISHED)
chrome 1681 dafoot 231u IPv4 1439467 0t0 TCP bigfoot:53860->lhr14s20-in-f4.1e100.net:80 (ESTABLISHED)
chrome 1681 dafoot 295u IPv4 1615106 0t0 TCP bigfoot:54269->m560-mp1-cvx1b.lan.ntl.com:80 (ESTABLISHED)
banshee 16850 dafoot 20u IPv4 1183375 0t0 TCP bigfoot:55309->178.236.6.251:80 (CLOSE_WAIT)
banshee 16850 dafoot 23u IPv4 1163682 0t0 TCP localhost.localdomain:8089 (LISTEN)
banshee 16850 dafoot 35u IPv4 1165756 0t0 TCP bigfoot:55267->178.236.6.251:80 (CLOSE_WAIT)
banshee 16850 dafoot 38u IPv4 1167754 0t0 TCP bigfoot:51386->a88-221-88-42.deploy.akamaitechnologies.com:80 (CLOSE_WAIT)
banshee 16850 dafoot 39u IPv4 1166546 0t0 TCP bigfoot:51391->a88-221-88-42.deploy.akamaitechnologies.com:80 (CLOSE_WAIT)
banshee 16850 dafoot 40u IPv4 1167756 0t0 TCP bigfoot:35847->a88-221-88-57.deploy.akamaitechnologies.com:80 (CLOSE_WAIT)
banshee 16850 dafoot 44u IPv4 1168462 0t0 TCP bigfoot:51404->a88-221-88-42.deploy.akamaitechnologies.com:80 (CLOSE_WAIT)
banshee 16850 dafoot 45u IPv4 1167755 0t0 TCP bigfoot:35846->a88-221-88-57.deploy.akamaitechnologies.com:80 (CLOSE_WAIT)
banshee 16850 dafoot 48u IPv4 1166548 0t0 TCP bigfoot:35852->a88-221-88-57.deploy.akamaitechnologies.com:80 (CLOSE_WAIT)
banshee 16850 dafoot 52u IPv4 1169209 0t0 TCP bigfoot:50867->176.32.110.64:80 (CLOSE_WAIT)

It seems from a quick search that "lhr14s20-in-f7" is a Google service.

So a couple of questions:
What is "lhr14s20-in-f7" doing and do I need it?
Am I even reading the situation correctly (that these services running are preventing httpd.service from grabbing the port and therefore from running)?

---------- Post added 27th January 2013 at 12:08 AM ---------- Previous post was 26th January 2013 at 11:59 PM ----------

Never mind, it was a problem in my config.
I had specified a listen port twice somehow.

george_toolan · #2 27th January 2013, 11:09 AM

There's a little difference between local ports on your machine and remote ports on every other web server ;-)

The only interesting entry is this one:

Code:

TCP localhost.localdomain:8089 (LISTEN)