View previous topic :: View next topic |
Author |
Message |
selim Apprentice
Joined: 14 Apr 2004 Posts: 219
|
Posted: Sun Apr 09, 2006 12:25 am Post subject: vserver apache problem |
|
|
I've installed vserver-sources and utils-vserver, following the steps of this page: http://www.gentoo.org/doc/en/vserver-howto.xml
I've gettin the vps running and can enter it via "vserver vps01 enter" but after I emerge apache within the vps I get this error:
/sbin/runscript.sh: line 32: /var/lib/init.d/softlevel: No such file or directory
* Starting apache2 ...
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
when I'm doing /etc/init.d/apache2 start. Anyone some idea what's causing:
1. /sbin/runscript.sh (I've created a stage3 installation with vserver-new
2. bind to address 0.0.0.0:80 (could be that the vps is not really running correctly but how do I find out?)
Any suggestion would be apprechiated |
|
Back to top |
|
|
ppoudrier n00b
Joined: 21 Dec 2005 Posts: 51
|
Posted: Thu Sep 28, 2006 6:17 pm Post subject: |
|
|
your host machine (the one that run the vserver) already have something that listen on 0.0.0.0:80. For security reason, on your host machine, you must not have any application that listen on all interface (0.0.0.0)
see output of "netstat -anl"
should be like this :
Code: | Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 192.168.0.1:80 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.1:22 0.0.0.0:* LISTEN
tcp 0 0 192.168.0.1:443 0.0.0.0:* LISTEN
|
and not like this (first 0.0.0.0 mean what will listen on every ip address)
Code: | Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
|
if you have those entries, you must find which application bind that and tell them to bind a specific address (the one of your host machine (192.168.0.1 like the above example).
Why you have address already in use is when you look at the output of "ip addr or ipconfig" on your host machine, you will see all the address of your vserver. This mean that your host application can see them and they will bind on that address if you tell them to bind every possible address (0.0.0.0).
Hope it will help. |
|
Back to top |
|
|
slurpyx Tux's lil' helper
Joined: 02 Feb 2005 Posts: 75
|
Posted: Fri Dec 01, 2006 6:58 am Post subject: |
|
|
Also had the same problem..
what i did was..
all my vserver apache service configuration was binded to its spefic ip address.
that worked for me |
|
Back to top |
|
|
|