what I did today in the morning was to put the socket in /run
input(type="imuxsock" socket="/run/logmat")

until now no errors so far but that does not mean a lot as there is not much traffic right now. you mean remove the python script or the whole script call? what I could do is to echo the message to a file instead of piping it to the python script, yes.
I will try it an let it run for today, or until I have an error again

On 18/09/2023 09:18, Rainer Gerhards wrote:
Maybe a debug logs helps, but if rsyslog does not emit an error
message, it does not sound like it has some issue. I also don't see a
relation to the script. But to be sure, would it be possible to
temporarily remove it and see if that changes anything?

Rainer

El lun, 18 sept 2023 a las 9:09, TG Servers (<sr...@prvtmail.net>) escribió:
Hi Rainer,

this is from nginx error log, yes.
No I cannot find any other errors, thats my problem
But it happens every single day, regularly...
as just written in another message re the question if it occurs with rsyslog 
restart or logrotate :

no absolutely not, I cannot see any relation to things like that, that is what 
leaves me a bit baffled here.
You can see this is all from one day, and if there is a 111 on 2:52:19 on 
2:52:22 there is everything ok (just as an example)
Rsyslog restarts run between 0:10 and 0:15, depending on finish of nightly 
dnf-update, logrotate runs at 0:00 via systemd timer, nginx is not restarted 
automatically
There is no information in any log except in the nginx logs, and the entries 
that are shown as failed are clearly missing in the target analytics log
I cannot see any pattern...


On 18/09/2023 08:53, Rainer Gerhards wrote:

Is this from a nginx text log? Any errors infos from rsyslog itself?

Rainer
PS: I do not see how this can be related to rsyslog, but you never
know. I do not yet understand the fault scenario TBH.

El dom, 17 sept 2023 a las 18:39, TG Servers via rsyslog
(<rsyslog@lists.adiscon.com>) escribió:

Hi,

ever since I started logging to a UDS from my nginx I get the occasional
111 in my nginx error logs.
As I literally don't have any other information or log entries I
honestly do not know how to debug this.
The thing is requests one second, or a few seconds later are processed
totally fine, so it cannot be a general problem, nor a access problem or
a permission problem.
I would be glad if anyone could help on fixing this

Examples:
error.log:2023/09/17 02:41:59 [error] 346192#346192: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 02:41:59 [error] 346191#346191: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 02:52:19 [error] 346192#346192: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 04:09:44 [error] 346193#346193: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 04:09:45 [error] 346185#346185: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 04:20:20 [error] 346186#346186: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 06:20:01 [error] 346182#346182: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 08:32:35 [error] 346182#346182: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 08:32:35 [error] 346188#346188: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 09:34:34 [error] 346183#346183: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 09:34:35 [error] 346183#346183: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket
error.log:2023/09/17 16:00:25 [error] 346187#346187: send() failed (111:
Connection refused) while logging to syslog, server:
unix:/var/cache/nginx/rsyslog.socket

configuration for this single use case, of course there is a lot more in
rsyslog.conf
$AddUnixListenSocket /var/cache/nginx/rsyslog.socket

$template app,"%msg:2:$%"

if $programname == "app" then {
     ^/usr/local/script/app_log.sh;app
     stop
}

The script app_log.sh does simply
echo "${@}" | /usr/bin/python <python_script>

Many thanks

_______________________________________________
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.



_______________________________________________
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.

Reply via email to