Messed printing when following deleted and recreated logs

[Lightjohn]

Hi,

I'm working and debugging an application and from time to time I delete the logs and the application will recreate them seconds later.
But the problem is that glogg is missing the new lines characters and so the printing is bad.

I'm using the latest version from the git.
I know it's not an usual way to work and just wanted to let you know that.

[bristolweb]

I have a similar problem. I upgraded recently to 1.1.3 from 0.9 on linux Mint 17.3 (Rosa). Reason for upgrading: I needed more than the 5 logs easily available from 0.9. I really like the new 1.1.3 tabs for selecting each log! :)

Version 1.1.3 seems fine except that every time one of the logs is rotated (ie most mornings depending on the log) I have to drop glogg and reload it. Not a major problem since unlike syslog viewer the log names and filter colours are retained and all I have to do is hit Follow for each log. Still annoying, though. Reload has no effect on this.

Primary logs used in this situation are mail (postfix), dovecot, spamd, clamav and ubound. Various apache logs are also viewed depending on current needs. Mail log is usually ok but dovecot always displays with no regard for newlines.

[nickbnf]

Could you check if the problem is still happening with 1.1.4? A bug was fixed that might be the root cause for what you are seeing as well.

[bristolweb]

Not sure how to download/install 1.1.4 - apt-get install just says "latest version installed". Could you give some idea, please? Linux Mint 17.3.

[Lightjohn]

Compiling using latest git I get this version "Built 2017-05-19 from 624d1a5". Nothing changed and it seems even a little bit worse: it was only filling with blank line (happen twice). So it seems for now that I will have to restart glogg at each logs reset. But if I let it open long enough, it seems that the problem solve itself. Thanks.

…

On 19 May 2017 at 11:18, Nicolas Bonnefon ***@***.***> wrote: Could you check if the problem is still happening with 1.1.4? A bug was fixed that might be the root cause for what you are seeing as well. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#151 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHN8Gbb1T2PWrBwws_a3pZPu8RungXPLks5r7WxggaJpZM4Mx-G1> .

[nickbnf]

OK, so we have a real problem here, the fact reloading is not doing anything is especially bizarre. Do you have a scenario where you can reproduce the problem 100%? I'll give it a try.

[Lightjohn]

Hi sorry for the late comeback, I'm still getting the issue so just went back and saw your message.
At least with time I know exactly what cause the issue in my case.
My application is rotating the log every hour and every time it happen while I'm watching, the output will be all messed up.
So I think just:

move current log and and wait for the application to recreate it is enough in my case.

It's still happening for me and I compile directly from git from time to time (just done that before that message) and the only solution to solve that is to close and reopen glogg.
Do you want a script that could reproduce it?

[gin-ahirsch]

Can you try PR #222? It changes things when re-opening files some.

[Lightjohn]

I just tried and it's working :)
It seems I will just have to wait for your changes to be merged.

Thank you

[nickbnf]

When your app recreate the log, does it create an empty file and then append to it, or is it creating an already full file (like a log rotation tool would do)?

[Lightjohn]

In my case it's just log4j auto rotate option, so the file would be very briefly an empty file, then a lot of logs will be appended.

[crazycliffy]

Anyone experiencing any issue with this still? I compiled from the latest version 1.1.4 for linux (redhat/centos) target. When the file gets rolled over (e.g. "mv file.log file.log.1; cp file.log.1 file.log"), I see garbled, messed up text displayed in glogg. Using the Reload (Ctrl-R) feature does not fix the issue. As a workaround, I have to close the file, and just reopen it.

[Lightjohn]

I still have this issue.
Same I just close and re open the app all the time.
And because I use glogg as debug tool I close reopen it quite a lot

[variar]

@Lightjohn is this issue present in glogg built from latest master? I've chery-picked fix into my fork, but if the problem is still present in glogg master, then I'll have to find some other fix.

[Lightjohn]

@variar Latest build from master seems OK I played with it a little bit by moving logs with a script.

So the fix is not in buntu repo but that's another story! Fix is here and working. Thank you