da-popb4smtp stopped after update

F

Freddy

Verified User
Joined
Apr 14, 2016
Messages
119
A few days ago one of my servers noticed me about the process da-popb4smtp which had stopped working. I looked into it and found that it was not service but just a process being run by DirectAdmin. I don't know how this process is started or restarted and could not find any documentation about restarting it, so I just executed the file directly which seems to fix the problem.

A few days later (today) I have two more servers with the exact same problem. This makes me think that something is wrong. I found the following in the messages log:

Code: 
May 17 21:32:10 srv07 directadmin[3403988]: starting auto-updating    current-commit=ef029e9290a15af5cfb41b4a72804aeff23c1c25 current-version=1.648 latest-commit=b3525e60c30da803e6710c4a3badb838b5b70601 latest-version=1.649
May 17 21:32:11 srv07 dbus-daemon[791]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.5079895' (uid=0 pid=1094556 comm="timedatectl ")
May 17 21:32:11 srv07 systemd[1]: Starting System clock and RTC settings service...
May 17 21:32:11 srv07 dbus-daemon[791]: [system] Successfully activated service 'org.freedesktop.timedate1'
May 17 21:32:11 srv07 systemd[1]: Started System clock and RTC settings service.
May 17 21:32:12 srv07 systemd[1]: Reloading.
May 17 21:32:12 srv07 systemd[1]: /usr/lib/systemd/system/irqbalance.service:6: Unknown lvalue 'ConditionCPUs' in section 'Unit'
May 17 21:32:12 srv07 systemd[1]: Stopping POP before SMTP daemon...
May 17 21:32:12 srv07 systemd[1]: da-popb4smtp.service: Succeeded.
May 17 21:32:12 srv07 systemd[1]: Stopped POP before SMTP daemon.
May 17 21:32:12 srv07 systemd[1]: Reloading.
May 17 21:32:12 srv07 systemd[1]: /usr/lib/systemd/system/irqbalance.service:6: Unknown lvalue 'ConditionCPUs' in section 'Unit'
May 17 21:32:12 srv07 systemd[1]: Starting dnf makecache...
May 17 21:32:12 srv07 directadmin[3403988]: auto-update complete      current-commit=ef029e9290a15af5cfb41b4a72804aeff23c1c25 current-version=1.648 latest-commit=b3525e60c30da803e6710c4a3badb838b5b70601 latest-version=1.649
May 17 21:32:12 srv07 systemd[1]: Stopping DirectAdmin Web Control Panel...
May 17 21:32:12 srv07 directadmin[3403988]: waiting for legacy sub-process to terminate error=wait: no child processes
May 17 21:32:12 srv07 systemd[1]: directadmin.service: Succeeded.
May 17 21:32:12 srv07 systemd[1]: Stopped DirectAdmin Web Control Panel.
May 17 21:32:12 srv07 systemd[1]: directadmin.service: Found left-over process 1094758 (build) in control group while starting unit. Ignoring.
May 17 21:32:12 srv07 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 17 21:32:12 srv07 systemd[1]: directadmin.service: Found left-over process 1094962 (build) in control group while starting unit. Ignoring.
May 17 21:32:12 srv07 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 17 21:32:12 srv07 systemd[1]: directadmin.service: Found left-over process 1094963 (spamd) in control group while starting unit. Ignoring.
May 17 21:32:12 srv07 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 17 21:32:12 srv07 systemd[1]: directadmin.service: Found left-over process 1094964 (grep) in control group while starting unit. Ignoring.
May 17 21:32:12 srv07 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 17 21:32:12 srv07 systemd[1]: directadmin.service: Found left-over process 1094965 (awk) in control group while starting unit. Ignoring.
May 17 21:32:12 srv07 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
May 17 21:32:12 srv07 systemd[1]: Starting DirectAdmin Web Control Panel...
May 17 21:32:13 srv07 directadmin[1094966]: license updated successfully
May 17 21:32:13 srv07 systemd[1]: Started DirectAdmin Web Control Panel.

It looks like DirectAdmin is updating itself and restarting the popb4stmp daemon. And although it reports success it actually is not running any more. I restarted DirectAdmin itself but it does not restart popb4smtp. So now I have two questions.

  1. What is the restart procedure for popb4stmp?
  2. Please fix the updater that causes this problem so my other servers do not get the same problem.
 
cjd said:
As far as I know the service is no longer required as of 1.649, it's functionality is supposed to be part of the DA binary now.

Version 1.649 | Directadmin Docs

DirectAdmin Knowledge Base
docs.directadmin.com
Click to expand...
That could be a good reason to stop the process after an update. Thanks for the link. I should update my server monitoring according to this.

My question now is if manually starting /usr/local/directadmin/da-popb4smtp messes things up?
 
Two services trying to do the same thing could cause a conflict.
 
@fln @smtalk Maybe one of the DA staff can shed some light on this. If it's no longer required it probably should be removed to eliminate confusion, unless it's still needed for some purpose.
 
You must log in or register to reply here.
Back
Top