You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
syslog-ng fails to start at boot if you use the IP address of the ethernet interface (static IP address):
source s_udp { udp(ip(10.1.1.1) port(514)); };
After boot, if you manually start syslog-ng service, it starts with no problems:
service syslog-ng start
If you change the IP address to 0.0.0.0, the service starts at boot with no problems. So I think the network interface is up but the IP address is not already bind to the interface.
Describe the bug
I think the problem is in $network dependency. It dont check if the IP address is bind to the ethernet interface. From the init.d script:;
To reproduce
List the steps required to reproduce the issue.
Expected behaviour
Add a clear and concise description of what you expected to happen.
Actual behaviour
Add a clear and concise description of what actually happened.
System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
Which OS and version (cat /etc/rpi-issue)?
Raspberry Pi reference 2018-11-13
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 7e0c786c641ba15990b5662f092c106beed40c9f, stage2
Which firmware version (vcgencmd version)?
Mar 27 2019 15:45:53
Copyright (c) 2012 Broadcom
version 2e98b31d18547962e564bdf88e57b3df7085c29b (clean) (release) (start)
syslog-ng fails to start at boot if you use the IP address of the ethernet interface (static IP address):
source s_udp { udp(ip(10.1.1.1) port(514)); };
After boot, if you manually start syslog-ng service, it starts with no problems:
service syslog-ng start
If you change the IP address to 0.0.0.0, the service starts at boot with no problems. So I think the network interface is up but the IP address is not already bind to the interface.
Describe the bug
I think the problem is in $network dependency. It dont check if the IP address is bind to the ethernet interface. From the init.d script:;
Required-Stop: $local_fs $network $time $remote_fs
To reproduce
List the steps required to reproduce the issue.
Expected behaviour
Add a clear and concise description of what you expected to happen.
Actual behaviour
Add a clear and concise description of what actually happened.
System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
Which OS and version (
cat /etc/rpi-issue
)?Raspberry Pi reference 2018-11-13
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 7e0c786c641ba15990b5662f092c106beed40c9f, stage2
Which firmware version (
vcgencmd version
)?Mar 27 2019 15:45:53
Copyright (c) 2012 Broadcom
version 2e98b31d18547962e564bdf88e57b3df7085c29b (clean) (release) (start)
Which kernel version (
uname -a
)?Linux leonidas 4.19.42-v7+ system freeze while unplug r8152 usb2network card #1219 SMP Tue May 14 21:20:58 BST 2019 armv7l GNU/Linux
Logs
If applicable, add the relevant output from
dmesg
or similar.service syslog-ng status
● syslog-ng.service - System Logger Daemon
Loaded: loaded (/lib/systemd/system/syslog-ng.service; enabled; vendor preset: enable
Active: failed (Result: exit-code) since Wed 2019-07-03 01:09:42 CEST; 6min ago
Docs: man:syslog-ng(8)
Process: 535 ExecStart=/usr/sbin/syslog-ng -F $SYSLOGNG_OPTS (code=exited, status=2)
Main PID: 535 (code=exited, status=2)
Status: "Starting up... (Wed Jul 3 01:09:42 2019"
Jul 03 01:09:42 leonidas systemd[1]: syslog-ng.service: Failed with result 'exit-code'.
Jul 03 01:09:42 leonidas systemd[1]: syslog-ng.service: Service hold-off time over, sche
Jul 03 01:09:42 leonidas systemd[1]: Stopped System Logger Daemon.
Jul 03 01:09:42 leonidas systemd[1]: syslog-ng.service: Start request repeated too quick
Jul 03 01:09:42 leonidas systemd[1]: Failed to start System Logger Daemon.
Jul 03 01:09:42 leonidas systemd[1]: syslog-ng.service: Unit entered failed state.
Jul 03 01:09:42 leonidas systemd[1]: syslog-ng.service: Failed with result 'exit-code'.
lines 1-15/15 (END)
Additional context
Add any other relevant context for the problem.
Hope you will understand
The text was updated successfully, but these errors were encountered: