If during a pfSense reboot you get one or more messages from syslog
about “operation not supported by device” on various log files, then they are likely corrupt.
I had this when a pfSense 2.4.x RELEASE version VM was accidentally power-cycled during initial setup.
A side effect was that no logs showed in the web UI either, nor would clog
on any file in the /var/log
directory.
The solution was to choose option 8
(Shell), then in the /var/log
directory, remove all files with extension .log
, then reboot.
Now the messages were gone and the web UI showed logs. clog /var/log/system.log
showed content as well.
Solution based on these posts:
- [WayBack] [SOLVED] pfSense SG-1000 lan-interface missing IP with snapshot 20171007
- [WayBack] pfsense on Hyper-v 2016 no system logs. (Resolved)
- [WayBack] Bug #4768: Operation not supported by device – pfSense – pfSense bugtracker (a simple reboot did NOT resolve the issue)
- [WayBack] Bug #7919: Logging not working – pfSense – pfSense bugtracker
–jeroen