8.32 is several years old, if you need support on it, you will need to ask for
support though your Ubuntu support channels (or setup a paid support contract)
The Ubuntu developers have backported some fixes from newer versions, but far
from all of them, so we of the community don't really know what they have done.
Since the source is available, it is possible for us to figure it out, but we
are a small enough group that we don't have the manpower to do so for all the
different distros and can only really support the recent versions we have
released.
We do try to help, but when things get involved enough, we need you to be able
to run a current version.
Let's put it this way, if we did find there was a previously unknown bug and we
fixed it, that fix would go into the current version, not into the version you
are running (unless the Ubuntu maintainers opted to backport that fix)
I have used disk assited queues since well prior to 8.32, so they can work, but
there have been farily serious improvements in that code since that time.
The path that we have been going down of tracking the state of the queue with
pstats and making sure that you have retries set to -1 apply no matter what
version you are running, but I know that back in that timeframe draining a disk
queue was very slow. I don't think you are being limited by that issue yet, but
if you did have a significant queue build up, it could take hours to days to
drain a few minutes of queue on that version.
I would suggest that you start down the path of getting the permission to run
more current versions, there has been so much development over the lst 4 or so
years that you will be missing if you stick with that version
David Lang
On Mon, 20 Apr 2020, TaSK via rsyslog wrote:
Date: Mon, 20 Apr 2020 08:57:27 +0200
From: TaSK via rsyslog <[email protected]>
To: rsyslog-users <[email protected]>
Cc: TaSK <[email protected]>
Subject: Re: [rsyslog] How to drain a queue?
Would you be so kind as to elaborate? What is not working? Some
particular combination?
On Ubuntu 18.04.04 LTS, which ships with 8.32.0, neither disk-queue nor
disk-assisted memory-queue seems to work.
I've only tested the simplest of cases: Disconnecting the destination and
reconnecting. Both with disk-queues and disk-assisted memory-queues, the
messages are stored on disk, but not forwarded upon reconnect.
Memory-only queues seems to work. But I run in containers, and Kubernetes
OOM (Out Of memory) is a frequent cause of death. There is more disk than
memory available.
Bottom line: If I stay with Ubuntu LTS, both disk-assisted queues must be
avoided?
It is an uphill battle to get permission to pull in software to replace
something in LTS and I really want to avoid that.
Regardless of this: Thank you for your efforts!
[TaSK]
søn. 19. apr. 2020 kl. 08:15 skrev Rainer Gerhards via rsyslog <
[email protected]>:
IIRC we had an issue fixed that was related. Maybe you should check
the ChangeLog. I guess an update to rsyslog current (8.2002.0) would
solve the problem.
HTH
Rainer
El sáb., 18 abr. 2020 a las 20:16, David Lang via rsyslog
(<[email protected]>) escribió:
>
> enable impstats so you can get reports on how many messages are in the
queue and
> in the disk portion of the queue.
>
> David Lang
>
> On Sat, 18 Apr 2020, TaSK via rsyslog wrote:
>
> > Date: Sat, 18 Apr 2020 16:29:03 +0200
> > From: TaSK via rsyslog <[email protected]>
> > To: [email protected]
> > Cc: TaSK <[email protected]>
> > Subject: [rsyslog] How to drain a queue?
> >
> > Setup is quite simple:
> > - An application sending 5 log messages per second
> > - A local rsyslogd server (8.1901) with the following simple setup:
> >
> > $WorkDirectory /var/spool/rsyslog
> > module(load="imuxsock")
> > module(load="imudp")
> > input(type="imudp" port="514")
> > *.* action (
> > type="omfwd"
> > queue.type="LinkedList"
> > queue.filename="forwarding"
> > queue.size="1000"
> > queue.maxFileSize="8m"
> > target="192.168.100.30"
> > protocol="tcp"
> > port="514"
> > )
> > *.* /var/spool/rsyslog/test-file
> >
> > - A server that dumps to disk.
> >
> > If I disconnect the server, messages starts piling up, and after a
while
> > ends up on disk in the expected file (forwarding.00000001). Messages
are
> > continuously being logged to the test-file, so everything is working.
> >
> > On reconnect, the messages immediately starts flowing again. But the
queue
> > is not drained. Thousands of messages remain on disk on the client
side.
> >
> > After an hour I restarted rsyslogd on the client side. On restart, the
> > file with the queued messages was deleted., but not sent. Thus, all
> > messages that were buffered were lost.
> >
> > A pointer to where I have erred in my setup would be very appreciated!
> >
> > [TaSK]
> >
> > --
> > Tage Stabell-Kulø
> > Pisa & Oslo
> > _______________________________________________
> > 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.
_______________________________________________
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.
--
Tage Stabell-Kulø
Pisa & Oslo
_______________________________________________
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.
