Hi Andre,

Thanks for the feedback.

Should setting queue.lightDelayMark to 0 be done for the imrelp input ruleset 
or the main queue?

-----Original Message-----
From: Andre Lorbach <[email protected]> 
Sent: Monday, August 24, 2020 4:07 AM
To: rsyslog-users <[email protected]>
Cc: Adam Chalkley <[email protected]>
Subject: AW: [rsyslog] Upgraded receiver from Ubuntu 16.04 to 18.04, 
connections from clients failing with a high number of CLOSE_WAIT connections 
on receiver

Hi Adam,

See my comments below.

> -----Ursprüngliche Nachricht-----
> Von: rsyslog <[email protected]> Im Auftrag von Adam
> Chalkley via rsyslog
> Gesendet: Sonntag, 23. August 2020 18:49
> An: rsyslog-users <[email protected]>
> Cc: Adam Chalkley <[email protected]>
> Betreff: Re: [rsyslog] Upgraded receiver from Ubuntu 16.04 to 18.04,
> connections from clients failing with a high number of CLOSE_WAIT
> connections on receiver
>
> I enabled debug-on-demand mode and found the lines noted earlier in this
> thread within the debug log.
>
> I also found lots of messages like these:
>
> $ sudo grep 'main Q' /var/log/rsyslog-debug-on-demand.log
> 7501.401841560:imuxsock.c     : main Q: queue.c: EnqueueMsg advised
> worker start
> 7502.328726922:imrelp.c       : main Q: queue.c: EnqueueMsg advised
worker
> start
> 7502.329026161:imrelp.c       : main Q: queue.c: doEnqSingleObject:
LightDelay
> mark reached for light delayable message - blocking a bit.
> 7502.329631733:imuxsock.c     : main Q: queue.c: EnqueueMsg advised
> worker start
> 7502.329664576:imuxsock.c     : main Q: queue.c: EnqueueMsg advised
> worker start
> 7503.329150535:imrelp.c       : main Q: queue.c: EnqueueMsg advised
worker
> start
> 7503.329426002:imrelp.c       : main Q: queue.c: doEnqSingleObject:
LightDelay
> mark reached for light delayable message - blocking a bit.
> 7503.329950433:imuxsock.c     : main Q: queue.c: EnqueueMsg advised
> worker start
> 7503.329989705:imuxsock.c     : main Q: queue.c: EnqueueMsg advised
> worker start
> 7504.329531389:imrelp.c       : main Q: queue.c: EnqueueMsg advised
worker
> start
> 7504.329854248:imrelp.c       : main Q: queue.c: doEnqSingleObject:
LightDelay
> mark reached for light delayable message - blocking a bit.
>
>
> Turning to Google, I landed on these pages:
>
> https://www.rsyslog.com/doc/master/concepts/queues.html
> https://www.rsyslog.com/doc/master/rainerscript/queue_parameters.html
> https://github.com/rsyslog/rsyslog/issues/1778#issuecomment-353135527
> https://github.com/rsyslog/rsyslog/pull/3642
> https://github.com/rsyslog/rsyslog-doc/pull/819
>
> Is the fix here to set queue.lightDelayMark to 0? Should this be set for
the
> main queue or the ruleset attached to imrelp?

Unless you are using any UDP inputs, setting this to 0 should solve this
problem.

Best regards,
Andre Lorbach
--
Adiscon GmbH
Mozartstr. 21
97950 Großrinderfeld, Germany
Ph. +49-9349-9298530
Geschäftsführer/President: Rainer Gerhards Reg.-Gericht Mannheim, HRB
560610
Ust.-IDNr.: DE 81 22 04 622
Web: www.adiscon.com - Mail: [email protected]

Informations regarding your data privacy policy can be found here:
https://www.adiscon.com/data-privacy-policy/

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient or have received this e-mail in error
please notify the sender immediately and delete this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren und die unbefugte
Weitergabe dieser E-Mail sind nicht gestattet.
_______________________________________________
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