You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example I'm missing almost half of all expected events. Yet I can confirm on the log server with the 'journalctl' command that there are actually 20K log records stored on the server.
Even if I test with just 1K events per client and run that simultaneously it's also clearly visible:
Happy to run any additional tests if that helps.
If I made a huge mistake, please let me know.
Update 1
I've been testing this issue on virtual machines on my mac.
I've also a few physical x86 micro pc's and the issue is the same.
Rate-limiting the logging with sleep .01 doesn't impact the result.
Question, is python-systemd built to handle remote logging from multiple clients through polling?
The text was updated successfully, but these errors were encountered:
louwrentius
changed the title
When monitoring /var/log/journal/remote events are missed when two remote hosts send messages at the same time
When monitoring /var/log/journal/remote events are missed when two remote hosts send messages at the same time (updates)
Jul 17, 2024
Context
Testing Method
We first cleanup the server with:
On each client we run (side by side / simultaneously:
So we expect 20,000 records on the server, which we validate:
I've tested this many times to confirm that the systemd-journal-remote/upload mechanism is OK.
The failing code
First of all, I'm not sure if this code is right. If I've made a glaring mistake, I apologise in advance for this report.
That said, I get correct results if I run my '10K log generator command' on one client at a time.
If I run the command at the same time on each client at once, I would expect 20K records, but it gets nowhere near that:
In this example I'm missing almost half of all expected events. Yet I can confirm on the log server with the 'journalctl' command that there are actually 20K log records stored on the server.
Even if I test with just 1K events per client and run that simultaneously it's also clearly visible:
Happy to run any additional tests if that helps.
If I made a huge mistake, please let me know.
Update 1
I've been testing this issue on virtual machines on my mac.
I've also a few physical x86 micro pc's and the issue is the same.
Rate-limiting the logging with sleep .01 doesn't impact the result.
Question, is python-systemd built to handle remote logging from multiple clients through polling?
The text was updated successfully, but these errors were encountered: