FedoraForum.org - Fedora Support Forums and Community
Results 1 to 10 of 10
  1. 27th February 2015, 11:35 PM #1
    zimon
    zimon is offline Registered User
    Join Date
    Sep 2004
    Posts
    351
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question systemd flooding system log every 5 minutes. What is wrong?

    This has been going on since fedup from F20 to F21.

    I have kdm enabled and I have logged in from that either to LXDE or MATE. And journald is getting those lines from systemd every 5 minutes.

    # journalctl -b 0 -t systemd

    See what happens every 5 minutes from the end of the log:
    http://ur1.ca/jte44

    Code:
    # journalctl -b 0 -t systemd
...
Feb 27 23:55:02 localhost systemd[24119]: Stopped target Default.
Feb 27 23:55:02 localhost systemd[24119]: Stopping Basic System.
Feb 27 23:55:02 localhost systemd[24119]: Stopped target Basic System.
Feb 27 23:55:02 localhost systemd[24119]: Stopping Paths.
Feb 27 23:55:02 localhost systemd[24119]: Stopped target Paths.
Feb 27 23:55:02 localhost systemd[24119]: Stopping Timers.
Feb 27 23:55:02 localhost systemd[24119]: Stopped target Timers.
Feb 27 23:55:02 localhost systemd[24119]: Stopping Sockets.
Feb 27 23:55:02 localhost systemd[24119]: Stopped target Sockets.
Feb 27 23:55:02 localhost systemd[24119]: Starting Shutdown.
Feb 27 23:55:02 localhost systemd[24119]: Reached target Shutdown.
Feb 27 23:55:02 localhost systemd[24119]: Starting Exit the Session...
Feb 27 23:55:02 localhost systemd[24119]: Received SIGRTMIN+24 from PID 24156 (kill).
Feb 27 23:55:02 localhost systemd[24124]: pam_unix(systemd-user:session): session closed for user root
Feb 27 23:55:02 localhost systemd[1]: Stopped User Manager for UID 0.
Feb 27 23:55:02 localhost systemd[1]: Stopping user-0.slice.
Feb 27 23:55:02 localhost systemd[1]: Removed slice user-0.slice.
Feb 28 00:00:01 localhost systemd[1]: Starting user-0.slice.
Feb 28 00:00:01 localhost systemd[1]: Created slice user-0.slice.
Feb 28 00:00:01 localhost systemd[1]: Starting User Manager for UID 0...
Feb 28 00:00:01 localhost systemd[1]: Starting Session 400 of user root.
Feb 28 00:00:01 localhost systemd[1]: Started Session 400 of user root.
Feb 28 00:00:01 localhost systemd[25221]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 28 00:00:01 localhost systemd[25221]: Starting Paths.
Feb 28 00:00:01 localhost systemd[25221]: Reached target Paths.
Feb 28 00:00:01 localhost systemd[25221]: Starting Timers.
Feb 28 00:00:01 localhost systemd[25221]: Reached target Timers.
Feb 28 00:00:01 localhost systemd[25221]: Starting Sockets.
Feb 28 00:00:01 localhost systemd[25221]: Reached target Sockets.
Feb 28 00:00:01 localhost systemd[25221]: Starting Basic System.
Feb 28 00:00:01 localhost systemd[25221]: Reached target Basic System.
Feb 28 00:00:01 localhost systemd[25221]: Starting Default.
Feb 28 00:00:01 localhost systemd[25221]: Reached target Default.
Feb 28 00:00:01 localhost systemd[25221]: Startup finished in 8ms.
Feb 28 00:00:01 localhost systemd[1]: Started User Manager for UID 0.
Feb 28 00:00:01 localhost systemd[1]: Stopping User Manager for UID 0...
Feb 28 00:00:01 localhost systemd[25221]: Stopping Default.
Feb 28 00:00:01 localhost systemd[25221]: Stopped target Default.
Feb 28 00:00:01 localhost systemd[25221]: Stopping Basic System.
Feb 28 00:00:01 localhost systemd[25221]: Stopped target Basic System.
Feb 28 00:00:01 localhost systemd[25221]: Stopping Paths.
Feb 28 00:00:01 localhost systemd[25221]: Stopped target Paths.
Feb 28 00:00:01 localhost systemd[25221]: Stopping Timers.
Feb 28 00:00:01 localhost systemd[25221]: Stopped target Timers.
Feb 28 00:00:01 localhost systemd[25221]: Stopping Sockets.
Feb 28 00:00:01 localhost systemd[25221]: Stopped target Sockets.
Feb 28 00:00:01 localhost systemd[25221]: Starting Shutdown.
Feb 28 00:00:01 localhost systemd[25221]: Reached target Shutdown.
Feb 28 00:00:01 localhost systemd[25221]: Starting Exit the Session...
Feb 28 00:00:01 localhost systemd[25221]: Received SIGRTMIN+24 from PID 25243 (kill).
Feb 28 00:00:01 localhost systemd[25228]: pam_unix(systemd-user:session): session closed for user root
Feb 28 00:00:01 localhost systemd[1]: Stopped User Manager for UID 0.
Feb 28 00:00:01 localhost systemd[1]: Stopping user-0.slice.
Feb 28 00:00:01 localhost systemd[1]: Removed slice user-0.slice.
Feb 28 00:01:01 localhost systemd[1]: Starting user-0.slice.
Feb 28 00:01:01 localhost systemd[1]: Created slice user-0.slice.
Feb 28 00:01:01 localhost systemd[1]: Starting User Manager for UID 0...
Feb 28 00:01:01 localhost systemd[1]: Starting Session 401 of user root.
Feb 28 00:01:01 localhost systemd[1]: Started Session 401 of user root.
Feb 28 00:01:01 localhost systemd[25543]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 28 00:01:01 localhost systemd[25543]: Starting Paths.
Feb 28 00:01:01 localhost systemd[25543]: Reached target Paths.
Feb 28 00:01:01 localhost systemd[25543]: Starting Timers.
Feb 28 00:01:01 localhost systemd[25543]: Reached target Timers.
Feb 28 00:01:01 localhost systemd[25543]: Starting Sockets.
Feb 28 00:01:01 localhost systemd[25543]: Reached target Sockets.
Feb 28 00:01:01 localhost systemd[25543]: Starting Basic System.
Feb 28 00:01:01 localhost systemd[25543]: Reached target Basic System.
Feb 28 00:01:01 localhost systemd[25543]: Starting Default.
Feb 28 00:01:01 localhost systemd[25543]: Reached target Default.
Feb 28 00:01:01 localhost systemd[25543]: Startup finished in 9ms.
Feb 28 00:01:01 localhost systemd[1]: Started User Manager for UID 0.
Feb 28 00:04:16 localhost systemd[1]: Stopping User Manager for UID 0...
Feb 28 00:04:16 localhost systemd[25543]: Stopping Default.
Feb 28 00:04:16 localhost systemd[25543]: Stopped target Default.
Feb 28 00:04:16 localhost systemd[25543]: Stopping Basic System.
Feb 28 00:04:16 localhost systemd[25543]: Stopped target Basic System.
Feb 28 00:04:16 localhost systemd[25543]: Stopping Paths.
Feb 28 00:04:16 localhost systemd[25543]: Stopped target Paths.
Feb 28 00:04:16 localhost systemd[25543]: Stopping Timers.
Feb 28 00:04:16 localhost systemd[25543]: Stopped target Timers.
Feb 28 00:04:16 localhost systemd[25543]: Stopping Sockets.
Feb 28 00:04:16 localhost systemd[25543]: Stopped target Sockets.
Feb 28 00:04:16 localhost systemd[25543]: Starting Shutdown.
Feb 28 00:04:16 localhost systemd[25543]: Reached target Shutdown.
Feb 28 00:04:16 localhost systemd[25543]: Starting Exit the Session...
Feb 28 00:04:16 localhost systemd[25543]: Received SIGRTMIN+24 from PID 26337 (kill).
Feb 28 00:04:16 localhost systemd[25547]: pam_unix(systemd-user:session): session closed for user root
Feb 28 00:04:16 localhost systemd[1]: Stopped User Manager for UID 0.
Feb 28 00:04:16 localhost systemd[1]: Stopping user-0.slice.
Feb 28 00:04:16 localhost systemd[1]: Removed slice user-0.slice.
Feb 28 00:05:01 localhost systemd[1]: Starting user-0.slice.
Feb 28 00:05:01 localhost systemd[1]: Created slice user-0.slice.
Feb 28 00:05:01 localhost systemd[1]: Starting User Manager for UID 0...
Feb 28 00:05:01 localhost systemd[1]: Starting Session 402 of user root.
Feb 28 00:05:01 localhost systemd[1]: Started Session 402 of user root.
Feb 28 00:05:01 localhost systemd[26623]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
Feb 28 00:05:01 localhost systemd[26623]: Starting Paths.
Feb 28 00:05:01 localhost systemd[26623]: Reached target Paths.
Feb 28 00:05:01 localhost systemd[26623]: Starting Timers.
Feb 28 00:05:01 localhost systemd[26623]: Reached target Timers.
Feb 28 00:05:01 localhost systemd[26623]: Starting Sockets.
Feb 28 00:05:01 localhost systemd[26623]: Reached target Sockets.
Feb 28 00:05:01 localhost systemd[26623]: Starting Basic System.
Feb 28 00:05:01 localhost systemd[26623]: Reached target Basic System.
Feb 28 00:05:01 localhost systemd[26623]: Starting Default.
Feb 28 00:05:01 localhost systemd[26623]: Reached target Default.
Feb 28 00:05:01 localhost systemd[26623]: Startup finished in 9ms.
Feb 28 00:05:01 localhost systemd[1]: Started User Manager for UID 0.
Feb 28 00:05:02 localhost systemd[1]: Stopping User Manager for UID 0...
Feb 28 00:05:02 localhost systemd[26623]: Stopping Default.
Feb 28 00:05:02 localhost systemd[26623]: Stopped target Default.
Feb 28 00:05:02 localhost systemd[26623]: Stopping Basic System.
Feb 28 00:05:02 localhost systemd[26623]: Stopped target Basic System.
Feb 28 00:05:02 localhost systemd[26623]: Stopping Paths.
Feb 28 00:05:02 localhost systemd[26623]: Stopped target Paths.
Feb 28 00:05:02 localhost systemd[26623]: Stopping Timers.
Feb 28 00:05:02 localhost systemd[26623]: Stopped target Timers.
Feb 28 00:05:02 localhost systemd[26623]: Stopping Sockets.
Feb 28 00:05:02 localhost systemd[26623]: Stopped target Sockets.
Feb 28 00:05:02 localhost systemd[26623]: Starting Shutdown.
Feb 28 00:05:02 localhost systemd[26623]: Reached target Shutdown.
Feb 28 00:05:02 localhost systemd[26623]: Starting Exit the Session...
Feb 28 00:05:02 localhost systemd[26623]: Received SIGRTMIN+24 from PID 26647 (kill).
Feb 28 00:05:02 localhost systemd[26630]: pam_unix(systemd-user:session): session closed for user root
Feb 28 00:05:02 localhost systemd[1]: Stopped User Manager for UID 0.
Feb 28 00:05:02 localhost systemd[1]: Stopping user-0.slice.
Feb 28 00:05:02 localhost systemd[1]: Removed slice user-0.slice.
    Every 5 minutes:
    Code:
    # journalctl -b 0 -t systemd | head -2
