|
i reinstalled qmail.. and i still have errors!!
remember what u told me yesterday... about the syntax of the svc command.. well .. im following LWQ . and when it says to check for errors in the installation.. it tells u to do this..: # ps -efl | grep "service errors" | grep -v grep my out put to that is this : root@azul:~/qmail# ps -efl | grep "service errors" | grep -v grep 0 S root 31291 31288 0 69 0 - 333 pipe_w 10:47 ? 00:00:00 readproctitle service errors: ...ail/smtpd: access denied?multilog: fatal: unable to lock directory /var/log/qmail: access denied?multilog: fatal: unable to lock directory /var/log/qmail/smtpd: access denied?multilog: fatal: unable to lock directory /var/log/qmail: access denied?multilog: fatal: unable to lock directory /var/log/qmail/smtpd: access denied?multilog: fatal: unable to lock directory /var/log/qmail: access denied? so.. after that.. LWQ tells u can try this.: cd /service/qmail-smtpd/log svc -d . ./run so i tried it and this is what i got root@azul:/service/qmail-smtpd/log# svc -d root@azul:/service/qmail-smtpd/log# ./run multilog: fatal: unable to lock directory /var/log/qmail/smtpd: temporary failure i know u told me i must specify sth to the svc command.. but it tells me error.. do u think this is an owner file problem? |
Yep.. /var/log/qmail - access denied is most definitely a ownership/permissions problem. You need to chown qmaill /var/log/qmail /var/log/qmail/smtpd. The inst_check script should have caught this error and asked you to fix it.
After you change that stuff, you should reboot the system and it will wipe out your "readproctile" errors. If there are none, it will just be a bunch of dots. If there are new errors, they will show up there. Hopefully you will not get the same error again. |
yes!! finally!!!!!!!!!!!!! it was an owners problem!!
the thing is that LWQ doesnt tell u that /var/qmail/supervise and all in it needed to be owned by qmaill as well this is what i get now: root@azul:/var/log/qmail# qmailctl stat /service/qmail-send: up (pid 975) 982 seconds /service/qmail-send/log: up (pid 978) 982 seconds /service/qmail-smtpd: up (pid 979) 982 seconds /service/qmail-smtpd/log: up (pid 981) 982 seconds messages in queue: 0 messages in queue but not yet preprocessed: 0 root@azul:/var/log/qmail# ps -efa | grep qmail root 892 890 0 12:26 ? 00:00:00 supervise qmail-send root 894 890 0 12:26 ? 00:00:00 supervise qmail-smtpd qmails 975 892 0 12:26 ? 00:00:00 [qmail-send] qmaill 978 893 0 12:26 ? 00:00:00 /usr/local/bin/multilog t /var/log/qmail/send qmaild 979 894 0 12:26 ? 00:00:00 [tcpserver] qmaill 981 897 0 12:26 ? 00:00:00 /usr/local/bin/multilog t /var/log/qmail/smtpd root 984 975 0 12:26 ? 00:00:00 qmail-lspawn ./Mailbox qmailr 985 975 0 12:26 ? 00:00:00 [qmail-rspawn] qmailq 987 975 0 12:26 ? 00:00:00 [qmail-clean] root 1040 16278 0 12:43 pts/3 00:00:00 grep qmail root@azul:/var/log/qmail# ps -efl | grep "service errors" | grep -v grep 0 S root 891 888 0 69 0 - 333 pipe_w 12:26 ? 00:00:00 readproctitle service errors: .................................................................................................... ............................................................... it is ok .. isn't it?? |
though.. i still dont understand.. why when i do this..
root@azul:/service/qmail-smtpd/log# svc -d root@azul:/service/qmail-smtpd/log# ./run multilog: fatal: unable to lock directory /var/log/qmail/smtpd: temporary failure i still have that error message-- |
>> LWQ doesnt tell u that /var/qmail/supervise and all in it needed to be owned by qmaill
That's because they don't need to be. The directory /var/qmail/supervise does need to be owned by qmaill, but this is created by the make/install command. The stuff under there can be owned by root. However, LWQ also tells you to chmod the run scripts to 755 which makes the executable by any user, so therefore they CAN be owned by root and still be executed by any user. Everything looks good now. Your readproc is showing all dots, and your services are up for more than 1 second, so you're in business. Glad you got it working. Have fun! |
You should go back and look at LWQ... you're missing one very small but important thing... there is a single dot right beside svc -d in that statement. You should also look at "2.8.2.1. The qmailctl script" and look at the start and stop sections of that script. You'll notice that it's just using "svc -u /path/to/service" and "svc -d /path/to/service" which is really the correct usage for that command. I don't like Dave's usage of it where he uses only a single dot... this confuses people too much, I think.
|
i checked" svc -d . "
u were right! i wasnt writting it! :P thanks! theres one thing that still bothers me.. and its that .. accordingly to LWQ.. another qmaild server should be starting up.. qmaild 13717 1185 0 17:33 ? 00:00:00 /var/qmail/bin/qmail-smtpd it seems as if the qmail-smtpd wouldnt be stating-- but that is not what the qmailctl stat says... i dont realise what is happening here.. |
Well, looking at one of your earlier posts today, you have something running under qmaild... it's tcpserver. This is probably what you're looking for. One thing... I'm surprised it only says [tcpserver]... mine says the whole command that is running, which is basically the contents of my /var/qmail/supervise/qmail-smtpd/run file that is running under qmaild user.
If you can try to telnet to your smtpd service and it works, then you're OK. Try this... telnet 127.0.0.1 25 Notice there is a space between the ip address and the 25 which is the port number. You should get something like this... [root@falcon root]# telnet 127.0.0.1 25 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. 220 hostname.yourdomain.com ESMTP helo anything 250 hostname.yourdomain.com mail from: me@mydomain.com 250 ok rcpt to: user@yourdomain.net 250 ok data 354 go ahead something blah,blah blah . 250 ok 1090602878 qp 13724 quit 221 hostname.yourdomain.com Connection closed by foreign host. The helo, mail from, rcpt to, and data commands are commands you input yourself at the command line. When you're done typing the body of your message (like something, blah, blah etc) just put a single dot and hit enter to end the body section. Then type quit and the connection will be closed. Hopefully you should get all positive responses from your smtp server. |
i did what u told me and this is my out put:
root@azul:/var/qmail/supervise/qmail-smtpd/log# telnet 127.0.0.1 25 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. 220 azul.uba.ar ESMTP helo 250 azul.uba.ar mail from: azul@azul 250 ok rcpt to: root@azul 250 ok data 354 go ahead blabla . 250 ok 1090604699 qp 2088 quit 221 azul.uba.ar Connection closed by foreign host. everything @25 seeems to be workin' i think.. though i still dont understan what i told u before.. i checked.. the run scripts.. i think what is happening is that in someway the svscan is not getting up the qmail-smtp-- i think so.. because the line i dont have seems to be calling /var/qmail/bin/qmail-smtpd this is strange.. should qmaild be the owner of this file?? my owner is qmaill.. |
i m leaving from work now.. and i'll be on vacations next week.. can i keep asking on my return the other week?
|
>> i did what u told me and this is my out put:
Looks perfect! Now you should have a blank email message injected into your queue. If qmail is working right, it should move that message over to root@azul's mailbox pretty quickly (seconds) after it's inserted into the queue. >> though i still dont understan what i told u before Not sure what you mean by this. >> i think what is happening is that in someway the svscan is not getting up the qmail-smtp Not sure why you feel that way. Looks like smtp is working fine. If you can check your mail using pop3 that would be a good way to test. Otherwise (like if you dont have that setup yet) you can just go to root's mailbox and look to see if the message was moved into there. >> because the line i dont have seems to be calling... Maybe it doesn't matter. So long as it's delivering mail from the outside to the inside, you're all good. >> should qmaild be the owner of this file qmaild should be the owner according to ps output. I wouldn't worry about it too much until we're sure there is a problem. >> can i keep asking on my return the other week Sure. Keep em coming. If I'm available I'll try to help when I can. |
Hey !
i reinstalled qmail.. and it seemed to be workin'-- though i still have problems! :( when i arrived @work this morning i asked for the qmailctl stat and everything was up.-- so i thought the qmail was running ok.. i sent an email and it went out . but.. now.. when i ask for the qmailctl stat i've got this: root@azul:/var/log/qmail/smtpd# qmailctl stat /service/qmail-send: up (pid 10972) 446 seconds /service/qmail-send/log: up (pid 10974) 446 seconds /service/qmail-smtpd: up (pid 10976) 446 seconds /service/qmail-smtpd/log: up (pid 11570) 0 seconds and before i restarted qmail.. it told me that : /service/qmail-smtpd/log:down - normally up for quite a while.. it also gives me this error: root@azul:/var/log/qmail/smtpd# ps -efa | grep qmail qmaill 8394 8292 0 09:36 pts/0 00:00:00 /usr/local/bin/multilog t /var/log/qmail/smtpd root 9458 9455 0 11:47 ? 00:00:00 readproctitle service errors: ...al: unable to lock directory /var/log/qmail/smtpd: temporary failure?multilog: fatal: unable to lock directory /var/log/qmail/smtpd: temporary failure?multilog: fatal: unable to lock directory /var/log/qmail/smtpd: temporary failure?multilog: fatal: unable to lock directory /var/log/qmail/smtpd: temporary failure?multilog: fatal: unable to lock directory /var/log/qmail/smtpd: temporary failure? root 9459 9457 0 11:47 ? 00:00:00 supervise qmail-send root 9461 9457 0 11:47 ? 00:00:00 supervise qmail-smtpd qmails 10972 9459 0 12:08 ? 00:00:00 [qmail-send] qmaill 10974 9460 0 12:08 ? 00:00:00 /usr/local/bin/multilog t /var/log/qmail/send qmaild 10976 9461 0 12:08 ? 00:00:00 [tcpserver] root 10977 10972 0 12:08 ? 00:00:00 qmail-lspawn ./Mailbox qmailr 10978 10972 0 12:08 ? 00:00:00 [qmail-rspawn] qmailq 10979 10972 0 12:08 ? 00:00:00 [qmail-clean] qmaill 11732 9464 3 12:17 ? 00:00:00 [multilog] <defunct> i don't understan why???? from one second to another it gives me this kind of message.. 'cause it didn't before!!! i didnt change anything on mi configuration.. does anyone know what can be happening?? thanks! |
Can you post your qmailctl script? I suspect there is a command missing and its not stopping/starting the smtp logging process like it should.
You may also want to check the permisions on /var/log/qmail/smtpd be sure they match whatever you have for /var/log/qmail/send. |
THANKS 4 ANSWER!!!! :)
i realised i had a zombie fooling aroun' that was botherig me.. though................. (there's always a " though! " ). LWQ says this.. : ---------------------------------------------------------------------------------------- [dave@sparge dave]$ ps waux|grep qmail dave 2222 0.0 0.8 836 348 p4 S 10:25 0:00 grep qmail qmaild 351 0.0 1.0 840 400 ? S N 12:43 0:00 /usr/local/bin/tcpserver -v -x /etc/tcp.smtp.cdb -u 49491 -g 31314 0 smtp /var/qmail/bin/qmail-smtpd- qmaild 2220 0.0 1.0 844 420 ? S N 10:25 0:00 /usr/local/bin/tcpserver -v -x /etc/tcp.smtp.cdb -u 49491 -g 31314 0 smtp /var/qmail/bin/qmail-smtpd- qmaill 365 0.0 0.8 748 344 ? S N 12:43 0:00 splogger qmail qmailq 368 0.0 0.7 736 292 ? S N 12:43 0:00 qmail-clean qmailr 367 0.0 0.6 732 272 ? S N 12:43 0:00 qmail-rspawn qmails 350 0.0 0.8 776 336 ? S N 12:43 0:00 qmail-send root 340 0.0 0.6 724 252 ? S N 12:43 0:00 /usr/local/sbin/supervise /var/supervise/qmail-send /var/qmail/rc root 341 0.0 0.6 724 252 ? S N 12:43 0:00 /usr/local/sbin/supervise /var/supervise/tcpserver-qmail /usr/local/bin/tcpserver -v -x /etc/tcp.smtp root 366 0.0 0.7 736 276 ? S N 12:43 0:00 qmail-lspawn ./Mailbox [dave@sparge dave]$ If you run qmail or qmail-smtpd under supervise, as in the example above, you should see those processes as well. And if run qmail-smtpd under tcpserver, you should see a parent tcpserver process plus an additional tcpserver process for each active incoming SMTP connectioni ! thanks 4 answer! ---------------------------------------------------------------------------------------- while my my output is: root@azul:/etc# ps waux | grep qmail root 18911 0.0 0.2 1336 76 ? S Aug02 0:00 supervise qmail-smtpd root 18921 0.0 0.2 1336 76 ? S Aug02 0:00 supervise qmail-send qmails 18932 0.0 0.8 1384 236 ? S Aug02 0:00 [qmail-send] qmaill 18935 0.0 0.2 1352 60 ? S Aug02 0:00 /usr/local/bin/multilog t /var/log/qmail/send qmaild 18936 0.0 0.5 1404 164 ? S Aug02 0:00 [tcpserver] qmaill 18937 0.0 0.0 1352 20 ? S Aug02 0:00 /usr/local/bin/multilog t /var/log/qmail/smtpd root 18938 0.0 0.1 1352 32 ? S Aug02 0:00 qmail-lspawn ./Mailbox qmailr 18939 0.0 0.7 1348 228 ? S Aug02 0:00 [qmail-rspawn] qmailq 18940 0.0 0.4 1344 128 ? S Aug02 0:00 [qmail-clean] LWQ says that if i am running qmail under tcpserver (and I AM) i should see all the processes they told... i still have a process missinig that shold be running under qmaild...: qmaild 351 0.0 1.0 840 400 ? S N 12:43 0:00 /usr/local/bin/tcpserver -v -x /etc/tcp.smtp.cdb -u 49491 -g 31314 0 smtp /var/qmail/bin/qmail-smtpd- this process is the one that listens @port 25... waiting for incoming conections i sent a mail to myself and it never arrived.. I can send mails but i can not receive them!! i think that this process is the responsible for this.. i checked the permissions & owners of the supervise file root@azul:/var/qmail# ls -l total 40 drwxr-sr-x 2 alias qmail 4096 Jul 23 11:30 alias/ drwxr-xr-x 2 root qmail 4096 Jul 23 10:55 bin/ drwxr-xr-x 2 root qmail 4096 Jul 23 10:26 boot/ drwxr-xr-x 2 root qmail 4096 Jul 23 11:05 control/ drwxr-xr-x 2 root qmail 4096 Jul 23 10:26 doc/ drwxr-xr-x 10 root qmail 4096 Jul 23 10:26 man/ drwxr-x--- 11 qmailq qmail 4096 Jul 23 10:26 queue/ -rwxr-xr-x 1 root root 216 Jul 23 10:50 rc* drwxr-xr-x 4 qmaill root 4096 Jul 23 11:01 supervise/ drwxr-xr-x 2 root qmail 4096 Aug 2 10:56 users/ root@azul:/var/qmail/supervise# ls -l total 8 drwxr-xr-x 4 qmaill root 4096 Jul 23 11:02 qmail-send/ drwxr-xr-x 4 qmaill root 4096 Jul 23 15:11 qmail-smtpd/ and the run script of the qmail-smtpd is the following: root@azul:/var/qmail/supervise/qmail-smtpd# cat run #! /bin/sh #Levanta tcpserver, quien maneja y espera las conexiones smtp en el puerto 25 (en vez de inetd) exec /usr/local/bin/softlimit -m 5000000 envuidgid qmaild tcpserver -c 10 -v -p -u 1003 -g 102 0 smtp \ /var/qmail/bin/qmail-smtpd 2>&1 i did everything LWQ tells.. and still not workin' any idea? |
I believe it must be because your run file doesn't look anything like what Life With Qmail shows. Yours looks totally different.
Here's what it says yours should look like... Quote:
qmaild 18936 0.0 0.5 1404 164 ? S Aug02 0:00 [tcpserver] which has caused me to scratch my head everytime I see it, but now I think I'm beginning to realize this must be the reason its showing up this way. For example.... my output looks like this... qmaild 2817 0.0 0.0 1384 312 ? S Jul31 0:01 /usr/local/bin/tcpserver -p -R -x /home/vpopmail/etc/tcp. cdb -u92 -g91 -v -c100 0 25 There's a little more, but this gives you the idea. The major difference is, I can see the full commands and arguments where in yours I don't. |
| All times are GMT -5. The time now is 08:40 PM. |