----- Original Message ----- From: "David" <[EMAIL PROTECTED]>
To: <toaster@shupp.org>
Sent: Sunday, March 27, 2005 12:50 PM
Subject: Re: [toaster] qmail-smtpd, qmail-pop3d and qmail-pop3s won't start...



Thanks Bill for the reply;

----- Original Message ----- From: "Bill Shupp" <[EMAIL PROTECTED]>
To: <toaster@shupp.org>
Sent: Sunday, March 27, 2005 9:00 AM
Subject: Re: [toaster] qmail-smtpd, qmail-pop3d and qmail-pop3s won't start...



David wrote:
Hi all,

Have made several Shupp toaster installs now, but this most recent one has stumped me.

It's on fedora core 3, (x86_64) and I made sure there were no running smtp/pop3/pop3s services before I began:


but neither qmail-smtpd, pop3d or pop3ds will start, using qmailctl script. In each of those daemons' logs, there is:


tcpserver: fatal: temporarily unable to figure out IP address for 0.0.0.0: file does not exist

Has anyone seen this before? I can't work out why tcpserver is being passed a hostname or IP address of 0.0.0.0

The latest toasters are built on netqmail, which has the 0.0.0.0 patch. Did you use the last toaster patch?

Oh... I used the latest version of the toaster (.7.9) with all downloads from there - netqmail 1.05.
Could this be a x86_64 specific problem?


David.


I still can't find a solution for this; and I can only find one or two other mentions of this problem on the 'net. I wonder if other people installing the toaster on x86_64 (AMD64) arch. Fedora core 3 will have the same problem?

I have in the meantime slightly 'hacked' things to get this to work, so I've posted the details here while I can still remember them:

I have two toaster installs which I have done side-by-side (or so to speak), one running redhat 9/i686 (which has been up for months) and one which I just recently installed on FC3/AMD64.

As mentioned the FC3 install keeps logging over and over the message:

"tcpserver: fatal: temporarily unable to figure out IP address for 0.0.0.0: file does not exist"

which I thought was fixed by a patch in netqmail... I've never had this problem before.

Well it seems to be a problem with tcpserver. I tried issuing the command out of the service run script for smtpd on the command line, running as root, on both machines (the rh9 and fc3), substituting the program to be launched by tcpserver for 'cat' (so it would exist on both, and to see if i still got the error without qmail-smtpd binary in the picture) with all qmail services stopped:

rh9]# /usr/local/bin/tcpserver -v -H -R -l 0 \
   -x /home/vpopmail/etc/tcp.smtp.cdb -c "$MAXSMTPD" \
   -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
   cat \

result:

tcpserver: status: 0/0

ok, so on the fc3 box:

fc3]# /usr/local/bin/tcpserver -v -H -R -l 0 \
   -x /home/vpopmail/etc/tcp.smtp.cdb -c "$MAXSMTPD" \
   -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
   cat \

result:

tcpserver: fatal: temporarily unable to figure out IP address for 0.0.0.0: file does not exist

So I figured I had narrowed it down to tcpserver, having countless times re-installed/rebuilt the qmail and daemontools/uscpi from the (Shupp) source...
so i cheated and copied the tcpserver binary accross from the rh9 box. Then I got:


fc3]# /usr/local/bin/tcpserver -v -H -R -l 0 \
   -x /home/vpopmail/etc/tcp.smtp.cdb -c "$MAXSMTPD" \
   -u "$QMAILDUID" -g "$NOFILESGID" 0 smtp \
   cat \

result:

tcpserver: status: 0/0

So far it seemed ok... but checking the smtpd logfile:

fc3]# tail /var/log/qmail/smtpd/current | tai64nlocal

2005-03-27 19:38:52.934767500 tcpserver: pid 11812 from [foreign ip]
2005-03-27 19:38:52.934769500 tcpserver: ok 11812 0:[my ip]:25 :[foreign ip]::22216
2005-03-27 19:38:52.934771500 /var/qmail/bin/qmail-smtpd: error while loading shared libraries: libz.so.1: failed to map segment from shared object: Cannot allocate memory


Rats. So after more testing I increased the softlimit value in the /service/qmail-smtpd/run script, and it worked. smtpd service came up, stayed up, and delivered mail.

I changed the softlimit from 8000000 (8,000,000) to 32000000 (32,000,000) - this was the smallest setting I could manage to make it work with.
I am a little worried that I have had to quadruple the amount of RAM allowed for qmailsmtpd to run; however I haven't had to increase the softlimits for either pop3d or pop3ds services, which work after the tcpserver replacement, and they didn't work before either... should I be concerned about a softlimit this big?


Btw, I have not installed simscan or any other qmailqueue "plugin".

Sorry about the long post, I hope the extra info might help spark an idea that could help me solve this problem more cleanly....

Thanks again,
David.

Regards,

Bill







!DSPAM:424626a839461389110235!







Reply via email to