-- Logs begin at Sat 2014-11-08 14:02:06 EET, end at Sat 2015-02-28 00:40:55 EET. --
Feb 26 19:47:15 localhost systemd[1]: systemd 216 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)

# journalctl -b 0 -t systemd |grep "Stopping Default" | wc
    337    2359   18775
    So it has happened 337 times since yesterday, it has been ~28 hours.
    Code:
    28/337*60
4.98516320474777448060
    => every 5 minutes.


    systemd is something I am not really familiar with yet, so some hints which to check and how to debug would be great!
    Last edited by zimon; 27th February 2015 at 11:48 PM.
    Reply With Quote Reply With Quote
  2. 28th February 2015, 01:44 AM #2
    PabloTwo's Avatar
    PabloTwo
    PabloTwo is offline "Fedora User" T-Shirt Winner
    Join Date
    Mar 2007
    Location
    Seville, FL
    Posts
    8,919
    Mentioned
    39 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    I don't know how to resolve your particular journald issue (system log), but if it's over active and eating up too much hdd space in the process, you at least have a way to limit how much disk space it uses. Thanks to Marko for this tip. I've set mine to 300MB.
    Code:
    $ grep SystemMax /etc/systemd/journald.conf
SystemMaxUse=300M
#SystemMaxFileSize=
    Code:
    $ du -sh /var/log/journal/
