[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Syslog/Rsyslog/Systemctl issue

Deleted the folder, restarted and back to square 1.

--
❯ systemctl --failed
  UNIT                            LOAD   ACTIVE SUB    DESCRIPTION
● dbus.socket                     loaded failed failed D-Bus System Message Bus Socket
● syslog.socket                   loaded failed failed Syslog Socket
● systemd-fsckd.socket            loaded failed failed fsck to fsckd communication Socket
● systemd-journald-audit.socket   loaded failed failed Journal Audit Socket
● systemd-journald-dev-log.socket loaded failed failed Journal Socket (/dev/log)
● systemd-journald.socket         loaded failed failed Journal Socket
● systemd-udevd-control.socket    loaded failed failed udev Control Socket
● systemd-udevd-kernel.socket     loaded failed failed udev Kernel Socket
● uuidd.socket                    loaded failed failed UUID daemon activation 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.
9 loaded units listed.
--

--
❯ ls /run/systemd/journal
ls: cannot access '/run/systemd/journal': No such file or directory
--

To make it works again I had to:
- mount /sys/fs/selinux -o remount,ro
- reinstall again "systemd systemd-sysv libsystemd0 dbus-user-session"
- start all failed systemd services

Still can't these 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.
--

But now I have journalctl giving me recent logs !
That's a starter.

So when I try to start them I'm getting this:
--
❯ systemctl start systemd-udevd-control.socket
Job failed. See "journalctl -xe" for details.

Feb 02 14:40:14 shax systemd[1]: systemd-udevd-control.socket: Socket service systemd-udevd.service already active, refusing.
Feb 02 14:40:14 shax systemd[1]: Failed to listen on udev Control Socket.
░░ Subject: A start job for unit systemd-udevd-control.socket has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit systemd-udevd-control.socket has finished with a failure.
░░
░░ The job identifier is 5423 and the job result is failed.
--

--
❯ systemctl start systemd-udevd-kernel.socket
Job failed. See "journalctl -xe" for details.

Feb 02 14:41:13 shax systemd[1]: systemd-udevd-kernel.socket: Socket service systemd-udevd.service already active, refusing.
Feb 02 14:41:13 shax systemd[1]: Failed to listen on udev Kernel Socket.
░░ Subject: A start job for unit systemd-udevd-kernel.socket has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit systemd-udevd-kernel.socket has finished with a failure.
░░
░░ The job identifier is 5431 and the job result is failed.
--

Le 02/02/2023 à 12:58, songbird a écrit :
Freyja wrote:
...

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 --


  if you are not concerned about keeping the last journals for
any reason i would remove the entire directory and then reboot.
if you do want them back them up and then remove that directory 
and try it again from a fresh reboot.


  songbird

Reply to: