Logging occasionally fails with existing rsyslogd.pid file error

[mikkonie]

When starting up the image using docker compose, there are occasional errors regarding logging. Either it's a complaint for not being able to write to the log file, or the following:

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

I'm definitely not a syslog expert, so no idea why these occur. Need to investigate.

[mikkonie]

The file itself could be easily wiped by adding rm -f /var/run/rsyslogd.pid to the entrypoint. However, when this next happens I need to check if there is indeed a corresponding process running. If so, that should be killed as well I suppose.

[mikkonie]

Nope, that process does not exist. Adding the rm command to the entrypoint. Open for ideas if there is a better way to handle this.

[mikkonie]

Fixed.