Re: Syslog/Rsyslog/Systemctl issue

[Freyja <debian@sioban.net>]

    Ok,
    
    Instead of just creating the folders, I've reinstalled some
    packages:
    
    --
    ❯ apt-get install --reinstall  systemd systemd-sysv libsystemd0
    dbus-user-session
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    0 upgraded, 0 newly installed, 4 reinstalled, 0 to remove and 3 not
    upgraded.
    Need to get 376 kB/5,090 kB of archives.
    After this operation, 0 B of additional disk space will be used.
    Get:1 http://ftp.fr.debian.org//debian bullseye/main amd64
    libsystemd0 amd64 247.3-7+deb11u1 [376 kB]
    Fetched 376 kB in 1s (645 kB/s)
    (Reading database ... 204034 files and directories currently
    installed.)
    Preparing to unpack .../libsystemd0_247.3-7+deb11u1_amd64.deb ...
    Unpacking libsystemd0:amd64 (247.3-7+deb11u1) over (247.3-7+deb11u1)
    ...
    Setting up libsystemd0:amd64 (247.3-7+deb11u1) ...
    (Reading database ... 204034 files and directories currently
    installed.)
    Preparing to unpack .../systemd_247.3-7+deb11u1_amd64.deb ...
    Unpacking systemd (247.3-7+deb11u1) over (247.3-7+deb11u1) ...
    Setting up systemd (247.3-7+deb11u1) ...
    (Reading database ... 204034 files and directories currently
    installed.)
    Preparing to unpack .../systemd-sysv_247.3-7+deb11u1_amd64.deb ...
    Unpacking systemd-sysv (247.3-7+deb11u1) over (247.3-7+deb11u1) ...
    Preparing to unpack
    .../dbus-user-session_1.12.24-0+deb11u1_amd64.deb ...
    Unpacking dbus-user-session (1.12.24-0+deb11u1) over
    (1.12.24-0+deb11u1) ...
    Setting up systemd-sysv (247.3-7+deb11u1) ...
    Setting up dbus-user-session (1.12.24-0+deb11u1) ...
    Processing triggers for libc-bin (2.31-13+deb11u5) ...
    Processing triggers for man-db (2.9.4-2) ...
    Processing triggers for dbus (1.12.24-0+deb11u1) ...
    Scanning processes...
    Scanning candidates...
    Scanning processor microcode...
    Scanning linux images...
    
    Running kernel seems to be up-to-date.
    
    The processor microcode seems to be up-to-date.
    
    Restarting services...
     systemctl restart clamav-daemon.service ossec.service
    smartmontools.service squid.service ssh.service tor@default.service
    transmission-daemon.service
    Service restarts being deferred:
     systemctl restart unattended-upgrades.service
    
    No containers need to be restarted.
    
    No user sessions are running outdated binaries.
    --
    
    It helped!
    The folders have been recreated:
    
    --
    ❯ ls -la /run/systemd/journal/socket
    srw-rw-rw- 1 root root 0 Feb  1 15:44 /run/systemd/journal/socket
    
    ❯ ls -lad /run/systemd/journal/
    drwxr-xr-x 2 root root 120 Feb  1 15:44 /run/systemd/journal/
    
    --
    
    I was even able to start most of the failing process but two:
    
    --
    ❯ systemctl --failed
      UNIT                         LOAD   ACTIVE SUB    DESCRIPTION
    ● systemd-udevd-control.socket loaded failed failed udev Control
    Socket
    ● systemd-udevd-kernel.socket  loaded failed failed udev Kernel
    Socket
    
    LOAD   = Reflects whether the unit definition was properly loaded.
    ACTIVE = The high-level unit activation state, i.e. generalization
    of SUB.
    SUB    = The low-level unit activation state, values depend on unit
    type.
    2 loaded units listed.
    --
    
    However journalctl still stucks on 24th Oct:
    --
    ❯ 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 --
    --

Le 01/02/2023 à 15:32, Charles Curley a écrit :

> On Wed, 1 Feb 2023 13:26:58 +0100
> Freyja <debian@sioban.net> wrote:
>
> > For /run/systemd/journal/socket this is another story.
> > The folder journal does not exist at all.
> >       
> Well, that could be a problem. On one of my computers:
>
> root@jhegaala:~# ll /run/systemd/journal/socket
> srw-rw-rw- 1 root root 0 Jan 25 09:55 /run/systemd/journal/socket=
> root@jhegaala:~# ll -d /run/systemd/journal/
> drwxr-xr-x 3 root root 200 Jan 25 09:55 /run/systemd/journal//
> root@jhegaala:~# 
>
> You might try rebuilding the directory /run/systemd/journal/ with
> appropriate permissions and manually restarting the relevant services.
> (The services should rebuild the sockets for you.)
>
>