Am 23.12.2014 um 02:49 schrieb Daniel Dickinson: > Package: systemd > Followup-For: Bug #773766 > > It turns there was a permissions problem on the log file directory > for deluged causing deluged failing to start, however there was a > lack of information about the failure in the canonical place to look > for for such information (syslog). > > It's great and all to have the systemctl status command, once > you finally find out about it, but such information should > also be in the logs.
Does deluged log the error to syslog directly or to stdout/stderr? In both cases the error should end up in the journal, and can be queueried via systemctl status deluged.service and journalctl (in the latter case, you can use the builtin filter mechanisms like -u deluged.service or the path to the deluged binary). If a syslogger like syslog-ng or rsyslog is installed, the journal messages should also end up in the syslog (depending on the configuration, you should check files like /var/log/daemon.log,syslog,messages). Are you saying, that no log messages appeared in the journal and/or syslog? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
