On Tuesday 22 Mar 2005 03:27, Carl Parrish wrote: > On Mon, 2005-03-21 at 20:18 +0000, Bob Hutchinson wrote: > > > qmailctl stat looks like this. > > > > > > /service/qmail-send: up (pid 5411) 0 seconds > > > /service/qmail-send/log: up (pid 5985) 556382 seconds > > > /service/qmail-smtpd: up (pid 20712) 1963 seconds > > > /service/qmail-smtpd/log: up (pid 6048) 556382 seconds > > > messages in queue: 2 > > > messages in queue but not yet preprocessed: 0 > > > > check your logs in /var/log/qmail/current > > You may still have sendmail (or whatever) running, which might be why > > qmail-send will not start. > > > > and where is qmail-pop3d? > > now when I type "ps -ef | grep pop" I get this error. > > root 5763 5666 0 Mar15 ? 00:00:12 readproctitle service > errors: ...ied?multilog: fatal: unable to lock > directory /var/log/qmail/pop3ds: access denied?multilog: fatal: unable > to lock directory /var/log/qmail/pop3d: > > Again no clue what I'm doing wrong here. Permissions > of /var/log/qmail/is > > drwxr-xr-x 2 qmaill root 1024 Mar 21 20:24 pop3d > drwxr-xr-x 2 qmaill root 1024 Mar 21 20:23 pop3ds > drwxr-xr-x 2 qmaill root 1024 Mar 15 16:07 smtpd
Looks to me like you have other processes already running and using the ports concerned. You need to hunt them down, stop them and make sure they don't start again on reboot Get the hang of using the svc command directly, read qmailctl and see what it is doing to stop/start/reload etc you could try this: Stop svscan altogether. edit /etc/inittab and comment out the svscan line which is probably right at the bottom. Run kill -HUP 1 then run ps ax and svscan should be gone completely use netstat -at to see if any of the ports are still in use, if they are look at inetd or xinetd to see if they are there, and disable them. Look in /etc/init.d for anything likely looking and disable/uninstall. When you are sure that things look better, remove the symlinks in /service, uncomment svscan in inittab and -HUP it again. Look to see how it's doing with ps ax. look in /var/qmail/supervise/*/supervise/ and /var/qmail/supervise/*/log/supervise/ and delete all the stuff found in those dirs, lock, status etc This will give you a clean start rebuild your symlinks, one at a time, checking carefully each time. ln -s /var/qmail/supervise/qmail-send /service/ look at it's log. note the date and does it look ok in the log something like status 0/30 ps ax or for more info ps auxwwwf you can watch a log with tail -f current leave the pop3ds service till last, it is not required to get the mail going use telnet to connect and test that a service is talking you'll get there! HTH -- ----------------- Bob Hutchinson Midwales dot com -----------------
