0
I am dealing with a misbehaving third-party program, the vendor of which seems happy to help if I can provide them with the debug log. They told me how to turn debug logging on and off, however somewhere within the program there's a limit on the log file of 65 KB - according to the vendor this is hardcoded. As soon as this log limit is hit, the entire log is simply deleted and a new file with the same name is created instead. As a result, only about 1 minute of debug log is saved before the log is deleted and a new one is created. Trying to tail -f
the log doesn't help as when the new one is created, it's not the same file any more, so tail
just stops.
The whole thing is made more complicated by the fact that the program is running on an embedded linux with absolute minimal tool support (there's no ssh or ftp even, only telnet to connect to it). There is no find
command, not locate
or slocate
and I'm not even talking about the compilers. There's shell there - sh
and ash
- that's all. I'm really at a loss as to how to capture about 20 minutes of debug logging. Any suggestions would be more than appreciated.
1If
tail -F
is supported, use that. – yoonix – 2014-06-18T22:33:17.590Can you see cron jobs? probably the program would have written cron job, try editing the time of it, so that you can escape the deletion – J Bourne – 2014-06-19T17:24:34.360
@Sai The deletion occurs not by time but by the size of the log file. As soon as the log file hits 65535 bytes, it's deleted. – Aleks G – 2014-06-19T21:12:14.710
Are you sure it is done the deletion is done by programme, or /etc/logrotate.d? – J Bourne – 2014-06-20T09:13:16.857
@Sai there is no
/etc/logrotate*
. It's a very cut down version of embedded linux. – Aleks G – 2014-06-20T09:16:00.697