[Server-devel] Error binding 8080 port for Dansgaurdian
John Watlington
wad at laptop.org
Wed Feb 27 11:06:41 EST 2008
That thread finally got my attention. Port 8080 is used by the
registration service on the server:
http://wiki.laptop.org/go/XS_Service_Description#Identity_Manager
As that port is wired into the existing laptop builds, Dansguardian
should be moved to another port.
wad
On Feb 27, 2008, at 9:10 AM, Tony Pearson wrote:
>
> Stefan Reitz wrote:
> > Dansguardian complains:
> > Starting Web Content Filter (dansguardian): Error binding server
> socket
> > (is something else running on the filter port? [8080])
> > Exiting with error [FAILED]
>
> Stefan, I think I figured out your problem.
>
> ==> First, I did an "nmap -v 192.168.0.29" on my eth0 machine for
> XF, and it shows 8080 also:
>
> [root at squid ~]# nmap -v 192.168.0.29
>
> Starting Nmap 4.20 ( http://insecure.org ) at 2008-02-27 06:50 MST
> Initiating SYN Stealth Scan at 06:50
> Scanning squid.school.pinewood.net (192.168.0.29) [1697 ports]
> Discovered open port 22/tcp on 192.168.0.29
> Discovered open port 443/tcp on 192.168.0.29
> Discovered open port 80/tcp on 192.168.0.29
> Discovered open port 53/tcp on 192.168.0.29
> Discovered open port 8080/tcp on 192.168.0.29
> Discovered open port 3128/tcp on 192.168.0.29
> Completed SYN Stealth Scan at 06:50, 0.18s elapsed (1697 total ports)
> Host squid.school.pinewood.net (192.168.0.29) appears to be up ...
> good.
> Interesting ports on squid.school.pinewood.net (192.168.0.29):
> Not shown: 1691 closed ports
> PORT STATE SERVICE
> 22/tcp open ssh
> 53/tcp open domain
> 80/tcp open http
> 443/tcp open https
> 3128/tcp open squid-http
> 8080/tcp open http-proxy
>
> ==> Then, I did a grep to look for 8080 in my /etc files
>
> [root at squid ~]# grep -r "8080" /etc/*
> /etc/gconf/schemas/system_http_proxy.schemas: <default>8080</
> default>
> /etc/gconf/gconf.xml.defaults/%gconf-tree.xml:
> <default type="int" value="8080">
> grep: /etc/httpd/run/dbus/system_bus_socket: No such device or address
> grep: /etc/httpd/run/avahi-daemon/socket: No such device or address
> /etc/lighttpd/lighttpd.conf:server.port = 8080
> /etc/services:webcache 8080/tcp # WWW
> caching service
> /etc/services:webcache 8080/udp # WWW
> caching service
>
> I don't know what gconf is, but I do recognize "lighty" (lighttpd)
> as a "Apache Lite",
> but given that we are already using "Apache" itself, no need for
> it. I am not sure why
> we have Lighty active at all.
>
> * * * * * Wad? Can you shed some light on this? (pun intended.)
>
> ==> Then, I checked if ligthttpd was running. It was
>
> [root at squid ~]# chkconfig --list | grep light
> lighttpd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
>
> ==> Then I stopped it
>
> [root at squid ~]# service lighttpd stop
> Stopping lighttpd: [ OK ]
>
> ==> Then I ran nmap again:
>
> [root at squid ~]# nmap -r 192.168.0.29
>
> Starting Nmap 4.20 ( http://insecure.org ) at 2008-02-27 07:06 MST
> Interesting ports on squid.school.pinewood.net (192.168.0.29):
> Not shown: 1692 closed ports
> PORT STATE SERVICE
> 22/tcp open ssh
> 53/tcp open domain
> 80/tcp open http
> 443/tcp open https
> 3128/tcp open squid-http
>
> Nmap finished: 1 IP address (1 host up) scanned in 0.178 seconds
>
> ==> So shutting down lighttpd eliminated the 8080 port listening.
> Now to make
> it permanent so that it doesn't start backup up again during boot
> time.
>
> [root at squid ~]# chkconfig --level 345 lighttpd off
> [root at squid ~]# chkconfig --list lighttpd
> lighttpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
>
> ==> This is probably what is happening in your situation, or at
> least shows
> you the diagnostic process for figuring things out like this.
>
> Hope this helps, Tony
>
> Tony Pearson
> Senior Storage Consultant, IBM System Storage™
> Telephone: +1 520-799-4309 | tie 321-4309 | Cell: +1 520 990-8669
> email: tpearson at us.ibm.com | GSA: http://tucgsa.ibm.com/~tpearson
> Blog: http://www.ibm.com/developerworks/blogs/page/InsideSystemStorage
> AKA: 990tony Paravane, eightbar specialist
>
> _______________________________________________
> Server-devel mailing list
> Server-devel at lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel
More information about the Server-devel
mailing list