Bug #4352
closed2.2 syslogd exiting sig 15 when boot finishes
0%
Description
upgraded box from 2.1.5. syslogd now exits at boot/reboot and does not restart again. prevents ALL logs on the entire system from being generated. manually running syslogd from the command line to restart the process fixes the issue of no logs being generated..
Updated by Chris Buechler almost 10 years ago
- Status changed from New to Feedback
does it do that at every boot? could you share your config?
Updated by Mike Oxlong almost 10 years ago
Yes, it does it at every boot or reboot and started exactly after performing an in place upgrade from 2.1.5 release.
There are several issues present (which need other bug filings, but I can't keep the system running this way so I'm going to revert back to 2.1.5 for the time being.
What do you need from my config exactly and I'll supply it before I wipe the system...
Updated by Chris Buechler almost 10 years ago
I emailed you to see if we can setup a time that I can check out your system in general
Updated by Mike Oxlong almost 10 years ago
received email. will reply with access info...
Updated by James S over 9 years ago
Did you ever find a resolution to this? We're seeing the exact same behavior.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Closed
it's fixed in 2.2.1. this is actually a duplicate of #4393 which has the specific cause and commits that fixed.