Re: [toaster] qmail-smtpd, qmail-pop3d and qmail-pop3s won't start...
- Original Message - From: "David" <[EMAIL PROTECTED]> To: 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: 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 800 (8,000,000) to 3200 (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!
[toaster] had problem with queue, need to recreate directories
I had everything working perfectly, then out of nowhere, my email alias for root was reset to "[EMAIL PROTECTED]". I have no idea how this happened, but nonetheless, it caused thousands of messages to get backed up in the queue and double bounce. In an effort to remove all the pending messages, I removed most of the "1". "2"..."19".. directories in the /var/qmail/queue subdirectories. I did get rid of the huge bounce queue, but now qmail won't work! I'm getting this message: "451 qq trouble creating files in queue " I know it was a dumb move (I assumed they were temp directories to handle the large queue), but what the best way to re-create all the queue subdirectories I removed? Thanks, -Hank
Re: [toaster] had problem with queue, need to recreate directories
Hank wrote: I had everything working perfectly, then out of nowhere, my email alias for root was reset to "[EMAIL PROTECTED]". I have no idea how this happened, but nonetheless, it caused thousands of messages to get backed up in the queue and double bounce. [EMAIL PROTECTED] is the example address used in the toaster. If you copied and pasted the commands, you likely overwrote your previous entries. In an effort to remove all the pending messages, I removed most of the "1". "2"..."19".. directories in the /var/qmail/queue subdirectories. I did get rid of the huge bounce queue, but now qmail won't work! I'm getting this message: "451 qq trouble creating files in queue " I know it was a dumb move (I assumed they were temp directories to handle the large queue), but what the best way to re-create all the queue subdirectories I removed? Yikes. Don't ever mess with the queue unless you know exactly what you are doing. When I want to empty the queue, I usually do it via queuelifetime, rather than trying to touch the right files with a specific date to force expiration, which is the only proper way to do it AFAIK. You can try make setup check from the netqmail source (patched, of course), and it will recreate the queue directory. However, if that directory is already present, I'm not sure if it will recreate the subdirectories that you deleted. If in doubt, rm the queue directory, and re-install netqmail with make setup check. That should do it. Regards, Bill
Re: [toaster] had problem with queue, need to recreate directories
> [EMAIL PROTECTED] is the example address used in the toaster. If you > copied and pasted the commands, you likely overwrote your previous entries. Well, I did change that when I installed the toaster, as things were all working fine... then it mysteriously changed back to "[EMAIL PROTECTED]". Very strange. I did find on qmail.org a repair utility called queue-repair written in python. When I run it, it's complaining about a conf-split of 1 - here's the error: "split should be prime, not 1: suggestions [2] use --i-want-a-broken-conf-split to force non-prime split". What would be the proper setting for the toaster? thanks again, -Hank
Re: [toaster] had problem with queue, need to recreate directories
Hank wrote: [EMAIL PROTECTED] is the example address used in the toaster. If you copied and pasted the commands, you likely overwrote your previous entries. Well, I did change that when I installed the toaster, as things were all working fine... then it mysteriously changed back to "[EMAIL PROTECTED]". Very strange. Check .bash_history, if you use bash (for example). You'll likely find your evidence there, and it will no longer be a mystery. I guarantee it didn't just magically happen. :) I did find on qmail.org a repair utility called queue-repair written in python. When I run it, it's complaining about a conf-split of 1 - here's the error: "split should be prime, not 1: suggestions [2] use --i-want-a-broken-conf-split to force non-prime split". What would be the proper setting for the toaster? The toaster uses the default, which is 23 I believe. Check conf-split. Bill
Re: [toaster] had problem with queue, need to recreate directories
Bill Shupp wrote: > Yikes. Don't ever mess with the queue unless you know exactly what > you are doing. When I want to empty the queue, I usually do it via > queuelifetime, rather than trying to touch the right files with a > specific date to force expiration, which is the only proper way to do > it AFAIK. There is also the qmHandle project : http://sourceforge.net/projects/qmhandle I've used this. I'm still *very* wary of mucking with the queue, but I haven't had any failures yet.. > You can try make setup check from the netqmail source (patched, of > course), and it will recreate the queue directory. However, if that > directory is already present, I'm not sure if it will recreate the > subdirectories that you deleted. If in doubt, rm the queue directory, > and re-install netqmail with make setup check. That should do it. > > Regards, > > Bill -- --- Jason 'XenoPhage' Frisvold Engine / Technology Programmer [EMAIL PROTECTED] RedHat Certified - RHCE # 803004140609871 MySQL Pro Certified - ID# 207171862 MySQL Core Certified - ID# 205982910 --- "Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming."
Re: [toaster] Error 111
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > I have run qmailctl stop countless times but qmail will not stop. > Is there another way? #killal -HUP qmail-lspawn - -- Muhammad -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCR3yfCz+9yg155JgRArZaAJwN9A+e3xdjJp0R2bh/OHfqw5dvEACdGWVh DtINNqSNNCxJo59ashRRFMc= =8Gsu -END PGP SIGNATURE-
Re: [toaster] Odd behavior with Courier?
On Mar 27, 2005, at 7:04 PM, danny soh wrote: I have lots of Unix domain sockets open by /tmp/fam-vpopmail-. After sometime, i will not be able to access my mail through SQUIRRELMAIL. When I stop or restart courier, they still remained. ?The only i get rid of them is by restarting the whole machine. Saw online that you had faced this problem before, had you resolved this issue? Hope you can shared with me your solution. Thanks. Danny emailed me off list, but I'm sending the response back to the list as it might be useful for others. Bill might even want to include a mention of it in the toaster document. I installed the toaster on RedHat FC3, and had fam-related problems. The only solution I found was to run configure, manually edit maildir/config.h to comment out the "#define HAVE_FAM 1" line, and then compile. I've been running problem-free ever since. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
Re: [toaster] Odd behavior with Courier?
Tom Collins wrote: On Mar 27, 2005, at 7:04 PM, danny soh wrote: Danny emailed me off list, but I'm sending the response back to the list as it might be useful for others. Bill might even want to include a mention of it in the toaster document. I installed the toaster on RedHat FC3, and had fam-related problems. The only solution I found was to run configure, manually edit maildir/config.h to comment out the "#define HAVE_FAM 1" line, and then compile. I've been running problem-free ever since. This is exactly what I do. It's a hack, but it works. One of these days, I'd like to find the time to actually get FAM working properly with courier. Regards, Bill
