Timeline for /dev/log is a socket not a symbolic link
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 27 at 5:46 | comment | added | Boogeyman | @ChesterGillon On the problematic system the output of systemctl status systemd-journald-dev-log.socket is Failed to restart systemd-journald-dev-log.socket: Unit not found. | |
| May 25 at 9:30 | comment | added | Chester Gillon | On the problematic system (a) what is the output of systemctl status systemd-journald-dev-log.socket (b) does sudo systemctl restart systemd-journald-dev-log.socket then allow logger "test" to work? These debugging steps were suggested by systemctl restart systemd-journald-dev-log.socket, albeit that was based on Ubuntu 20.04. | |
| May 25 at 8:58 | comment | added | Boogeyman | @ChesterGillon when i use logger "test" it gives logger: socket /dev/log: Connection refused | |
| May 25 at 8:40 | comment | added | Chester Gillon | On an AlmaLinux 8.10 (i.e. RHEL compatible) system (a) /dev/log is a symbolic link to /run/systemd/journal/dev-log (b) /run/systemd/journal/dev-log is a socket. According to en.wikipedia.org/wiki/Systemd#Adoption RHEL 7 will also be using systemd. What problem is caused by having /dev/log a socket as opposed to a symbolic link to a a socket? | |
| May 25 at 8:02 | comment | added | Boogeyman | @StephenKitt yes | |
| May 25 at 7:34 | comment | added | Stephen Kitt | You mention RHEL 7.9 for one of the systems — are the others running RHEL 8? | |
| May 25 at 7:00 | comment | added | Steffen Ullrich | See unix.stackexchange.com/questions/464361/examining-dev-log - basically it is about your system using systemd or not. | |
| S May 25 at 6:57 | review | First questions | |||
| May 25 at 7:04 | |||||
| S May 25 at 6:57 | history | asked | Boogeyman | CC BY-SA 4.0 |