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 <defunct> 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
