pfSense

Syslogd fails to fully start on boot,

This started over a month ago on April 17 it would appear (based on the latest timestamps), but I haven't been able to identify the cause yet.

From dmesg immediately following a boot:

coretemp0: <CPU On-Die Thermal Sensors> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
Failed to write core file for process syslogd (error 14)
pid 5900 (syslogd), uid 0: exited on signal 11
Failed to write core file for process syslogd (error 14)
pid 99492 (syslogd), uid 0: exited on signal 11
Failed to write core file for process syslogd (error 14)
pid 34050 (syslogd), uid 0: exited on signal 11

: df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ada0s1a 21G 1.1G 18G 5% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/md0 3.4M 124K 3.0M 4% /var/run
devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev

Attempting to run it manually crashes as well:

[2.2.2-RELEASE][root@jinn.cordite.atlagroup.com]/root: syslogd
syslogd: child pid 12313 exited on signal 11

I attempted patching with commit patch for cfda8861b93ef0a2daf2cc9ca2424200e45dd84f and it didn't make a difference.

Didn't see that #1284 was pertinent, but the symptoms are the same/similar.

The system appears to have a mix of ascii/data logs:

: file *
dansguardian: directory
dhcpd.log: ASCII text
dmesg.boot: ASCII text
filter.log: ASCII text
gateways.log: ASCII text
installer.log: ASCII text
ipsec.log: ASCII text
l2tps.log: data
lastlog: empty
lighttpd.log: data
ntp: directory
ntpd.log: ASCII text
openvpn.log: data
poes.log: data
portalauth.log: data
ppp.log: data
pptps.log: data
relayd.log: data
resolver.log: ASCII text
routing.log: ASCII text
suricata: directory
system.log: empty
system.log.old: ASCII text
userlog: ASCII text
utx.lastlogin: data
utx.log: data
vpn.log: data
wireless.log: data

Moving those logs aside, I'm then able to start syslogd:

: syslogd
/var/log: echo $?
0
: pgrep syslogd
20774