From: Christian Mayrhuber (christian.mayrhuber_at_gmx.net)
Date: Sun 11 Jan 2004 - 14:06:41 GMT
VServer wrote:
> Hello again:
>
> This email is in reference to a problem I reported back in December 18, 2003.
> Well, due to shortage of time as my real job kept me very busy, I never got
> an opportunity to try vs1.21 on my kernel 2.4.23 as suggested by Herbert.
>
> Just yesterday I decided to upgrade my kernel to 2.4.24 which I patched with
> vs1.22 in hopes of making it work, but it didn't. Now that I'm running
> 2.4.24-vs1.22, I'm still having the same problem I was experiencing back in
> December:
>
> --------------------------------------------------
> Jan 10 10:14:14 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket:
> daemon MTA-RX: cannot bind: Address already in use
> Jan 10 10:14:14 moses sm-mta[3237]: daemon MTA-RX: problem creating SMTP
> socket
> Jan 10 10:14:19 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket:
> daemon MTA-RX: cannot bind: Address already in use
> Jan 10 10:14:19 moses sm-mta[3237]: daemon MTA-RX: problem creating SMTP
> socket
> Jan 10 10:14:19 moses sm-mta[3237]: NOQUEUE: SYSERR(root): opendaemonsocket:
> daemon MTA-RX: server SMTP socket wedged: exiting
> --------------------------------------------------
>
> Here is the output of lsof -i (grep sendmail) where both the HOST and CLIENT
> should show the same output.
>
> ----- HOST -------
> sendmail 3165 root 4u IPv4 56533 TCP *:25 (LISTEN)
> sendmail 3165 root 5u IPv4 56534 TCP *:587 (LISTEN)
> sendmail 3167 root 4u IPv4 56531 TCP localhost:10025 (LISTEN)
>
> ----- CLIENT -------
> sendmail 3240 root 4u IPv4 58614 TCP christngraphics.com:10025
> (LISTEN)
These errors do normally appear if a smtp server is running in the host
system and binds to all network devices.
You can try to stop the smtp daemon on the host system
(sendmail/postfix, etc.) and restart the one in the vserver afterwards.
If this fixes the bind problem, you have to reconfigure the smtp server
in the host system to bind the ip address of the host system only, or
use the sysvwrapper scripts from /etc/init.d to accomplish this task.
This happens, because processes in the host system behave like normal
processes (= like a kernel without vserver patch) and can bind to all
available interfaces.
I have setups with sshd in the host system and sshd in vservers, so this
should work with smtp servers, too.
See: http://www.paul.sladen.org/vserver/faq/ questions 3 and 4.
PS: If vserver should be secure you must not activate IPV6 support in
the Linux kernel.
-- lg, Chris_______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver