rsyslog starting too soon causes race condition, could look the server for several minutes before a successful start

[curtishall]

bc-server    | > /usr/sbin/rsyslogd
bc-server    | rsyslogd: pidfile '/run/rsyslogd.pid' and pid 10 already exist.
bc-server    | If you want to run multiple instances of rsyslog, you need to specify
bc-server    | rsyslogd: run failed with error -3000 (see rsyslog.h or try https://www.rsyslog.com/e/3000 to learn what that number means)
bc-server    | > /usr/sbin/rsyslogd
bc-server    | rsyslogd: pidfile '/run/rsyslogd.pid' and pid 10 already exist.
bc-server    | If you want to run multiple instances of rsyslog, you need to specify
bc-server    | rsyslogd: run failed with error -3000 (see rsyslog.h or try https://www.rsyslog.com/e/3000 to learn what that number means)
bc-server    | > /usr/sbin/rsyslogd
bc-server    | > /usr/sbin/rsyslogd

[dawei1]

Having this problem, any fix yet?

[curtishall]

Is this a new install or an older install? Sent from Gmail Mobile

…

On Sun, Oct 22, 2023 at 12:02 AM dawei1 ***@***.***> wrote: Having this problem, any fix yet? — Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACQ5VSN2X4MOTOYJYZUKYDYASSH5AVCNFSM6AAAAAA5FKFILWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTHE4TKNBYGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dawei1]

Tried both. Same issue in new install of ubuntu 22.04 and rocky 9.2. I found a workaround, I need to hack the entrypoint.sh inside the bc-server container's filesystem (inside /var/lib/docker/overlay2/) and add the following line right before line '/usr/sbin/rsyslogd':
rm -f /run/rsyslogd.pid

This will remove any existing rsyslogd.pid before starting a new instance of rsyslogd. Then it works well.