329M	/var/log/journal/
    Reply With Quote Reply With Quote
  3. 28th February 2015, 02:51 AM #3
    zimon
    zimon is offline Registered User
    Join Date
    Sep 2004
    Posts
    351
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    Code:
    # du -sh /var/log/journal/
4.1G    /var/log/journal/
    Did now:
    SystemMaxUse=1G
    SystemMaxFileSize=1G

    Code:
    # killall -HUP systemd
...
Feb 28 03:45:50 myhost systemd[1]: Configuration file /usr/lib/systemd/system/auditd.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Feb 28 03:47:32  systemd[1]: Received SIGHUP from PID 10006 (killall).
Feb 28 03:47:32  systemd[1]: Reloading.
Feb 28 03:47:32  systemd[3333]: Received SIGHUP from PID 10006 (killall).
Feb 28 03:47:32  systemd[3333]: Reloading.
Feb 28 03:47:32  systemd[31285]: Received SIGHUP from PID 10006 (killall).
Feb 28 03:47:32  systemd[31285]: Reloading.
    Code:
    # du -sh /var/log/journal/
4.1G    /var/log/journal/
    Edit:

    Code:
    # killall -HUP systemd-journald
# du -sh /var/log/journal/
2.1G    /var/log/journal/
    Last edited by zimon; 28th February 2015 at 03:11 AM.
    Reply With Quote Reply With Quote
  4. 28th February 2015, 11:39 AM #4
    zimon
    zimon is offline Registered User
    Join Date
    Sep 2004
    Posts
    351
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    Found it. Sometimes it just works to write a problem up to have ideas.

    I had a cron job for root:

    Code:
    # crontab  -l
