FS#67539 - [syslog-ng] 3.28.1-2 does not start
Attached to Project:
Arch Linux
Opened by Miha Verlic (fluke571) - Sunday, 09 August 2020, 21:53 GMT
Last edited by Florian Pritz (bluewind) - Saturday, 29 August 2020, 09:43 GMT
Opened by Miha Verlic (fluke571) - Sunday, 09 August 2020, 21:53 GMT
Last edited by Florian Pritz (bluewind) - Saturday, 29 August 2020, 09:43 GMT
|
Details
Description:
syslog-ng 3.28.1-2 deadlocks at start. Probably same bug as https://bugs.archlinux.org/task/65206 resurfaced again; downgrading libcap to 2.37 and syslog-ng to 3.28.1-1 helps. |
This task depends upon
Closed by Florian Pritz (bluewind)
Saturday, 29 August 2020, 09:43 GMT
Reason for closing: Fixed
Additional comments about closing: syslog-ng 3.28.1-3
Saturday, 29 August 2020, 09:43 GMT
Reason for closing: Fixed
Additional comments about closing: syslog-ng 3.28.1-3
```
$ logger -t test "Is /dev/log availble?"
logger: socket /dev/log: Connection refused
$ /bin/ls -l /dev/log
srw-rw-rw- 1 root root 0 Aug 12 06:17 /dev/log
```
Did you reboot after installing syslog-ng 3.28.1-3 ?
$ ls -l /dev/log
lrwxrwxrwx 1 root root 28 12 aug 15:56 /dev/log -> /run/systemd/journal/dev-log
$ ls -l /run/systemd/journal/dev-log
srw-rw-rw- 1 root root 0 12 aug 15:56 /run/systemd/journal/dev-log
$