Results 1 to 3 of 3

Thread: Calling journalctl failed

  1. #1

    Default Calling journalctl failed

    If I try to look at the systemd logs via Yast2, I get "Calling journalctl failed." How do I read the logs, and also, how can I tail them?

  2. #2
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,056
    Blog Entries
    14

    Default Re: Calling journalctl failed

    Quote Originally Posted by jarome View Post
    If I try to look at the systemd logs via Yast2, I get "Calling journalctl failed." How do I read the logs, and also, how can I tail them?
    Normally not my reply, but the best here:
    Code:
    man journalctl
    shows all the options you can use. The "-n10" would give only the last 10 lines.

    But, I suggest you rather get the Yast issue fixed, it should work.
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  3. #3
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,610

    Default Re: Calling journalctl failed

    Checked with my Leap 42.1 Laptop -- YaST -- "view systemd-journal" seems to be OK. (I only took a quick look and a quick wander through the possibly options.)

    Is the (systemd) journal running? (Not a Leap 42.1 view -- this a 13.2 view):
    Code:
     # systemctl status systemd-journald.service systemd-journald.socket systemd-journal-flush.service
    systemd-journald.service - Journal Service
       Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
       Active: active (running) since Do 2016-07-21 08:42:33 CEST; 2h 46min ago
         Docs: man:systemd-journald.service(8)
               man:journald.conf(5)
     Main PID: 455 (systemd-journal)
       Status: "Processing requests..."
       CGroup: /system.slice/systemd-journald.service
               └─455 /usr/lib/systemd/systemd-journald
    
    Jul 21 08:42:33 xxx systemd-journal[455]: Runtime journal is using 8.0M (max allowed 399.0M, trying to leave …99.0M).
    Jul 21 08:42:33 xxx systemd-journal[455]: Runtime journal is using 8.0M (max allowed 399.0M, trying to leave …99.0M).
    Jul 21 08:42:33 xxx systemd-journal[455]: Journal started
    Jul 21 08:42:34 xxx systemd-journal[455]: Permanent journal is using 464.0M (max allowed 1.9G, trying to leav… 1.9G).
    Jul 21 08:42:35 xxx systemd-journal[455]: Time spent on flushing to /var is 900.483ms for 1151 entries.
    
    systemd-journald.socket - Journal Socket
       Loaded: loaded (/usr/lib/systemd/system/systemd-journald.socket; static)
       Active: active (running) since Do 2016-07-21 08:42:32 CEST; 2h 46min ago
         Docs: man:systemd-journald.service(8)
               man:journald.conf(5)
       Listen: /run/systemd/journal/stdout (Stream)
               /run/systemd/journal/socket (Datagram)
               /dev/log (Datagram)
    
    Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
    
    systemd-journal-flush.service - Trigger Flushing of Journal to Persistent Storage
       Loaded: loaded (/usr/lib/systemd/system/systemd-journal-flush.service; static)
       Active: inactive (dead) since Do 2016-07-21 08:42:34 CEST; 2h 46min ago
         Docs: man:systemd-journald.service(8)
               man:journald.conf(5)
      Process: 717 ExecStart=/usr/bin/systemctl kill --kill-who=main --signal=SIGUSR1 systemd-journald.service (code=exited, status=0/SUCCESS)
     Main PID: 717 (code=exited, status=0/SUCCESS)
    
    Jul 21 08:42:34 xxx systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
    Jul 21 08:42:34 xxx systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
    Hint: Some lines were ellipsized, use -l to show in full.
     #
    What are the settings in "/etc/systemd/journald.conf"?
    • Assuming a separate "/var" partition or a "BtrFS" partition, IMHO for non-commercial users only the following settings are needed: "Seal=no"; "ForwardToSyslog=no".

Posting Permissions

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