0-59/5 * * * * ( date -Is ; sensors ) >> /root/sensors/sensors-log.txt
    Have collected CPU and other temperatures aiming to make a long term graph later and see how it relates to different things on the system and surroundings (room temperature).

    I commented that cron job away, and systemd stopped flooding every 5 minutes.

    How to do this other way so systemd wouldn't log so thoroughly root's cron jobs?

    P.S.
    Does someone know any Linux application which could do that what I am trying, collect sensors data 24/7 and draw long term graphs?
    Reply With Quote Reply With Quote
  5. 28th February 2015, 06:25 PM #5
    marko
    marko is offline Administrator
    Join Date
    Jun 2004
    Location
    Maryland, US
    Posts
    15,377
    Mentioned
    186 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    Quote Originally Posted by zimon
    Found it. Sometimes it just works to write a problem up to have ideas.

    I had a cron job for root:

    Code:
    # crontab  -l
0-59/5 * * * * ( date -Is ; sensors ) >> /root/sensors/sensors-log.txt
    Have collected CPU and other temperatures aiming to make a long term graph later and see how it relates to different things on the system and surroundings (room temperature).

    I commented that cron job away, and systemd stopped flooding every 5 minutes.

    How to do this other way so systemd wouldn't log so thoroughly root's cron jobs?

    P.S.
    Does someone know any Linux application which could do that what I am trying, collect sensors data 24/7 and draw long term graphs?
    option 1, don't use root to do that. I suspect the problem is that the
    journal system and audit are way more stringent in how they police the
    root account than a user.
    "sensors" works fine from a normal user account (on my machine I just lose one of the PCI Video card temp sensors,
    apparently it's only root accessible). Just make a crontab for your usual account user with the same setup but just point it to somewhere accessible to the user
    like a 'zimon' accessible dir under /var/tmp: (using 'zimon' as your normal account). Create a crontab for 'zimon' and put the same
    stuff in it as the root one but just point the redirection file to /var/tmp/sensors/sensors-log.txt
    Code:
    zimon$> crontab  -l
0-59/5 * * * * ( date -Is ; sensors ) >> /var/tmp/sensors/sensors-log.txt
    Option 2: use 'sensord', logging sensor data is what it's for, install the package lm_sensors-sensord
    and check the manual page for instructions: "man sensord" or there's also the page at http://www.lm-sensors.org/wiki/man/sensord
    Reply With Quote Reply With Quote
  6. 28th February 2015, 08:13 PM #6
    zimon
    zimon is offline Registered User
    Join Date
    Sep 2004
    Posts
    351
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    thanks.
    sensord (and RRD tools) seems to be just what I need. Had it already installed, but not in use.

    Code:
    # vim /etc/sysconfig/sensord
# ln -s /usr/lib/systemd/system/sensord.service /etc/systemd/system/multi-user.target.wants/
# systemctl start sensord
    '

    Also found this:
    http://oss.oetiker.ch/rrdtool-trac/w...MonitorScripts
    Reply With Quote Reply With Quote
  7. 1st March 2015, 03:14 PM #7
    zimon
    zimon is offline Registered User
    Join Date
    Sep 2004
    Posts
    351
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    sensord is producing even more gutter to system log if temperatures are probed every 5 minutes :-)

    Code:
    # journalctl -b 0 -t sensord|head -2
