From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Mon 12 Jan 2004 - 18:32:03 GMT
On Mon, Jan 12, 2004 at 08:53:01AM -0500, 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)
sendmail on the host has to be limited to a subset
of all IP addresses available, otherwise the sendmail
in the vservers cannot bind to any address, because
there is no address left to bind to ...
using the v_* sysvwrapper scripts is one option,
configuring sendmail to _not_ use all addresses
(binding to 0.0.0.0) could be another ...
besides that, it works perfectly, although I switched
to postfix some time ago ...
HTH,
Herbert
> ----- CLIENT -------
> sendmail 3240 root 4u IPv4 58614 TCP christngraphics.com:10025
> (LISTEN)
>
>
> The new question is, how do I back out the vs1.22 patch in order to try
> vs1.21?
>
> Thanks in advance,
> RV
>
>
> On Thu, Dec 18, 2003 at 12:01:34AM -0500, VServer wrote:
> > Hello list:
> >
> > What a great project this is. Hats off guys.
> > I recently found the vserver project and quickly
> > decided to setup my box to take some abuse...
> > This was the logical solution since there are too
> > many computers in this room already.
>
> sounds great!
>
> > I have been running linux-vserver version 2.4.23-vs1.20
> > on a athlon 1.2 MHz with 1.5 GB Ram with Slackware 9.1
> > as the OS.
>
> hmm, don't know about slackware, but the rest
> sounds good to me ...
>
> > I configured 3 vserver guests (2 running Slackware Live
> > and 1 running Sentry Linux) to handle email for 3 domains.
>
> > Sendmail and the virus/spam scanning system have been
> > running beautifully on this setup.
>
> okay, so it works with vs1.20 ...
>
> > I attempted to run 2.4.23-vs1.22 as soon as it came out
> > but after the reboot, sendmail started to error out on me.
>
> > I wrote a rc.vservers script that executes on boot to bring
> > up the vserver clients.
>
> there is a runlevel script included in the userspace
> tools (/etc/init.d/vservers) this might be working
> for you too ...
>
> > Once Sendmail starts up on the clients, I get the following
> > error repeated every five minutes:
> >
> > ----------------------------------------------------------------------------
> > Dec 17 21:41:40 salvation sm-mta[1867]: NOQUEUE: SYSERR(root):
> > opendaemonsocket: daemon MTA-RX: cannot bind: Address already in use
> > Dec 17 21:41:40 salvation sm-mta[1867]: daemon MTA-RX: problem creating SMTP
> > socket
> > ----------------------------------------------------------------------------
>
> okay, looks like the 'address/port' (whatever it might be)
> is already used by some other task ...
>
> I would ask you to try vs1.21, and see if this works for
> you, and to locate the address/port the daemon tries to
> bind to ...
>
> maybe you could provide the following on a web site:
>
> * output of lsof -i
> * your vserver configurations
> * your host service configuration
>
> TIA,
> Herbert
>
> > I hope somebody can help,
> > Ronald Vazquez
>
> _______________________________________________
> Vserver mailing list
> Vserver_at_list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver