New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
incremental mode with ssh does not work until log file rotates #723
Comments
After digging, I found that the problem seems to be in the
It could be that piping ssh into
while when using
The only difference, to me, are the connection options that should not cause the problem. |
Apparently the key-changing fact is the
|
Hi Luca, Thanks for the report, commit 093e233 adds the ssh options to the command. Please let us know if that's solve your issue. |
Uhm, it seems not working to me without the
while if, immediatly after, I do the same with
so the |
Ok, I was able to reproduce, the problem was that I was testing change with a new log file not with new entries in the last log. Commit 6a4750b fixes this issue. |
Great job! It works for me now. |
@fluca1978 please give a try to latest commit 44f0be5. I have done a full review of the log file detection so please confirm that is not break your reports. It should not impact remote log file but just to be sure. |
It is working for me. I've tested against v11.8 at 996c199. I see messages in the debug output that state what is happening, I don't remember having seen such messages before:
|
Hi all,
I'm observing a strange, at least to me, problem with
pgbadger 11.7
and SSH connection.if I keep executing the
pgbadger
no new logs entries are found, while the log file (in this casepostgresql-Wed.log
) is increasing.I've already checkd that the
ssh luca@miguel "cat '/var/log/postgresql/postgresql-Wed.log'"
command is working and is outputting all the entries in the log file, so it seems there is no problem in retrieving the log content.The
LAST_PARSED
file is fine and contains:If I
rsync
locally the file thenpgbadger
builds incrementally on the very same file, while via SSH keeps stating that the file has been already parsed.The text was updated successfully, but these errors were encountered: