pfSense

I have a problem that is similar to #16478 but is not the same because the SIGABRT reported there does not occur.

1. Environment
   - pfSense Version: 2.8.1-RELEASE
   - System Uptime: 67 days (other installations with the same problem have between 23 and 81 days)
   - Hardware: Intel Atom C3758, 16 GiB RAM, 8 cores (other installations are on a Celeron N2930 and a VM on an Epyc 9124, respectively)
2. Symptoms (compare to #16478)
   - syslogd processes a message from cron that it is starting newsyslog, receives a SIGHUP probably from newsyslog, then exits
   - syslogd does not restart
3. Evidence
   - No dmesg output showing a crash, hence probably a regular error exit.
   - The end of a ktrace of the running syslogd, starting just before the cron message, is attached. Note in particular the message that syslogd itself attempts to log, but fails, at the very end.

These syslogds are configured to forward logs to a remote server. Problems started after upgrading to 2.8.1; I initially identified them as #16362 because the timing was suspicious and applied the workaround suggested there. That did not help, or rather I suspect that I had both problems at once and since adding #16362's firewall rules only the newsyslog-related cause remains.