• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Magicspam and systemd log entries every 5 minutes

Oliver Marugg

Oliver Marugg

Basic Pleskian
Hi

I set a fresh server with of Ubuntu 16.04.2 LTS‬ latest updates, with Plesk Onyx Version 17.5.3 Update #4 Webhost edition+Hostpack.

Everything works smooth, but every 5 mInutes I have got following sequence in my log, sometime with backupmgr and always with the magicspam queue cleaner.

First I thought it would be refernce to this discussion-found bug here. I did the workaround 2, but stil.
Any ideas or hints for me? Greets oliver

Code: 
May  2 21:15:01 HOSTNAME systemd[1]: Created slice User Slice of root.
May  2 21:15:01 HOSTNAME systemd[1]: Starting User Manager for UID 0...
May  2 21:15:01 HOSTNAME systemd[1]: Started Session 3 of user root.
May  2 21:15:01 HOSTNAME systemd[1]: Started Session 2 of user root.
May  2 21:15:01 HOSTNAME systemd[3975]: Reached target Timers.
May  2 21:15:01 HOSTNAME systemd[3975]: Reached target Sockets.
May  2 21:15:01 HOSTNAME systemd[3975]: Reached target Paths.
May  2 21:15:01 HOSTNAME systemd[3975]: Reached target Basic System.
May  2 21:15:01 HOSTNAME systemd[3975]: Reached target Default.
May  2 21:15:01 HOSTNAME systemd[3975]: Startup finished in 10ms.
May  2 21:15:01 HOSTNAME systemd[1]: Started User Manager for UID 0.
May  2 21:15:01 HOSTNAME CRON[3985]: (root) CMD (/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/magicspam/scripts/ms_clean_queue.php')
May  2 21:15:01 HOSTNAME CRON[3986]: (root) CMD ([ -x /opt/psa/admin/sbin/backupmng ] && /opt/psa/admin/sbin/backupmng >/dev/null 2>&1)
May  2 21:15:01 HOSTNAME systemd[1]: Stopping User Manager for UID 0...
May  2 21:15:01 HOSTNAME systemd[3975]: Reached target Shutdown.
May  2 21:15:01 HOSTNAME systemd[3975]: Starting Exit the Session...
May  2 21:15:01 HOSTNAME systemd[3975]: Stopped target Default.
May  2 21:15:01 HOSTNAME systemd[3975]: Stopped target Basic System.
May  2 21:15:01 HOSTNAME systemd[3975]: Stopped target Paths.
May  2 21:15:01 HOSTNAME systemd[3975]: Stopped target Timers.
May  2 21:15:01 HOSTNAME systemd[3975]: Stopped target Sockets.
May  2 21:15:01 HOSTNAME systemd[3975]: Received SIGRTMIN+24 from PID 4000 (kill).
May  2 21:15:01 HOSTNAME systemd[1]: Stopped User Manager for UID 0.
May  2 21:15:01 HOSTNAME systemd[1]: Removed slice User Slice of root.

Or such as

Code: 
May  2 21:25:01 HOSTNAME systemd[1]: Created slice User Slice of root.
May  2 21:25:01 HOSTNAME systemd[1]: Starting User Manager for UID 0...
May  2 21:25:01 HOSTNAME systemd[1]: Started Session 6 of user root.
May  2 21:25:01 HOSTNAME systemd[4526]: Reached target Sockets.
May  2 21:25:01 HOSTNAME systemd[4526]: Reached target Paths.
May  2 21:25:01 HOSTNAME systemd[4526]: Reached target Timers.
May  2 21:25:01 HOSTNAME systemd[4526]: Reached target Basic System.
May  2 21:25:01 HOSTNAME systemd[4526]: Reached target Default.
May  2 21:25:01 HOSTNAME systemd[4526]: Startup finished in 10ms.
May  2 21:25:01 HOSTNAME systemd[1]: Started User Manager for UID 0.
May  2 21:25:01 HOSTNAME CRON[4534]: (root) CMD (/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/magicspam/scripts/ms_clean_queue.php')
May  2 21:25:01 HOSTNAME systemd[1]: Stopping User Manager for UID 0...
May  2 21:25:01 HOSTNAME systemd[4526]: Stopped target Default.
May  2 21:25:01 HOSTNAME systemd[4526]: Reached target Shutdown.
May  2 21:25:01 HOSTNAME systemd[4526]: Starting Exit the Session...
May  2 21:25:01 HOSTNAME systemd[4526]: Stopped target Basic System.
May  2 21:25:01 HOSTNAME systemd[4526]: Stopped target Paths.
May  2 21:25:01 HOSTNAME systemd[4526]: Stopped target Sockets.
May  2 21:25:01 HOSTNAME systemd[4526]: Stopped target Timers.
May  2 21:25:01 HOSTNAME systemd[4526]: Received SIGRTMIN+24 from PID 4546 (kill).
May  2 21:25:01 HOSTNAME systemd[1]: Stopped User Manager for UID 0.
May  2 21:25:01 HOSTNAME systemd[1]: Removed slice User Slice of root.
 
Hi Oliver Marugg,

Oliver Marugg said:
May 2 21:25:01 HOSTNAME CRON[4534]: (root) CMD (/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/magicspam/scripts/ms_clean_queue.php')
Click to expand...
This cronjob runs EVERY minute. All fine here!

Oliver Marugg said:
May 2 21:15:01 HOSTNAME CRON[3986]: (root) CMD ([ -x /opt/psa/admin/sbin/backupmng ] && /opt/psa/admin/sbin/backupmng >/dev/null 2>&1)
Click to expand...
This cronjobs runs EVERY 15 minutes. All fine here!


Oliver Marugg said:
May 2 21:15:01 HOSTNAME systemd[1]: Created slice User Slice of root.
May 2 21:15:01 HOSTNAME systemd[1]: Starting User Manager for UID 0...
May 2 21:15:01 HOSTNAME systemd[1]: Started Session 3 of user root.
May 2 21:15:01 HOSTNAME systemd[1]: Started Session 2 of user root.
May 2 21:15:01 HOSTNAME systemd[3975]: Reached target Timers.
May 2 21:15:01 HOSTNAME systemd[3975]: Reached target Sockets.
May 2 21:15:01 HOSTNAME systemd[3975]: Reached target Paths.
May 2 21:15:01 HOSTNAME systemd[3975]: Reached target Basic System.
May 2 21:15:01 HOSTNAME systemd[3975]: Reached target Default.
May 2 21:15:01 HOSTNAME systemd[3975]: Startup finished in 10ms.
May 2 21:15:01 HOSTNAME systemd[1]: Started User Manager for UID 0.
Click to expand...
Oliver Marugg said:
May 2 21:15:01 HOSTNAME systemd[1]: Stopping User Manager for UID 0...
May 2 21:15:01 HOSTNAME systemd[3975]: Reached target Shutdown.
May 2 21:15:01 HOSTNAME systemd[3975]: Starting Exit the Session...
May 2 21:15:01 HOSTNAME systemd[3975]: Stopped target Default.
May 2 21:15:01 HOSTNAME systemd[3975]: Stopped target Basic System.
May 2 21:15:01 HOSTNAME systemd[3975]: Stopped target Paths.
May 2 21:15:01 HOSTNAME systemd[3975]: Stopped target Timers.
May 2 21:15:01 HOSTNAME systemd[3975]: Stopped target Sockets.
May 2 21:15:01 HOSTNAME systemd[3975]: Received SIGRTMIN+24 from PID 4000 (kill).
May 2 21:15:01 HOSTNAME systemd[1]: Stopped User Manager for UID 0.
May 2 21:15:01 HOSTNAME systemd[1]: Removed slice User Slice of root.
Click to expand...
Oliver Marugg said:
May 2 21:25:01 HOSTNAME systemd[1]: Created slice User Slice of root.
May 2 21:25:01 HOSTNAME systemd[1]: Starting User Manager for UID 0...
May 2 21:25:01 HOSTNAME systemd[1]: Started Session 6 of user root.
May 2 21:25:01 HOSTNAME systemd[4526]: Reached target Sockets.
May 2 21:25:01 HOSTNAME systemd[4526]: Reached target Paths.
May 2 21:25:01 HOSTNAME systemd[4526]: Reached target Timers.
May 2 21:25:01 HOSTNAME systemd[4526]: Reached target Basic System.
May 2 21:25:01 HOSTNAME systemd[4526]: Reached target Default.
May 2 21:25:01 HOSTNAME systemd[4526]: Startup finished in 10ms.
May 2 21:25:01 HOSTNAME systemd[1]: Started User Manager for UID 0.
Click to expand...
Oliver Marugg said:
May 2 21:25:01 HOSTNAME systemd[1]: Stopping User Manager for UID 0...
May 2 21:25:01 HOSTNAME systemd[4526]: Stopped target Default.
May 2 21:25:01 HOSTNAME systemd[4526]: Reached target Shutdown.
May 2 21:25:01 HOSTNAME systemd[4526]: Starting Exit the Session...
May 2 21:25:01 HOSTNAME systemd[4526]: Stopped target Basic System.
May 2 21:25:01 HOSTNAME systemd[4526]: Stopped target Paths.
May 2 21:25:01 HOSTNAME systemd[4526]: Stopped target Sockets.
May 2 21:25:01 HOSTNAME systemd[4526]: Stopped target Timers.
May 2 21:25:01 HOSTNAME systemd[4526]: Received SIGRTMIN+24 from PID 4546 (kill).
May 2 21:25:01 HOSTNAME systemd[1]: Stopped User Manager for UID 0.
May 2 21:25:01 HOSTNAME systemd[1]: Removed slice User Slice of root.
Click to expand...
Not related to Plesk components. Pls. contact your system administrator or your hosting provider to fix this issue with the vendor package "systemd" / "systemd-sysv" ( and/or possible related/depending packages ).
 
Last edited by a moderator:
Many thanks. I understood for both cornjobs, but for that Pleks-unrelated systemd thing I really do not any idea what to do. Just to metion it was a fresh OS+Plesk 17.5.3 install and no backup from other plesk instance., Perhaps anyone could give me a hint (PM?).
 
Hi Oliver Marugg,

Oliver Marugg said:
Perhaps anyone could give me a hint
Click to expand...
I would start to investigate your boot - logs, followed by re-installing all related/depending packages to "systemd". Pls. check as well other logs in "/var/log" for issues/failures/problems from all current services, because the current log - entries don't point to the possible service with issues/errors/problems.

I would compare the timestamp from
Code: 
Received SIGRTMIN+24 from PID
with entries in other logs, which might point you to a service with issues/errors/problems.
 
I found out that this cronjob will be started every 5 minutes, at 5, 10 and so on.
Code: 
" (root) CMD (/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/magicspam/scripts/ms_clean_queue.php')"

I did not find any entries in the boot logs concerning other processes or other errors/failure etc. in other log files.

For testing purposes I just removed one and then both cronjobs from above crontab. And those systemd entries arent released anymore. Then I switched back and after 5 minutes the whole sstemd bunch from above is released again and shown in syslog.
 
Hi Oliver Marugg,

you should consider another FRESH install instead of digging around, because you recently stated:
Oliver Marugg said:
I set a fresh server with of Ubuntu 16.04.2 LTS‬ latest updates
Click to expand...
Sometimes such installation routines ( with templates from the hosting company ) didn't finish as expected... shouldn't happen... but still do happen. ;)
From my point of view, it will be much faster and less time-consuming, if you try to reproduce the very same issue/error/problem, instead of searching for the current root cause and this should throw you back to your initial installation process. :)
 
Oliver Marugg said:
I found out that this cronjob will be started every 5 minutes, at 5, 10 and so on.
Code: 
" (root) CMD (/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/magicspam/scripts/ms_clean_queue.php')"

I did not find any entries in the boot logs concerning other processes or other errors/failure etc. in other log files.

For testing purposes I just removed one and then both cronjobs from above crontab. And those systemd entries arent released anymore. Then I switched back and after 5 minutes the whole sstemd bunch from above is released again and shown in syslog.
Click to expand...


Hello Oliver,

Just for your information, ms_clean_queue.php script on your server, configured to run every 5 minutes is used for checking and cleaning up the rate-limiter operations queue. Related logs such as the one below can be safely ignored.

Code: 
" (root) CMD (/opt/psa/admin/bin/php -dauto_prepend_file=sdk.php '/opt/psa/admin/plib/modules/magicspam/scripts/ms_clean_queue.php')"

We hope this information helps.

Thank you for choosing MagicSpam for Plesk for your anti-spam protection.
 
Just to keep you informed. I did 3 installations on bare metal, on vms (vmware and proxmox) with the base of Ubuntu 16.04.2, after each reinstall (tried with different install medias etc, different hardware). Also latest installation is on a vm and after several days of operation this behaviour will occur again.

UFHH01 said:
Hi Oliver Marugg,
From my point of view, it will be much faster and less time-consuming, if you try to reproduce the very same issue/error/problem, instead of searching for the current root cause and this should throw you back to your initial installation process. :)
Click to expand...
Yes, you are definitely right, but I can no reinstall once a week;-)

I suppose this is the normal behaviour of 2 cronjobs with systemd under Ubuntu 16.04.2, I can not explain anything else, but it fills the syslog in a unexpected manner (there is enough diskspace...).

UPDATE: All services, plesk and magicspam work as expected.
 
Last edited:
Hello Oliver,

Thank you for the update.

Please let us know if you have any further updates or if you have any questions about MagicSpam on your system.

Thank you.
 
You must log in or register to reply here.

Similar threads

J
Resolved Logs and proFtpd
Replies
5
Views
562
JuanCar
J
L
Question Many log-entrys after update to Debian 12 and Plesk 18.0.61
Replies
2
Views
477
Larian
L
J
Resolved 25: Connection timed out - Almalinux 9.4 x86_64 | 18.0.61.1
Replies
2
Views
917
josemanuuxd
J
K
Issue Docker containers don't start after plesk/extension upgrades
Replies
0
Views
1K
kassi
K
Ankebut
Resolved PHP 8.1 Another FPM instance seems to already listen on [...] php-fpm.sock
2
Replies
26
Views
13K
Ankebut
Ankebut
Back
Top