Qmail won't start
Hi Guys,
I thought I had made a thread about this already but I don't seem to be able to find it so I'll pop it up again. I have just followed through the guide QmailToaster Guide - Start to Finish, link here and everything went really well. One tiny problem though whenever I attempt to start, restart or do anything with qmail I get the following (In the following I did a restart) Code:
Restarting qmail: I am at a bit of a loss, I have tried going back over this to no avail, I really don't know what I'm missing. I'm running FC3 with all the latest updates if that's of any help. Thanks Cheers Darren |
i prefer www.qmailrocks.org to install qmail. i can advice u to follow that guide for qmail.
good luck. |
I have just tried that myself to no avail, when I get so far you have to stop qmail which comes back with exactly the same error.
|
remove old packets first. if prevous installation was rpm based (i think it was), remove them with rpm command.
do rpm -qa|grep toaster so it will show u packets which includes "toaster" word. note that names. DO NOT note packets which are not related to qmail-toaster. after that remove them like this: rpm -e packet1-toaster packet2-toaster .... packet(x)-toaster after that delete qmail and its softwares dir rm -rf /var/qmail rm -rf /var/log/qmail rm -rf /home/vpopmail also check last line of /etc/inittab file. it musnt have a line like this: SV:123456:respawn:env ..... good luck. |
Thanks for that maxut, I went through and did as instructed removing anything to do with toaster and my failed qmailrocks install and went about installing from scratch.
I've run through all the way up to part 14 and despite getting stuck on some perl modules which have been installed but spamassassin-tools doesn't pick them up, nevertheless it's at least a lot happier. Thanks once again, it's really put a smile on my face seeing some progress. Cheers Darren |
if "/downloads/qmailrocks/scripts/util/check_perlmods.script" shows u those perl modules installed, u can go with
rpm -Uvh --nodeps spamassassin-tools good luck. |
I tried that script as per the instructions, all passed with flying colours from what I can see and installed spamassassin-tools using --nodep which worked fine.
Although further down the track when I run /downloads/qmailrocks/qmail-scanner-1.24/contrib/ ./test_installation.sh I get the following Code:
[root@test contrib]# /downloads/qmailrocks/qmail-scanner-1.24/contrib/./test_installation.sh -doit Code:
Dec 21 18:54:21 test X-Antivirus-MYDOMAIN-1.24-st-qms: [test.justcommodores.com.au110361746176019702] clamdscan: corrupt or unknown clamd scanner error or memory/resource/perms problem - exit status 512/2 |
hmm. im not familiar to clamav. i use kaspersky antivrus.
it seems that it is a clam trouble. what does "qmailctl stat" show? also try to change following line in /var/qmail/bin/qmail-scanner-queue.pl to make sure that clam causes that. Code:
my @scanners_installed=("clamdscan_scanner","spamassassin","perlscan_scanner"); |
I actually found a similar post in another language regarding changing the qmail-scanner-queue.pl file which as soon as I changed it everything worked as expected so as you were pointing it certainly is something to do with ClamAV which is great to know.
Running qmailctl stat I get Code:
/service/qmail-send: up (pid 18427) 58620 seconds EDIT I am not sure what I did but I went back over anything that seemed relevant, rebooted the system and bob's your uncle it's now working. Once again thank you very much maxut for all your help and answering all the questions I have put forward. |
I think I saw this same problem, however, not during install. Assuming your qmail directory is, /var/qmail, check the /var/qmail//supervise/qmail-smtpd/run file. Check the size of the softlimit entry. I had mine set to 5000000 and I still had problems. I tried 10000000 as well. So, I decided to crank it up to like 50000000 and I haven't seen that problem again. So, try increasing the softlimit and see if that works.
|
isnt it too much for softlimit?
from lifewithqmail.org: Note: The memory limit specified in the softlimit command may need to be raised depending upon your operating system and hardware platform. If attempts to connect to port 25 fail or remote systems are unable to send you mail, or you see a message like: /usr/local/bin/tcpserver: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory try raising it to 3000000 or 4000000. good luck. |
All times are GMT -5. The time now is 04:49 PM. |