On 14/12/16 13:14, Tony Nelson wrote:
On 16-12-13 19:27:21, Stephen Davies wrote:
On 14/12/16 02:03, Tony Nelson wrote:
On 16-12-13 02:49:53, Stephen Davies wrote:
I have no idea where the reference to
/var/spool/clientmqueue/sm-client.pid
comes from.
The pidfile should come from /etc/mail/submit.mc via /etc/mail/submit.cf
THANK YOU!!
That is indeed where /var/spool/clientmqueue/sm-client.pid looks to
come from.
However, after fixing that, the original sm-client now gives:
[root@mustang system]# systemctl start sm-client
Job for sm-client.service failed because a timeout was exceeded. See
"systemctl status sm-client.service" and "journalctl -xe" for details.
[root@mustang system]# systemctl status sm-client
● sm-client.service - Sendmail Mail Transport Client
Loaded: loaded (/usr/lib/systemd/system/sm-client.service; enabled;
vendor preset: disabled)
Active: failed (Result: timeout) since Wed 2016-12-14 10:52:25 ACDT; 4s ago
Process: 11022 ExecStart=/usr/sbin/sendmail -L sm-msp-queue -Ac
$SENDMAIL_OPTS $SENDMAIL_OPTARG (code=exited, status=0/SUCCESS)
Process: 11019 ExecStartPre=/etc/mail/make (code=exited, status=0/SUCCESS)
Process: 11013 ExecStartPre=/sbin/restorecon /run/sm-client.pid
(code=exited, status=0/SUCCESS)
Process: 11008 ExecStartPre=/bin/chown smmsp:smmsp /run/sm-client.pid
(code=exited, status=0/SUCCESS)
Process: 10989 ExecStartPre=/bin/touch /run/sm-client.pid (code=exited,
status=0/SUCCESS)
Dec 14 10:50:55 mustang.sdc.com.au systemd[1]: Starting Sendmail Mail
Transport Client...
Dec 14 10:50:55 mustang.sdc.com.au systemd[1]: sm-client.service: Failed to
read PID from file /run/sm-client.pid: Invalid argument
Dec 14 10:50:55 mustang.sdc.com.au sm-msp-queue[11024]: starting daemon
(8.15.1): queueing@01:00:00
Dec 14 10:50:55 mustang.sdc.com.au sm-msp-queue[11024]: unable to write pid
to /run/sm-client.pid: Permission denied
Dec 14 10:52:25 mustang.sdc.com.au systemd[1]: sm-client.service: Start
operation timed out. Terminating.
Dec 14 10:52:25 mustang.sdc.com.au systemd[1]: Failed to start Sendmail Mail
Transport Client.
Dec 14 10:52:25 mustang.sdc.com.au systemd[1]: sm-client.service: Unit
entered failed state.
Dec 14 10:52:25 mustang.sdc.com.au systemd[1]: sm-client.service: Failed
with result 'timeout'.
The process is definitely running as smmsp so should have write
access to the PID file.
As Ed says, check the ownership of the file, though the log claims that
it was set, and see what's in it.
FWIW, on my Fedora20 machine:
# systemctl status sm-client
sm-client.service - Sendmail Mail Transport Client
Loaded: loaded (/usr/lib/systemd/system/sm-client.service; enabled)
Active: active (running) since Sun 2016-12-11 21:43:30 EST; 1 day 23h ago
Process: 882 ExecStart=/usr/sbin/sendmail -L sm-msp-queue -Ac $SENDMAIL_OPTS
$SENDMAIL_OPTARG (code=exited, status=0/SUCCESS)
Process: 878 ExecStartPre=/etc/mail/make (code=exited, status=0/SUCCESS)
Process: 868 ExecStartPre=/sbin/restorecon /run/sm-client.pid (code=exited,
status=0/SUCCESS)
Process: 861 ExecStartPre=/bin/chown smmsp:smmsp /run/sm-client.pid
(code=exited, status=0/SUCCESS)
Process: 858 ExecStartPre=/bin/touch /run/sm-client.pid (code=exited,
status=0/SUCCESS)
Main PID: 887 (sendmail)
CGroup: /system.slice/sm-client.service
└─887 sendmail: Queue runner@01:00:00 for /var/spool/clientmqueue
Dec 11 21:43:30 master.lan systemd[1]: Failed to read PID from file
/run/sm-client.pid: Invalid argument
Dec 11 21:43:30 master.lan sm-msp-queue[887]: starting daemon (8.14.8):
queueing@01:00:00
Dec 11 21:43:30 master.lan systemd[1]: Started Sendmail Mail Transport Client.
# ll /run/sm-client.pid
-rw-r--r--. 1 smmsp smmsp 48 Dec 11 21:43 /run/sm-client.pid
# ps -ef | grep sendmail
root 856 1 0 Dec11 ? 00:00:12 sendmail: accepting connections
smmsp 887 1 0 Dec11 ? 00:00:00 sendmail: Queue
runner@01:00:00 for /var/spool/clientmqueue
root 9615 1833 0 21:41 pts/0 00:00:00 grep --color=auto sendmail
[root@master ~]# cat /run/sm-client.pid
887
/usr/sbin/sendmail -L sm-msp-queue -Ac -q1h
So "Failed to read PID" seems to be OK, but "unable to write pid" seems
bad.
I manually created an empty /run/sm-client.pid and set the ownership to
smmsp:smmsp and the ran systemctl.
It failed again as before but after the failure, /run/sm-client.pid did not exist.
What is actually trying to write/read the PID file?
If I run the sendmail command manually, no PID file is mentioned nor created.
Cheers,
Stephen
--
=============================================================================
Stephen Davies Consulting P/L Phone: 08-8177 1595
Adelaide, South Australia. Mobile:040 304 0583
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
