Description of problem: tcmu-runner dumps some of its logs (levels # 0: CRIT # 1: ERROR # 2: WARNING # 3: INFO # 4: DEBUG) into tcmu-runner.log as well as /var/log/messages, while logs with loglevel # 5: DEBUG SCSI CMD, are dumped to stdout (as dumping them to tcmu-runner.log could fill up the disk space) rsyslogd.service will maintain these copy stdout logs into /var/log/messages While debugging other bugs, we found syslog service is not installed as part of containers. As part of this bug, we should install syslog service and start/enable it. Manual steps: # yum install rsyslog # systemctl enable rsyslog # systemctl start rsyslog
Sorry, realized this is not my component, dropping my devel_ack. Will let Saravana take a look.
Adding rsyslogd or other logger is not really advised for containers. There is a logger on the host already that should capture these messages. If debug logs are needed and manually enabled, can not also the logs from the container host be requested? It would be easier if this can be configured in the tcmu.conf configuration file to log everything to the selected tcmu-runner.log file. Is that not an option?
@John & @Niels, Yes, makesense to me. I'm okay closing this bug. Thank you very much!