-- Logs begin at Sat 2014-11-08 14:02:06 EET, end at Sun 2015-03-01 16:05:01 EET. --
Feb 28 20:03:11 myhost sensord[20057]: Creating round robin database

# journalctl -b 0 -t sensord|tail -11
Mar 01 16:03:11 myhost sensord[20058]: Chip: acpitz-virtual-0
Mar 01 16:03:11 myhost sensord[20058]: Adapter: Virtual device
Mar 01 16:03:11 myhost sensord[20058]: temp1: 27.8 C
Mar 01 16:03:11 myhost sensord[20058]: temp2: 29.8 C
Mar 01 16:03:11 myhost sensord[20058]: Chip: coretemp-isa-0000
Mar 01 16:03:11 myhost sensord[20058]: Adapter: ISA adapter
Mar 01 16:03:11 myhost sensord[20058]: Physical id 0: 43.0 C
Mar 01 16:03:11 myhost sensord[20058]: Core 0: 35.0 C
Mar 01 16:03:11 myhost sensord[20058]: Core 1: 43.0 C
Mar 01 16:03:11 myhost sensord[20058]: Core 2: 40.0 C
Mar 01 16:03:11 myhost sensord[20058]: Core 3: 38.0 C

# journalctl -b 0 -t sensord|wc
    674    5643   38027
    SOLVED -> NOT SOLVED:

    How to configure journald or systemd to ignore sensord, or sensord not to send information to systemd?
    Last edited by zimon; 1st March 2015 at 03:44 PM.
    Reply With Quote Reply With Quote
  8. 1st March 2015, 06:39 PM #8
    Peter H.S.
    Peter H.S. is offline Registered User
    Join Date
    Oct 2004
    Posts
    107
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    Quote Originally Posted by zimon
    sensord is producing even more gutter to system log if temperatures are probed every 5 minutes :-)

    Code:
    # journalctl -b 0 -t sensord|head -2
