Truncated WebIF Display of Log Files

[Black Hole]

Picking up from here:

I trawled the logs again this morning, and checked what RS was reporting, for all machines, and found that sometimes the Diagnostics log viewer fails to display the whole log despite clicking the Reload button. I checked the logging is active by setting test recordings from RS.

I assume the display is assembled at the server (the 'FOX) with Jim, rather than in the browser using JS? If it were the latter, I could understand that the download of the log file got interrupted, but I don't know how to explain it if powered by Jim at the server.

The whole file is downloaded in to the browser by Jim, than paged though with JS.
Getting a partial log seems weird. You can test what the Jim is doing by issuing a command such as:

cd /mod/webif/html/log
QUERY_STRING="file=/mod/tmp/rs.log&dload=-" ./fetch.jim

which gives the HTML formatting, otherwise you can get the raw file by setting "dload=1" in the above command.

Here is a typical example:



Notice the headline says the file is 5725 lines and showing only the most recent 5000 (that's normal for the WebIF Diagnostics log file viewer), but I'm only actually being shown 519 lines.

This is persistent over multiple refreshes and sessions (and historically clears with a reboot).

I don't understand those command lines, but I'll give it a go... I adapted the second command for auto.log, and it spat out the whole thing (filling up the console buffer). Retrying the log viewer continues to truncate it at 519 lines.

Displaying activity.log truncates 4473 lines at line 545.

 

[MymsMan]

I have the log rotate size set at 100kb so that they usually switch before they reach 5000 lines, I have never understood the use of logs that cant be fully viewed by the log viewer page.

However that does nothing to explain why you are only seeing about 500 lines - I don't recall ever seeing that.

 

[Black Hole]

I dunno. You said the test command spat out the whole file, so it seems like something client side. Investigate your browser's debugging options to see if you can work anything out.

I sampled several log files again, and got the same behaviour (including qtube.log declaring 1887 lines but displaying none at all). WebIF reboot, problem gone away. I don't understand how that could be client-side.

 

[prpr]

WebIF reboot, problem gone away. I don't understand how that could be client-side.

No, me neither, but why did it work OK from the command line. Makes no sense. I think your dodgy boxes must have hardware faults of some description. Seems pointless trying to pursue it when you know when it's broken and what to do to fix it. Or just schedule a reboot every day.

 

[Black Hole]

If nobody else is experiencing the same, I concur.