Success !Re: supervise lock problem on startup/install
Dave, et al, Thanks for the help. I let a linebreak get into my shell script. I've spent so much time in GUI-land that I still get stuck in the muck sometimes. After fixing that, and doing a qmail restart, I checked my running services. I have the following qmail related in my list: svscan supervise supervise qmail-send qmail-lspawn qmail-rspawn qmail-clean tcpserver In an earlier message, Dave suggested that I should see four 'supervise' entries... is all correct in the above? Thanks, J!M J!M > [EMAIL PROTECTED] wrote: > > >[root@samurai /root]# /var/qmail/rc: default: command not found > > Oops, you never mentioned that little detail. :-) Your rc script is > wrong. > > -Dave > >
Re: supervise lock problem on startup/install
[EMAIL PROTECTED] wrote: >[root@samurai /root]# /var/qmail/rc: default: command not found Oops, you never mentioned that little detail. :-) Your rc script is wrong. -Dave
Re: supervise lock problem on startup/install
J!M writes: > [root@samurai /root]# /var/qmail/rc: default: command not found What does your /var/qmail/rc look like? paul
Re: supervise lock problem on startup/install
I think we've almost got it golden... Dave Sill Wrote: > > Owners/groups/modes are a mess, but I don't think that's your > problem. Kill off all the processes, then do: > > rm -r /var/qmail/supervise/*/supervise > rm -r /var/qmail/supervise/*/log/supervise > chown -R root:qmail /var/qmail/supervise > chmod -R go-w /var/qmail/supervise > > Then run "qmail start" again. Everything else looks OK. > This is what happens when I start qmail. I get the rc error, and wait for a prompt to come back. Hitting enter gives back prompt. Are we close? [root@samurai /root]# /usr/local/sbin/qmail start Starting qmail: svscan. [root@samurai /root]# /var/qmail/rc: default: command not found tcpserver: status: 0/40 status: local 0/10 remote 0/20 [root@samurai /root]# Thanks, J!M > If that fails, post the output of: > > ps -ef|egrep 'qmail|supervise|sv|log' > qmail stat > > Before you clean anything up. > > -Dave > >
Re: supervise lock problem on startup/install
[EMAIL PROTECTED] wrote: >/var/qmail/supervise: >total 8 >drwxrwxrwx4 qmaill nofiles 4096 Jul 3 00:42 qmail-send >drwxrwxrwx4 qmaill nofiles 4096 Jul 3 00:42 qmail-smtpd > >/var/qmail/supervise/qmail-send: >total 12 >drwxrwxrwx3 qmaill nofiles 4096 Jul 3 00:42 log >-rwxr-xr-x1 qmaill nofiles29 Jul 2 23:20 run >drwxrwxrwx2 qmaill nofiles 4096 Jul 7 10:08 supervise > >/var/qmail/supervise/qmail-send/log: >total 8 >-rwxr-xr-x1 qmaill nofiles88 Jul 5 21:51 run >drwxrwxrwx2 qmaill nofiles 4096 Jul 5 21:55 supervise > >/var/qmail/supervise/qmail-send/log/supervise: >total 4 >prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 control >-rwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 lock >prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 ok >-rw-r--r--1 qmaill nofiles18 Jul 5 21:55 status > >/var/qmail/supervise/qmail-send/supervise: >total 4 >prwxrwxrwx1 qmaill nofiles 0 Jul 6 11:55 control >-rwxrwxrwx1 qmaill nofiles 0 Jul 4 18:46 lock >-rwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 lock.old >prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 ok >-rw-r--r--1 root root 18 Jul 7 10:08 status > >/var/qmail/supervise/qmail-smtpd: >total 12 >drwxrwxrwx3 qmaill nofiles 4096 Jul 3 00:42 log >-rwxr-xr-x1 qmaill nofiles 230 Jul 6 14:08 run >drwxrwxrwx2 qmaill nofiles 4096 Jul 7 10:08 supervise > >/var/qmail/supervise/qmail-smtpd/log: >total 8 >-rwxr-xr-x1 qmaill nofiles94 Jul 5 21:52 run >drwxrwxrwx2 qmaill nofiles 4096 Jul 5 21:55 supervise > >/var/qmail/supervise/qmail-smtpd/log/supervise: >total 4 >prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 control >-rwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 lock >prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 ok >-rw-r--r--1 qmaill nofiles18 Jul 5 21:55 status > >/var/qmail/supervise/qmail-smtpd/supervise: >total 4 >prwxrwxrwx1 qmaill nofiles 0 Jul 6 11:55 control >-rwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 lock >prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 ok >-rw-r--r--1 root root 18 Jul 7 10:08 status Owners/groups/modes are a mess, but I don't think that's your problem. Kill off all the processes, then do: rm -r /var/qmail/supervise/*/supervise rm -r /var/qmail/supervise/*/log/supervise chown -R root:qmail /var/qmail/supervise chmod -R go-w /var/qmail/supervise Then run "qmail start" again. Everything else looks OK. If that fails, post the output of: ps -ef|egrep 'qmail|supervise|sv|log' qmail stat Before you clean anything up. -Dave
Re: supervise lock problem on startup/install
> [EMAIL PROTECTED] wrote: > > >Still having the service lock problem -- thanks Dave, I've followed your > >suggestions here: > You mean "supervise"? You should see four: one each for qmail-send, > qmail-smtpd, and two for "log"--the logs associated with them. Yes "supervise" - Only two entries, both . > Post the output of the following: > > ls -lR /var/qmail/supervise /var/qmail/supervise: total 8 drwxrwxrwx4 qmaill nofiles 4096 Jul 3 00:42 qmail-send drwxrwxrwx4 qmaill nofiles 4096 Jul 3 00:42 qmail-smtpd /var/qmail/supervise/qmail-send: total 12 drwxrwxrwx3 qmaill nofiles 4096 Jul 3 00:42 log -rwxr-xr-x1 qmaill nofiles29 Jul 2 23:20 run drwxrwxrwx2 qmaill nofiles 4096 Jul 7 10:08 supervise /var/qmail/supervise/qmail-send/log: total 8 -rwxr-xr-x1 qmaill nofiles88 Jul 5 21:51 run drwxrwxrwx2 qmaill nofiles 4096 Jul 5 21:55 supervise /var/qmail/supervise/qmail-send/log/supervise: total 4 prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 control -rwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 lock prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 ok -rw-r--r--1 qmaill nofiles18 Jul 5 21:55 status /var/qmail/supervise/qmail-send/supervise: total 4 prwxrwxrwx1 qmaill nofiles 0 Jul 6 11:55 control -rwxrwxrwx1 qmaill nofiles 0 Jul 4 18:46 lock -rwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 lock.old prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 ok -rw-r--r--1 root root 18 Jul 7 10:08 status /var/qmail/supervise/qmail-smtpd: total 12 drwxrwxrwx3 qmaill nofiles 4096 Jul 3 00:42 log -rwxr-xr-x1 qmaill nofiles 230 Jul 6 14:08 run drwxrwxrwx2 qmaill nofiles 4096 Jul 7 10:08 supervise /var/qmail/supervise/qmail-smtpd/log: total 8 -rwxr-xr-x1 qmaill nofiles94 Jul 5 21:52 run drwxrwxrwx2 qmaill nofiles 4096 Jul 5 21:55 supervise /var/qmail/supervise/qmail-smtpd/log/supervise: total 4 prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 control -rwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 lock prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 ok -rw-r--r--1 qmaill nofiles18 Jul 5 21:55 status /var/qmail/supervise/qmail-smtpd/supervise: total 4 prwxrwxrwx1 qmaill nofiles 0 Jul 6 11:55 control -rwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 lock prwxrwxrwx1 qmaill nofiles 0 Jul 3 00:42 ok -rw-r--r--1 root root 18 Jul 7 10:08 status > cat /var/qmail/supervise/*/run #!/bin/sh exec /var/qmail/rc #!/bin/sh QMAILDUID='id -u qmaild' NOFILESGID='id -g qmaild' exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 2>&1 > cat /var/qmail/supervise/*/log/run #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail/smtpd Here they are. Thanks for the help. J!M
Re: supervise lock problem on startup/install
[EMAIL PROTECTED] wrote: >Still having the service lock problem -- thanks Dave, I've followed >your suggestions here: > >>The general approach to fixing this problem is: >> >> 1) Stop all qmail-related processes including svscan, supervises, >> anything running as a "qmail" user, qmail-send, multilogs, >> etc. *Everything*. > >ps -a shows no qmail related services running prior to sending the >start command. If I let the error loop in one term window I see >svscan and TWO service entries (with one or both >depending on how quickly I run ps). I looked for clues as to the >origin of the two instances, but couldn't find anything obvious. You mean "supervise"? You should see four: one each for qmail-send, qmail-smtpd, and two for "log"--the logs associated with them. >> 2) Double check directory names/owners/groups/modes and the >> contents of "run" scripts against LWQ. Check for extraneous >>ampersands (&) at the ends of lines. > >I have probably messed this up from standard... I recursively set >ownership of /var/qmail/supervise and its subdirectories to >qmaill.nofiles. The directories I opened up to 777. I reran the chmod >commands in LWQ on the run files in those directories setting >them to 755. I have no idea whether these changes would make >my problem worse, but the results have not changed... Post the output of the following: ls -lR /var/qmail/supervise cat /var/qmail/supervise/*/run cat /var/qmail/supervise/*/log/run -Dave
supervise lock problem on startup/install
Hello all, Still having the service lock problem -- thanks Dave, I've followed your suggestions here: >The general approach to fixing this problem is: > > 1) Stop all qmail-related processes including svscan, supervises, > anything running as a "qmail" user, qmail-send, multilogs, > etc. *Everything*. ps -a shows no qmail related services running prior to sending the start command. If I let the error loop in one term window I see svscan and TWO service entries (with one or both depending on how quickly I run ps). I looked for clues as to the origin of the two instances, but couldn't find anything obvious. > 2) Double check directory names/owners/groups/modes and the > contents of "run" scripts against LWQ. Check for extraneous >ampersands (&) at the ends of lines. I have probably messed this up from standard... I recursively set ownership of /var/qmail/supervise and its subdirectories to qmaill.nofiles. The directories I opened up to 777. I reran the chmod commands in LWQ on the run files in those directories setting them to 755. I have no idea whether these changes would make my problem worse, but the results have not changed... > 3) Restart svscan via "qmail start". > > If the problem doesn't go away, repeat 1 & 2, and re-run 3 with >"sh -x /usr/local/sbin/qmail start". Cut and paste the output and > post it to the list. [root@samurai supervise]# sh -x /usr/local/sbin/qmail start + PATH=/var/qmail/bin:/usr/local/bin:/usr/bin:/bin + export PATH + echo -n Starting qmail: svscan Starting qmail: svscan+ cd /var/qmail/supervise + env - PATH=/var/qmail/bin:/usr/local/bin:/usr/bin:/bin svscan + echo 20793 + echo . . + exit 0 [root@samurai supervise]# supervise: fatal: unable to acquire qmail-send/supervise/lock: temporary failure supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: temporary failure - Thanks for looking at this, qmail is the last piece in the puzzle before I can make this server live. J!M