-- Logs begin at Sat 2014-11-08 14:02:06 EET, end at Sun 2015-03-01 16:05:01 EET. --
Feb 28 20:03:11 myhost sensord[20057]: Creating round robin database

# journalctl -b 0 -t sensord|tail -11
Mar 01 16:03:11 myhost sensord[20058]: Chip: acpitz-virtual-0
Mar 01 16:03:11 myhost sensord[20058]: Adapter: Virtual device
Mar 01 16:03:11 myhost sensord[20058]: temp1: 27.8 C
Mar 01 16:03:11 myhost sensord[20058]: temp2: 29.8 C
Mar 01 16:03:11 myhost sensord[20058]: Chip: coretemp-isa-0000
Mar 01 16:03:11 myhost sensord[20058]: Adapter: ISA adapter
Mar 01 16:03:11 myhost sensord[20058]: Physical id 0: 43.0 C
Mar 01 16:03:11 myhost sensord[20058]: Core 0: 35.0 C
Mar 01 16:03:11 myhost sensord[20058]: Core 1: 43.0 C
Mar 01 16:03:11 myhost sensord[20058]: Core 2: 40.0 C
Mar 01 16:03:11 myhost sensord[20058]: Core 3: 38.0 C

# journalctl -b 0 -t sensord|wc
    674    5643   38027
    SOLVED -> NOT SOLVED:

    How to configure journald or systemd to ignore sensord, or sensord not to send information to systemd?

    Been a while since I used sensor, but AFAIK, you can choose to put the output in a round robin database (RRD) instead of logging to syslog. You can also make sensord ignore certain things like fan status etc., so they never get logged.

    Just checked the sensord(8) man page: use "--log-interval 0" to turn of syslog logging and "--rrd-interval 5m" to log to rdd every 5 minutes.
    Reply With Quote Reply With Quote
  9. 1st March 2015, 06:46 PM #9
    zimon
    zimon is offline Registered User
    Join Date
    Sep 2004
    Posts
    351
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    missed that from the man page. Reconfigured /etc/sysconfig/sensord and restarted. Let's see if it keeps quiet now and only goes to rrd-file.

    Edit:
    ok, works.

    Would think there has to be a way to filter something out from systemd-journald also not to fill (set quata) /var/log/journal
    ...like rsyslogd had.
    Last edited by zimon; 1st March 2015 at 08:34 PM.
    Reply With Quote Reply With Quote
  10. 9th March 2015, 12:03 AM #10
    marko
    marko is offline Administrator
    Join Date
    Jun 2004
    Location
    Maryland, US
    Posts
    15,377
    Mentioned
    186 Post(s)
    Tagged
    0 Thread(s)

    Re: systemd flooding system log every 5 minutes. What is wrong?

    Quote Originally Posted by zimon
    Would think there has to be a way to filter something out from systemd-journald also not to fill (set quata) /var/log/journal
    ...like rsyslogd had.
    I think there is, see "man journalctl" and "man systemd.journal-fields"

    see also

    https://access.redhat.com/documentat...e_Journal.html
    Last edited by marko; 9th March 2015 at 12:11 AM.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Similar Threads

  1. How does systemd shut down the system?
    By tom289332 in forum Using Fedora
    Replies: 0
    Last Post: 24th November 2012, 02:23 PM
  2. No desktop, system hangs 5 minutes after
    By Quanta in forum Using Fedora
    Replies: 10
    Last Post: 21st April 2005, 01:03 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules

User Tag List