Summary: | app-admin/syslog-ng: reload by logrotate can fail due to config version upgrade | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andriy Utkin (RETIRED) <andrey_utkin> |
Component: | Current packages | Assignee: | Tomáš Mózes <hydrapolic> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andriy Utkin (RETIRED)
2021-11-26 12:37:41 UTC
Started to get cron errors about this a month ago, finally figured its time to get to the bottom of this and found this... anyway instead of syslog-ng restart i went with: if [ -s "/run/syslog-ng.pid" ] ; then /bin/kill -HUP $(cat "/run/syslog-ng.pid") fi i will see with weekly rotate if its fixed or not :) kill -HUP does not work, still get whiny emails about auth.log on logrotate. I thought it's a good practice to call something like restart-services after @world upgrades. You may run into trouble without doing so. |