Re: Syslog/Rsyslog/Systemctl issue

[debian@sioban.net]

    Hi max,
    
    "journalctl -e" ends the 24th of October.
    
    --
    Oct 24 14:14:33 shax systemd[1]: Stopped Update UTMP about System
    Boot/Shutdown.
    Oct 24 14:14:33 shax systemd[1]: systemd-tmpfiles-setup.service:
    Succeeded.
    Oct 24 14:14:33 shax systemd[1]: Stopped Create Volatile Files and
    Directories.
    Oct 24 14:14:33 shax systemd[1]: Stopping Flush Journal to
    Persistent Storage...
    --
    
    --
    ❯ journalctl -b
    -- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon
    2022-10-24 14:14:33 CEST. --
    -- No entries --
    --
    
    systemd-journald.service reports error but unclear :/
    
    --
    ❯ systemctl status systemd-journald.service
    ● systemd-journald.service - Journal Service
         Loaded: loaded (/lib/systemd/system/systemd-journald.service;
    static)
         Active: inactive (dead)
    TriggeredBy: ● systemd-journald-dev-log.socket
                 ● systemd-journald-audit.socket
                 ● systemd-journald.socket
           Docs: man:systemd-journald.service(8)
                 man:journald.conf(5)
    --
    
    --
    ❯ systemctl start systemd-journald.service
    A dependency job for systemd-journald.service failed. See
    'journalctl -xe' for details.
    --

Le 01/02/2023 à 11:05, Max Nikulin a écrit :

> On
>       31/01/2023 16:57, debian@sioban.net wrote:
>       
> > I'm contacting you because I'm clueless on
> >         what's happening.
> >         
> >         Basically my issue is I don't have logs anymore :/
> >         
> >       
>       ...
>       
> >  > systemctl start rsyslog.service
> >         
> >         A dependency job for rsyslog.service failed. See 'journalctl
> >         -xe' for details.
> >         
> >       
>       
> > ❯systemctl --failed
> >         
> >            UNIT                            LOAD   ACTIVE SUB   
> >         DESCRIPTION
> >         
> >       
>       ...
>       
> > ● systemd-journald.socket         loaded
> >         failed failed Journal Socket
> >         
> >       
>       
>       This line looks suspicious. I would ensure at first that journald
>       is running correctly. Rsyslog likely receives logs from journald.
>       
>       
>       Are logs available through the following commands (last entries
>       and for current boot)?
>       
>       
>       journalctl -e
>       
>       journalctl -b
>       
>       
>       Does
>       
>       
>       systemctl status systemd-journald.service
>       
>       
>       reports any errors?
>       
>       
>