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

Re: Syslog/Rsyslog/Systemctl issue



Hi everyone and for people dropping by having the same issue.

The problem is *solved* !!!! \o/

The issue was: missing /run/systemd/journal/socket
What solved the problem:
- apt-get install --reinstall  systemd systemd-sysv libsystemd0 dbus-user-session
- /run/systemd/journal/socket and /run/systemd/journal/ were re-created
- reboot

I'm not completely sure why it didn't work the first time, but now I don't have ANY failed services.

--
systemctl list-units --state failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
--

But it might also be linked with a kernel update

Many thanks to all people involved in this thread and sorry that it took me so long to answer, I was missing the energy to look deeper.
Today I just rebooted after a kernel update (5.10.0-20) and the problem was gone...

Le 03/02/2023 à 09:59, Freyja a écrit :
I need to look deeper in your recommendations, I will try them as soon as I can.

Le 02/02/2023 à 17:28, songbird a écrit :
debian-user@howorth.org.uk wrote:
...
Maybe it's worth asking on the systemd-devel mailing list?
  did you reinstall rsyslog?  did you purge the configs for it
(back them up if needed)?  when i remove a package i have been
having troubles with i often purge it instead of uninstalling
it.

  you may need to reboot after reinstalling systemd and/or 
rsyslog or any other parts.

  see my other note about what your /var/log/journal directory
should look like if you have that set up right for permissions.

  back up the files if you want to keep the old ones.  i'm not
sure the subdirectory in /var/log/journal will be recreated or
not but i think it will if it isn't there, if it is there and
empty the journald service should set up a new one.  note this
depends upon what setting you've got in your config files for
systemd.  i'm not sure if you've altered systemd configuration
files or not.

  note that reinstalling without purging will not necessarily
reset your configuration files.

  rsyslog files should show up in /var/log or where ever you 
put them.

  these are things i can think of trying.  sorry i've gotta
get going and won't be able to help more until later tonight.
hope you get it figured out before then.  :)


  songbird




Reply to: