If cupsd fails to open the existing cups-files.conf (where the log location is defined) and journal is not available (f.e. in containers), the error message is lost because cupsd tries to sent it to journal.

This problem showed up during CUPS container investigation, when cups-files.conf had incorrect permissions in comparison to cupsd, which does not run as root in container.

How to reproduce:

1. dnf -y install cups
2. useradd user
3. systemctl stop systemd-journald systemd-journald-dev-log.socket systemd-journald.socket
4. su user -c '/usr/sbin/cupsd -f'

Results:
The command returns 1 as error, but with no information in journal or log file.

Expected result:
Error message on stderr.