[SOLVED] Ubuntu 16.04 LTS syslog flooded from systemd every other second

linumo · 10-27-2017, 02:23 AM

I have migrated my vServer with ubuntu 16.04 and plesk to a more powerful hardware.
I have aligned the setup of the old server and the new server and migrated my domains.
So far everything seems to work but I do see a vast of systemd messages in /var/log/syslog which I do not have on the old server.
Any clues on how I can troubleshoot the problem?

Code:

Oct 27 07:42:39 h2... systemd[19421]: Startup finished in 5ms.
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Default.
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Basic System.
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Timers.
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Sockets.
Oct 27 07:42:39 h2... systemd[19421]: Reached target Shutdown.
Oct 27 07:42:39 h2... systemd[19421]: Starting Exit the Session...
Oct 27 07:42:39 h2... systemd[19421]: Stopped target Paths.
Oct 27 07:42:39 h2... systemd[19421]: Received SIGRTMIN+24 from PID 19447 (kill).
Oct 27 07:42:40 h2... systemd[19468]: Reached target Paths.
Oct 27 07:42:40 h2... systemd[19468]: Reached target Timers.
Oct 27 07:42:40 h2... systemd[19468]: Reached target Sockets.
Oct 27 07:42:40 h2... systemd[19468]: Reached target Basic System.
Oct 27 07:42:40 h2... systemd[19468]: Reached target Default.
Oct 27 07:42:40 h2... systemd[19468]: Startup finished in 6ms.

syg00 · 10-27-2017, 07:45 PM

Got a (user) cron running every second ?.

linumo · 10-28-2017, 01:57 AM

Quote:

Originally Posted by syg00

Got a (user) cron running every second ?.

There is no CRON job running every other second.
As CRON also logs to syslog any evidence of CRON being the cause would be logged here too.

linumo · 10-29-2017, 12:55 AM

My apologies.
I found that in fact after a server move my surveillance system tried to contact the new server every second.
So it was a setup problem in my home environment and the log messages were just confusing me.