[feature request] options to deal with bad logging situation

[ElTopo]

Hello,

Debian's supervisor package configures logfile path to be
/var/log/supervisor/supervisord.log
and creates /var/log/supervisor at installation.

However, when I put /var/log in tmpfs that directory may not exist after system reboot/reset, causing supervisord exits with the following error:
Error: The directory named as part of the path /var/log/supervisor/supervisord.log does not exist.

This is a bad situation since I depend on supervisord for running several other processes.

I would like to request some options to deal with this situation:

1. "create directory" option: when enabled, supervisord tries to create the directory (/var/log/supervisor) if it does not exist;
2. "continue on error" option: when enabled, if supervisord cannot write the log files (read-only filesystem, directory does not exist, etc.), it complains about the problem in daemon.log, but still continues to run without any loggings (samba works this way by default, if I don't have /var/log/samba directory, it disables all loggings but still keeps running). I much prefer my processes running with any logs to not running at all.

Thanks.

[mnaberez]

Duplicate of #120

However, when I put /var/log in tmpfs that directory may not exist after system reboot/reset, causing supervisord exits with the following error:
Error: The directory named as part of the path /var/log/supervisor/supervisord.log does not exist.

In your init script that launches supervisord at startup, put the command mkdir /path/to/logs before the command supervisord.

[ElTopo]

Thanks for the reply, I currently use a script to create the (hardcoded) directory but the problem is, the script does not know the logfile path (or rather, it has to parse supervisord.conf for the logfile path), it's easier and better for supervisord to handle this.

PS: please don't close this issue so quickly... I also want the second option in case my script does something wrong.

EDIT: so I just read issie #120, it seems that you didn't even want to deal with this issue at all, maybe I should find anther super process manager that's more reliable.

[tevino]

As mentioned in #120, this feature will not deliver, what a shame. 😟

@ElTopo syslog and systemd are your friends.