LogViewPlus Support » LogViewPlus Support » Help & Support » Log files not updating

Log files not updating

SoBeGuy — Mon, 06 Dec 2021 16:35:43 GMT

Most of the time, LVP updates a log within a few seconds of the file being written to. However, I sometimes encounter situations where log files stop updating completely. For example, I just checked one of my log files in LVP and the last entry was from a week ago. I knew that was wrong, so I checked the monitoring pane and it showed that the file was being actively monitored. Then I closed and reopened the workspace. After that, it showed the hundreds of log entries from the past week.

I have LVP installed on my laptop and the machine is frequently suspended without an Internet connection when I'm moving about. Therefore, I'm wondering if it loses the connection while the machine is suspended, then fails to reestablish the connection when the Internet connection is restored. I think the monitoring function needs to be made more robust to account for this scenario.

RE: Log files not updating

LogViewPlus Support — Mon, 06 Dec 2021 16:35:43 GMT

Glad to hear it - thanks for letting me know! :-)

RE: Log files not updating

SoBeGuy — Mon, 06 Dec 2021 16:32:10 GMT

Yes, the 43 build works, thanks!

RE: Log files not updating

LogViewPlus Support — Mon, 06 Dec 2021 15:58:20 GMT

Apologies Brad. There was a problem with the installer which we failed to detect in our pre-release testing.

We have recreated and fixed the issue in the updated beta release - v2.5.43.

RE: Log files not updating

SoBeGuy — Mon, 06 Dec 2021 13:56:58 GMT

No, I haven't installed any custom code.

RE: Log files not updating

LogViewPlus Support — Mon, 06 Dec 2021 13:44:41 GMT

Thanks for the crash report. There is a problem loading one of the dependent libraries.

Do you have any custom code running in LogViewPlus extending Clearcove.LogViewer.Common.dll? If so, can you please update this library with the install file?

RE: Log files not updating

SoBeGuy — Mon, 06 Dec 2021 13:40:13 GMT

Unfortunately, the beta crashes immediately upon execution. I sent you the crash report.

RE: Log files not updating

LogViewPlus Support — Mon, 06 Dec 2021 08:27:42 GMT

Hi Brad,

We have just released LogViewPlus v2.5.42 as a beta release. This version has a number of fixes for dropped connections, recovery and reporting - both in the transfer progress view and the main tree view:

Hope that helps. Please let me know if you have any further issues or feedback.

Toby

RE: Log files not updating

LogViewPlus Support — Wed, 01 Dec 2021 15:01:07 GMT

Hi Brad,

No update yet, but this is something we will be actively looking at over the next two weeks. It is high on my list of priorities. We will be looking at this in conjunction with the status indicators we discussed previously.

Hope to have a BETA release for you soon.

Toby

RE: Log files not updating

SoBeGuy — Wed, 01 Dec 2021 14:50:20 GMT

Juts wondering if you're making any progress on this issue. It pretty much happens constantly, especially with larger log files. At least for me, the tailing mechanism is mostly useless at this point. Any time I want to view the latest entries, I have to manually reload the file.

RE: Log files not updating

SoBeGuy — Thu, 23 Sep 2021 14:18:29 GMT

This just happened again, but this time I was able to refresh the file using the Reload File option from the context menu.

RE: Log files not updating

LogViewPlus Support — Mon, 20 Sep 2021 05:50:44 GMT

That's interesting. I would have expected a full refresh to resolve the issue.

Thanks for the update. I will take a closer look and get back to you.

RE: Log files not updating

SoBeGuy — Mon, 20 Sep 2021 04:56:24 GMT

Actually, in this case, I first tried refreshing the log file and that didn't work. Then I closed and re-opened the worksspace.

RE: Log files not updating

LogViewPlus Support — Mon, 20 Sep 2021 04:47:50 GMT

Thanks for reporting this issues Brad.

I will need to investigate this issue and get back to you. In the meantime, if you detect a loss of connection, refreshing your log file (F5) may be the best work-around.

As suggested, the issue is probably related to the laptop suspension / loss of connection. The fix here will likely involve improved error detection and reporting. If we were to refresh the connection automatically, important log entries may be lost. If we resume the connection, there will be a gap where log entries may have been written.

Thanks again,

Toby