No logs are being sent to syslog

238 views
Skip to first unread message

Bartosz

unread,
Aug 25, 2021, 4:57:52 AM8/25/21
to rabbitmq-users
I'm trying to send rabbitmq logs (all of them) to a remote syslog server. But the configuration stanzas don't seem to work at all. 

Did I get this right?
If I set the log.syslog stanzas correctly in rabbitmq.conf then all logging should be also sent to the syslog server. 

log.syslog = true
log.syslog.level = debug
log.syslog.transport = udp
log.syslog.protocol = rfc3164
log.syslog.host = syslog.lan
log.syslog.port = 514
log.syslog.identity = rabbitmq
log.syslog.facility = local4

But nothing comes on syslog.lan:514. 

I'm using RabbitMQ v3.8.9 on Windows, with the firewall completely off (also off on syslog.lan host).
I also tried with the Docker image rabbitmq:3.9-management - same thing, it doesn't work.

And for the listener on syslog.lan:514/udp - there's just a docker image with datalust/seq-input-syslog container. I also used tcpdump to look for ttraffic, but there's none.

I'm trying to get all the rabbitmq logs into Seq. That's the goal. I would appreciate any help.


My complete rabbitmq.conf::

loopback_users = none

log.console = true
log.console.level = debug
log.file.level = debug
log.exchange = false
log.exchange.level = info

log.syslog = true
log.syslog.level = debug
log.syslog.transport = udp
log.syslog.protocol = rfc3164
log.syslog.host = tinkerbox.lan
log.syslog.port = 514
log.syslog.identity = rabbitmq
log.syslog.facility = local4

and advanced.config:
[
    {syslog, [
        {logger, []}
    ]},
    {lager, [
        {handlers, [
            {syslog_lager_backend, []}
        ]}
    ]}
].


Michal Kuratczyk

unread,
Aug 25, 2021, 5:46:04 AM8/25/21
to rabbitm...@googlegroups.com
Hi,

Seems to work for me (tested with 3.9.4 installed via brew).

# I only changed the host to 127.0.0.1
$ cat $RABBITMQ_CONFIG_FILE                                                                                                                                                                                  ✘ INT
log.syslog = true
log.syslog.level = debug
log.syslog.transport = udp
log.syslog.protocol = rfc3164
log.syslog.host = 127.0.0.1

log.syslog.port = 514
log.syslog.identity = rabbitmq
log.syslog.facility = local4

$ rabbitmq-server

# in another terminal
$ nc -l -u 514
<27>Aug 25 11:43:15 mkuratczyk-a01 rabbitmq[15426] logger_sup - Supervisor {local,logger_sup}: child rmq_1_file_1 started
...
# the logs keep coming in

Best,

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/7f8f732c-2083-433c-9ac5-fc03d620a948n%40googlegroups.com.


--
Michał
RabbitMQ team

Bartosz

unread,
Aug 25, 2021, 7:04:51 AM8/25/21
to rabbitmq-users
I did install the newer version (3.9.4) on Windows and updated Erlang to 24.0 and yes - the logs started coming in.

Is this a problem with 3.8.9 then? 
I have a number of nodes that currently cannot go through an update like this. I found some messages here that say the syslog support was broken between 3.8.4 and 3.8.16 or something close to those versions. Is it confirmed?

Thank you for taking the time to test this.

Michal Kuratczyk

unread,
Aug 25, 2021, 7:13:16 AM8/25/21
to rabbitm...@googlegroups.com

> Syslog dependency was not started correctly. This meant no log messages were sent to Syslog.


So yes, perhaps you should try 3.8.10+



--
Michał
Reply all
Reply to author
Forward
0 new messages