pidfile doesn't exist but it's started via systemd
Description
Description
Details
Details
- Difficulty level
- Normal (likely a few hours)
- Version
- 1.3
- Why the issue appeared?
- Will be filled on close
- Is it a breaking change?
- Unspecified (possibly destroys the router)
- Issue type
- Bug (incorrect behavior)
Event Timeline
Comment Actions
After looking into this, the problem seems bigger than originally thought. If the syslog config is being removed from the config the syslog.py script is called and syslog stopped. However if the system is rebooted the init system starts syslog and the config is not calling the script since there is no 'system syslog' node in the config. systemctl disable rsyslog doesn't work some type of depend unit is starting it during reboot.
Comment Actions
syslog is required by multiple targets and logs journald messages, stopping it works at the first commit, but the dependencies will start is automatically after reboot. the vyos config is being removed from rsyslog.d but the default rsyslog.conf will be used, which logs daemon, emerg (to console) and auth failures and would have to be changed in vyos-build if required.