jumanjihouse / docker-rsyslog Goto Github PK

rsyslog7 is the default package in Redhat6.x and 7 which is being used extensively in Corporate systems. Any chance to have rsyslog7 packaged in similar fashion?

http://www.rsyslog.com/doc/v8-stable/configuration/modules/imjournal.html

What do you think about adding logrotate? maybe with some env configuration in order to enable\disable it?

I think that's fine having it in the same rsyslog container because:

• logrotate is run by a cron (daily or hourly), so it's not a long running process, thus it does not violate docker principles of having single process in a container.
• if we have logrotate run where rsyslog runs we can easily use the logrotate's postrotate event to reload the rsyslog conf (avoiding issues like writing in wrong files after the rotation occurs). Something that could be harder if logrotate is in another container

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update alpine Docker tag
• Update dependency pre-commit to v2.21.0
• Update dependency pre-commit to v3
• Update jumanjiman/cci Docker tag to v20220712
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hi Team,

I'm trying to integrate the rsyslog with mongodb logs.

Currently, we have mongodb and rsyslog on the same container and mongodb is logging to syslog-facility local2 and rsyslog is capturing the requests (UDP port 514) and forwarding it to output. And now are planning to create a single central rsyslog daemon instead of running on each node. And so we separated the mongodb and rsyslog processes to two separate containers.

With the volumes-from approach, im not sure how can i integrate the mongodb logs (logging to local2 facility) to rsyslog container.

Any suggested path to proceed further.

Thanks in advance
Manoj Badam

Our rsyslog.service container, managed via docker compose, frequently got stuck in a restart loop.

Its own logs says over and over:
rsyslog.service | rsyslogd: run failed with error -3000 (see rsyslog.h or try http://www.rsyslog.com/e/3000 to learn what that number means) rsyslog.service | rsyslogd: pidfile '/var/run/rsyslogd.pid' and pid 1 already exist. rsyslog.service | If you want to run multiple instances of rsyslog, you need to specify rsyslog.service | different pid files for them (-i option).

Some quick research on the web found that by removing /var/run/rsyslogd.pid during container startup, just before rsyslogd is called, the issue can be resolved. Read here:
goharbor/harbor#1197

Would be awesome if you could add the equivalent change here as well. :)