I am trying to understand why a reboot takes over five minutes on my system. Looking at the pfSense system log I can see that there is a large gap in log entries between the syslogd stopping and restarting.
Apr 19 22:29:33 kernel pflog0: promiscuous mode disabled
Apr 19 22:29:33 syslogd kernel boot file is /boot/kernel/kernel
Apr 19 22:25:04 syslogd exiting on signal 15
Apr 19 22:25:04 reboot 54300 rebooted by root
That's a four minute gap!
I hooked up a monitor to the system and can see a lot of logging on the console which doesn't get logged in the syslog, but unfortunately I can't get the serial console to work to log everything permanently.This screenshot shows the majority of the time being taken up by wireguard establishing tunnels, one at the time, and I have quite a few...
52ea93fc-a36e-42a5-a348-8b975c5dfd44-image.png
I can see the log entries in the screenshot later in the syslog when they are all dumped in there, together with other boot messages but they all get the same timestamp:
Apr 19 22:29:33 kernel wg5: changing name to 'tun_wg6'
Apr 19 22:29:33 kernel tun_wg5: link state changed to UP
Apr 19 22:29:33 kernel wg4: changing name to 'tun_wg5'
Apr 19 22:29:33 kernel [fib_algo] inet.0 (bsearch4#39) rebuild_fd_flm: switching algo to radix4_lockless
Apr 19 22:29:33 kernel tun_wg4: link state changed to UP
Apr 19 22:29:33 kernel wg3: changing name to 'tun_wg4'
Apr 19 22:29:33 kernel tun_wg2: link state changed to UP
Apr 19 22:29:33 kernel wg2: changing name to 'tun_wg2'
Apr 19 22:29:33 kernel pflog0: promiscuous mode enabled
Apr 19 22:29:33 kernel igb2: link state changed to UP
I would like syslogd to start earlier to capture these events, with correct time stamps. Is there a trick/hack to force syslogd to start earlier in the boot process? What could be the reason why ir's not starting earlier?