Project

General

Profile

Actions

Bug #7269

closed

syslogd stops logging

Added by Robin Lutz about 7 years ago. Updated about 7 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Logging
Target version:
-
Start date:
02/17/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.3.2
Affected Architecture:

Description

I am trying to debug #7264 and have the problem that the log files don't recieve any update from syslogd. The last bytes arriving in the log are something like:

[2.3.2-RELEASE][root@fw.example.com]/root: hd /var/log/wireless.log 
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
0007cde0  00 00 00 00 00 00 00 00  00 00 00 00 43 4c 4f 47  |............CLOG|
0007cdf0  00 00 00 00 00 00 00 00  ec cd 07 00 00 00 00 00  |................|
0007ce00

When I clear the logs from the web interface, the logging process restarts for some minutes. Then the same messages are logged to the end of every syslogd file.

dmesg does not show any messages.

Actions #1

Updated by Robin Lutz about 7 years ago

With all log files empty, I get an segfault when running syslogd:

[2.3.2-RELEASE][root@fw.example.com]/root: /usr/sbin/syslogd -P /var/run/syslog.pid -f /var/etc/syslog.conf -F -d
listening on inet and/or inet6 socket
sending on inet and/or inet6 socket
off & running....
init
cfline("*.*                                %/var/log/routing.log", f, "radvd,routed,olsrd,zebra,ospfd,bgpd,miniupnpd", "*")
Segmentation fault
Actions #2

Updated by Jim Thompson about 7 years ago

  • Assignee set to Renato Botelho
Actions #3

Updated by Robin Lutz about 7 years ago

The segfaults occur, when a "clog" file gets truncated like:

echo > /path/to/log

After resetting all the logfiles, everything works again.

Can be closed.

Actions #4

Updated by Jim Pingle about 7 years ago

  • Status changed from New to Not a Bug
  • Assignee deleted (Renato Botelho)
Actions

Also available in: Atom PDF