(clog), uid 0: exited on signal 11 (core dumped) again

Mr. Joe

Dear folks:

since yesterday I got this error and I don' t get the log on the pfSense 2.1 to further write entries which makes it impossible to judge on the operations.

First I thought it might have to do with the upgrade to 2.1.1. but after spending some hours, I put in the backup that I cloned from the drive, and it is still there. Most of the logs in /var/log are at 512144 bytes of file size, which I understood would be o.k. because they would be overwritten in a cycle.

Here is a ls from the directory

ls -la /var/log
total 18112
drwxr-xr-x 3 root wheel 512 Mar 9 19:33 .
drwxr-xr-x 26 root wheel 512 Mar 15 09:15 ..
-rw–----- 1 root wheel 512144 Apr 2 17:36 dhcpd.log
-rw-r--r-- 1 root wheel 7287 Apr 7 02:59 dmesg.boot
-rw------- 1 root wheel 0 Apr 5 17:05 filter.log
-rw------- 1 root wheel 512144 Mar 27 18:21 gateways.log
-rw------- 1 root wheel 30552 Mar 9 19:13 installer.log
-rw------- 1 root wheel 511488 Apr 5 16:17 ipsec.log
-rw------- 1 root wheel 512144 Mar 9 19:07 l2tps.log
-rw-r--r-- 1 root wheel 56028 Apr 5 16:53 lastlog
-rw------- 1 root wheel 512144 Mar 9 19:07 lighttpd.log
drwxr-xr-x 2 root wheel 512 Mar 9 19:32 ntp
-rw------- 1 root wheel 512144 Apr 2 19:41 ntpd.log
-rw------- 1 root wheel 512144 Mar 9 19:07 openvpn.log
-rw------- 1 root wheel 512144 Mar 9 19:07 poes.log
-rw------- 1 root wheel 512144 Mar 18 22:36 portalauth.log
-rw------- 1 root wheel 512144 Mar 9 19:07 ppp.log
-rw------- 1 root wheel 512144 Mar 9 19:07 pptps.log
-rw------- 1 root wheel 512144 Mar 9 19:07 relayd.log
-rw------- 1 root wheel 512144 Apr 2 17:36 resolver.log
-rw------- 1 root wheel 512144 Mar 9 19:07 routing.log
-rw------- 1 root wheel 512144 Apr 5 16:59 system.log
-rw------- 1 root wheel 11808 Apr 7 02:59 userlog
-rw------- 1 root wheel 512144 Mar 9 19:07 vpn.log
-rw------- 1 root wheel 512144 Mar 9 19:07 wireless.log

I also used clog from the console to have a look, but the results are as seen on the web console. After a certain date, about 3pm yesterday afternoon, no more new logging is done. The hard drives and memory are 90% unoccupied.

some other hints: pfsense lives on my second partition, because #1 is usually reserved for swap (but swap is not active by now (thx FreeBSD).

Another hint: When I installed pfBlocker on 2.1.1, the crashes occurred multiple times, in a few minutes in a row. But now I am back on pfSense 2.1 without pfblocker an those clog crashes are still happening.

To me it looks as if the log gets busted, but I don't know where to alter it.

Any idea or hint would be highly appreciated.

Thanks, Joe

jimp

I'd rm *.log in there and then give it a restart to make sure it fully reinitializes the .log files.

(On 2.2 there is a button to reset the logs in case something like this happens)

Mr. Joe

Dear Jimp,

many thanks for your hint.

Erasing all logs did the job, so this one is currently solved.

To further avoid a log stall, do you know of a method to do so?

In particular, would a syslog server like syslog-ng do the job?

I will have post another question on the release depends here: https://forum.pfsense.org/index.php?topic=74897.0