Bug#773766: systemd: Real problem is lack of information when service fails

[Daniel Dickinson]

On 23/12/14 04:40 PM, Michael Biebl wrote:
> 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?

To a file in /var/log/deluged/deluged.log

This file was empty (deluged was never starting and before the config is
active it logs to stdout/err I believe, which is why the output is only
in journalctl)

> 
> 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?
> 

Messages appeared in journal (journalctl) however there was no output in
syslog.  I have noticed that *none* of the boxes / vms I have upgraded
from wheezy to jessie output the journal to syslog.  I suppose this may
be a systemd upgrade bug.

Regards,

Daniel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4273 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20141225/92083232/attachment-0002.bin>