I just wanted to add that in a further message as it came to my mind.
you were faster...
the script is definitely "slow", this is what I know for sure as it does
quite a lot of processing/analytics in the background, so even if you
trigger it from command line it can take half a sec or so.... I can't
change that, it needs to do what it does, I didn't write it
though it can handle manual fast F5 triggers in the browser without
issue and then it 111s when there are 2 requests incoming...
I thought rsyslog might handle that just well via the queue...
but then this might eventually really be the issue, and if it is, is
there anything to mitigate this from rsyslog side (in terms of own queue
for that socket or something in that direction)?
ok, will enable impstats, too when I switch back
Thanks,
Tom
On 18/09/2023 16:17, Rainer Gerhards wrote:
so far not a single 111 today, I let this run the until late evening,
and if there is stil no 111 I will put back the python script in order
because right now there are 2 possibilities, I moved the socket as said,
and I skipped the script and just appended the message to a file
if either of the 2 things are responsible in the end I won't understand
it either :)
I don't know what the script does. But if it is slow, it may push back
to the main queue, making rsyslog unresponsive.
This is David's concern. Tomorrow, if you re-enable, you should also
enable impstats as David suggested.
Rainer
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
