permanent syslog: saving log to the flash drive?

[davorj]

Anyone? Currently it is saved in /var/log/messages but this is on tmpfs. After a crash/poweroff the log is gone.

I tried to put it in “/var/tmp/flash/mod” and it seems to work. (Are there more appropriate places for this?) Then I cannot delete files from “/var/tmp/flash/mod”. If I “rm <file>” it is removed, but after I reboot, it is there again. I am puzzled. What is going on here?

 

[RalfFriedl]

Files in /var/tmp/flash are saved with modsave and restored on reboot.

 

[davorj]

That clears it up...

Is there a way to mount the flash drive?

 

[olistudent]

Why don't you set another path for the messages file?

You don't need to mount the flash drive manually. Just plug it in.

Regards
Oliver

 

[davorj]

You don't need to mount the flash drive manually. Just plug it in.

I am talking about the build in flash memory. My Fritz has no USB port.

The Fritz is rebooting/crashing almost every morning without apparent reason. I just want to find the cause. That’s why I installed syslogd. After the crash I would like to consult the log, and try to see what went wrong.

 

[RalfFriedl]

Most likely the reason for the crash won't be in the log because syslog will also be crashed before it can write to the log.
You can try to log to the network, but even then syslog may stop working before it can send something about the reason for a crash.
The flash memory in the box is already used for the firmware and the configuration, you can't use it for the log, and it would have the same limitations as all the other log destinations.

You can also try a serial console, or watch the memory usage of the box.

 

[davorj]

Memory usage seems fine. I have tried watching the /dev/debug simply by doing cat /dev/debug from the console on one of the computers. Just before a reboot I get this:

....
mcfw: group 0.0.0.0: query tiwlan:0 10sec
mcfw: group 0.0.0.0: query tiwlan:0 10sec
mcfw: group 0.0.0.0: query tiwlan:0 10sec
[B]mcfw: forward disabled (vcc0: bc:05:43:6a:dd:f8, vlan 0, pppoe 0)
kdsld: atmvcc_receive: vcc closed
kdsld_token_thread: end[/B]

"mcfw: group 0.0.0.0: query tiwlan:0 10sec" is normal, but the last tree are not and only show up before reboot/crash in the morning.

I have read that Fritzbox initiates a reboot if it detects many errors. Are there any other interesting log sources?

I am quite sure that this is unrelated to Freetz as I installed it to debug.

regards,
Davor

 

[RalfFriedl]

If the problem occurs with AVM firmware, you should ask AVM.

You can disable the watchdog with

echo disable > /dev/watchdog