Actions
Bug #16478
open
syslogd crashes with SIGABRT during newsyslog rotation
Status:
New
Priority:
Normal
Assignee:
-
Category:
System Logs
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.8.1
Affected Architecture:
amd64
Description
- Environment
- pfSense Version: 2.8.1-RELEASE
- System Uptime: 32 days
- Hardware: Intel Xeon E5-2630L v3, 16GB RAM, 32 CPUs
- Symptoms
- syslogd crashes with signal 6 (SIGABRT)
- Occurs during newsyslog rotation when log files exceed 500KB
- No core dump generated despite crash
- After crash/restart, syslogd loses file descriptor to `/var/log/system.log`
- Evidence
- dmesg output showing crash:
```
pid 92645 (syslogd), jid 0, uid 0: exited on signal 6 (no core dump - other error)
```
- Last log entry before crash:
```
Oct 10 12:33:00 pfSense-RM-MASTER newsyslog62411: logfile turned over due to size>500K
```
- File descriptor missing after crash:
```bash
- system.log exists but not open by syslogd
lsof -p $(pgrep syslogd | head -1) | grep system.log
(no output)
```
- Impact
- System logs not written to disk after crash
- Loss of diagnostic information
- Silent failure - process appears running but doesn't function correctly
- Reproduction
- System running normally for extended period (weeks)
- newsyslog triggers automatic log rotation when files exceed size threshold
- syslogd crashes with SIGABRT during rotation
- Process restarts but doesn't properly reopen log files
- Workaround
Manual restart of syslogd:
```bash
killall syslogd
/usr/sbin/syslogd -O rfc3164 -s -c -c -l /var/dhcpd/var/run/log -P /var/run/syslog.pid -f /etc/syslog.conf
```
- Additional Information
This appears to be related to log rotation handling in syslogd. The crash with SIGABRT suggests an assertion failure or abort() call, possibly due to race condition or improper file handle management during newsyslog operations.
No data to display
Actions