Summary: | Panic while kill -9 syslogd | ||||||
---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | Peter Eriksson <pen> | ||||
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||
Status: | Closed Overcome By Events | ||||||
Severity: | Affects Only Me | CC: | pi | ||||
Priority: | --- | ||||||
Version: | 12.2-RELEASE | ||||||
Hardware: | amd64 | ||||||
OS: | Any | ||||||
Attachments: |
|
Description
Peter Eriksson
2021-10-11 22:29:06 UTC
Created attachment 228602 [details]
procstat -kk, ps and some vmstat log output just before the panic
Adding a tar.gz file containing some "procstat -kka", "ps auxwww" and various "vmstat" outputs captured just a minute before the panic/reboot in case it would help in providing some clues...
It seems the syslogd processes is blocking in the kernel at a "pipe_write": # egrep syslogd /var/log/sys/15:10/procstat-kk-a.log 9212 101640 syslogd - mi_switch+0xd4 sleepq_catch_signals+0x403 sleepq_wait_sig+0xf _sleep+0x1de pipe_write+0x583 dofilewrite+0xb0 sys_write+0xc0 amd64_syscall+0x387 fast_syscall_common+0xf8 Looking at our other servers I notice that syslogd has frozen on more than one of them causing thousands of defunct processes, and it seems to have happened at the time of a log rotate. Hmm... |