Description of problem: In log files the following entries show up: sm-client.service: Failed to parse PID from file /run/sm-client.pid: Invalid argument Is that because a content of /run/sm-client.pid looks somewhat like that? 10835 /usr/sbin/sendmail -L sm-msp-queue -Ac -q1h The second line is indeed not something I would expect in a pid file. Actually there is also a second complaint in logs which says: Can't open PID file /run/sendmail.pid (yet?) after start: No such file or directory That looks like a race because with this entry from "Jan 24 08:10:35" 'stat /run/sendmail.pid' gives: Access: 2019-01-24 08:10:35.699374598 -0700 Modify: 2019-01-24 08:10:35.698374600 -0700 Change: 2019-01-24 08:10:35.698374600 -0700 sendmail does start OK but the whole corresponding fragment from journal is as follows: Jan 24 08:10:35 ... systemd[1]: Starting Sendmail Mail Transport Agent... -- Subject: Unit sendmail.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sendmail.service has begun starting up. Jan 24 08:10:35 ... sendmail[10825]: starting daemon (8.15.2): SMTP+queueing@01:00:00 Jan 24 08:10:35 ... systemd[1]: sendmail.service: Can't open PID file /run/sendmail.pid (yet?) after start: No such file or directory Jan 24 08:10:35 ... systemd[1]: Started Sendmail Mail Transport Agent. -- Subject: Unit sendmail.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sendmail.service has finished starting up. -- -- The start-up result is done. Jan 24 08:10:35 ... systemd[1]: Starting Sendmail Mail Transport Client... -- Subject: Unit sm-client.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sm-client.service has begun starting up. Jan 24 08:10:35 ... sm-msp-queue[10835]: starting daemon (8.15.2): queueing@01:00:00 Jan 24 08:10:35 ... systemd[1]: sm-client.service: Failed to parse PID from file /run/sm-client.pid: Invalid argument Jan 24 08:10:35 ... systemd[1]: Started Sendmail Mail Transport Client. -- Subject: Unit sm-client.service has finished start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit sm-client.service has finished starting up. -- -- The start-up result is done. Version-Release number of selected component (if applicable): sendmail-8.15.2-29.fc29.x86_64 How reproducible: journal collects these complaints many times
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.