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

[Daniel Dickinson]

On 26/12/14 08:48 PM, Michael Biebl wrote:
> Am 26.12.2014 um 06:11 schrieb Daniel Dickinson:
>>
>>
>> On 25/12/14 01:27 PM, Michael Biebl wrote:
>>>>
>>>> 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.
>>>
>>> Which syslogger do you have installed, rsyslog, syslog-ng? 
>>>
>> rsyslog with config that had been edited but reverted to defaults
>> (however probably detected as changed and therefore new defaults not
>> installed).
> 
> What is the output of
> systemctl status syslog.socket syslog.service
> 
> 

Er, sorry, no longer have the non-working configs.  Reverted rsyslog
configs completely to defaults using dpkg -i --force-confnew and it all
works now.

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/20141229/c0002abf/attachment-0002.bin>