Klaus Reimer wrote: > Haven't configured syslog yet to log onto my notebook. I'll configure it > this evening and hope it will tell me something interesting before it dies.
So I gave it another try, configured remote syslogging and additionaly wrote a script which logged the free memory every 5 seconds to syslog. Here are the famous last words of the router (and some previous logging lines so you can see how the memory usage increases): Jan 30 19:30:40 hellsgate.home root: Free Memory: 11988 ... Jan 30 19:40:35 hellsgate.home root: Free Memory: 11796 ... Jan 30 19:51:15 hellsgate.home root: Free Memory: 11792 ... Jan 30 20:00:02 hellsgate.home root: Free Memory: 11784 ... Jan 30 20:10:06 hellsgate.home root: Free Memory: 11640 ... Jan 30 20:20:20 hellsgate.home root: Free Memory: 11496 ... Jan 30 20:30:04 hellsgate.home root: Free Memory: 11360 ... Jan 30 20:40:03 hellsgate.home root: Free Memory: 11176 ... Jan 30 20:50:07 hellsgate.home root: Free Memory: 11012 ... Jan 30 20:55:09 hellsgate.home root: Free Memory: 10984 Jan 30 20:55:14 hellsgate.home root: Free Memory: 10960 Jan 30 20:55:19 hellsgate.home kernel: dst cache overflow Jan 30 20:55:19 hellsgate.home root: Free Memory: 10964 Jan 30 20:55:21 hellsgate.home kernel: dst cache overflow Jan 30 20:55:23 hellsgate.home last message repeated 4 times Jan 30 20:55:24 hellsgate.home root: Free Memory: 10960 Jan 30 20:55:24 hellsgate.home kernel: NET: 1 messages suppressed. Jan 30 20:55:24 hellsgate.home kernel: dst cache overflow Jan 30 20:55:34 hellsgate.home kernel: NET: 85 messages suppressed. Jan 30 20:55:44 192.168.36.1 kernel: dst cache overflow Jan 30 20:55:54 192.168.36.1 root: Free Memory: 10960 The memory usage increases but It doesn't look like it has anything to do with the crashing router. This increase may be normal because Azureus sees lots of different IPs during the session, resolves them into hostnames (cached by dnscache), conntrack tables, what ever. What exactly means "dst cache overflow"? And what is "NET: 85 messages suppressed"? Maybe I need to increase some logging level to see these suppressed and maybe important messages? Also interesting to see that DNS resolving no longer works in the last two log lines sent by the browser. So the router was already dying while it still was able to sent log lines before it died completely. -- Bye, K <http://www.ailis.de/~k/> [A735 47EC D87B 1F15 C1E9 53D3 AA03 6173 A723 E391] (Finger [EMAIL PROTECTED] to get public key) _______________________________________________ freewrt-users mailing list freewrt-users@freewrt.org https://www.freewrt.org/lists/listinfo/freewrt-users
