Inspecting logs
-
Hi,
one of my pfsense 1.2.3 box is behaving strangely since a couple of days. It seems it is frozen after almost 24 hours of perfect working. Rebooting the machine, everything goes fine again. I'd like to have some advice about which log can I inspect in order to find out what is the problem (I suspect an hardware problem).Thanks
-
Have you check your syslogs yet ?
-
I've checked the system.log but it does not contain any useful information, I mean, nothing before the freeze and only message from the boot and further. What I am searching for is a way to inspect what happened before the server get frozen.
-
You'd have to setup a syslog server and send the logs there. The logs are wiped on reboot, though sometimes if you get lucky the "dmesg" command can read some older kernel message buffer entries from the previous boot.
-
You'd have to setup a syslog server and send the logs there. The logs are wiped on reboot, though sometimes if you get lucky the "dmesg" command can read some older kernel message buffer entries from the previous boot.
It seems to me this is a feature of pfsense not present in FreeBSD. Is there any good reason why not using something like newsyslog?
-
It seems to me this is a feature of pfsense not present in FreeBSD. Is there any good reason why not using something like newsyslog?
They're kept in RAM to have consistency between embedded and full versions, can't use normal FreeBSD logging on nanobsd.
