Also, I forgot these:
# ps aux |grep tcpserver
vpopmail 787 0.0 0.0 4416 852 ? S 10:55 0:00
/usr/bin/tcpserver -v -R -H -l localhost.localdomain -x
/etc/tcprules.d/tcp.smtp.cdb -c 100 -u 89 -g 89 0 587
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
vpopmail 789 0.0 0.0 6540 1568 ? S 10:55 0:00
/usr/bin/tcpserver -v -R -H -l localhost.localdomain -x
/etc/tcprules.d/tcp.smtp.cdb -c 100 -u 89 -g 89 0 smtp /usr/bin/spamdyke
--config-file /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd
/home/vpopmail/bin/vchkpw /bin/true
vpopmail 790 0.0 0.0 4416 864 ? S 10:55 0:00
/usr/bin/tcpserver -v -R -H -l localhost.localdomain -x
/etc/tcprules.d/tcp.smtp.cdb -c 100 -u 89 -g 89 0 465
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
root 56811 0.0 0.0 12144 1144 pts/0 S+ 11:18 0:00 grep
--color=auto tcpserver
# ps aux |grep qmail-send
qmails 785 0.0 0.0 8664 964 ? S 10:55 0:00 qmail-send
kill -9 787 789 790 785
On 4/13/2023 10:35 AM, Jaime Lerner wrote:
Thank you! That fixed it. Silly me...not thinking of just restarting
the processes from the get-go. :)
*From: *Eric Broch <ebr...@whitehorsetc.com>
*Reply-To: *<qmailtoaster-list@qmailtoaster.com>
*Date: *Thursday, April 13, 2023 at 11:05 AM
*To: *<qmailtoaster-list@qmailtoaster.com>
*Subject: *Re: [qmailtoaster] Problems starting or restarting qmail
[root@localhost ~]# ps aux |grep multilog
qmaill 1025356 0.4 0.0 4260 832 pts/1 S 08:59 0:00
/usr/bin/multilog t s1000000 n100 /var/log/qmail/send
qmaill 1025358 0.4 0.0 4260 932 pts/1 S 08:59 0:00
/usr/bin/multilog t s1000000 n100 /var/log/qmail/smtp
qmaill 1025360 0.6 0.0 4260 928 pts/1 S 08:59 0:00
/usr/bin/multilog t s1000000 n100 /var/log/qmail/smtps
qmaill 1025364 0.4 0.0 4260 936 pts/1 S 08:59 0:00
/usr/bin/multilog t s1000000 n100 /var/log/qmail/submission
root 1025445 0.0 0.0 12144 1164 pts/1 S+ 08:59 0:00 grep
--color=auto multilog (grep application, ignore)
[root@localhost ~]# ps aux |grep supervise
root 1025349 0.0 0.0 4248 1232 pts/1 S 08:59 0:00
supervise send
root 1025350 0.0 0.0 4248 940 pts/1 S 08:59 0:00
supervise log
root 1025351 0.0 0.0 4248 936 pts/1 S 08:59 0:00
supervise smtp
root 1025352 0.0 0.0 4248 932 pts/1 S 08:59 0:00
supervise log
root 1025353 0.0 0.0 4248 840 pts/1 S 08:59 0:00
supervise smtps
root 1025354 0.0 0.0 4248 840 pts/1 S 08:59 0:00
supervise log
root 1025361 0.0 0.0 4248 840 pts/1 S 08:59 0:00
supervise submission
root 1025362 0.0 0.0 4248 932 pts/1 S 08:59 0:00
supervise log
root 1025635 0.0 0.0 12144 1160 pts/1 S+ 08:59 0:00 grep
--color=auto supervise (grep application, ignore)
# kill -9 1025356 1025358 1025360 1025364 1025349 1025350 1025351
1025352 1025353 1025354 1025361 1025362
On 4/13/2023 8:20 AM, Jaime Lerner wrote:
I keep getting the below as a response. Is there something I can
do to fix this without just rebooting the server? I’m just a
little wary of doing that when something doesn’t seem to be
running right – I’d rather fix it than hope a reboot will do it.
If I run a “qmailctl stop” then the errors go away and when I
check it, everything is up and running ... but if I try to start
or restart I get the following. I think it never actually stops is
the problem?
* Restarting qmail-smtpd.
[root@mail ~]# supervise: fatal: unable to acquire
send/supervise/lock: temporary failure
supervise: fatal: unable to acquire log/supervise/lock: temporary
failure
supervise: fatal: unable to acquire log/supervise/lock: temporary
failure
supervise: fatal: unable to acquire log/supervise/lock: temporary
failure
supervise: fatal: unable to acquire submission/supervise/lock:
temporary failure
supervise: fatal: unable to acquire smtp/supervise/lock: temporary
failure
