Your message dated Mon, 29 Dec 2014 13:57:23 +0100
with message-id <[email protected]>
and subject line Re: Bug#773766: systemd: Real problem is lack of information
when service fails
has caused the Debian Bug report #773766,
regarding systemd: Fails to start unconverted scripts in init.d
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
773766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773766
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-8
Severity: important
At least in the instance of deluged for which there is an initscript
in /etc/init.d/deluged but no deluged.service doing
/etc/init.d/deluged start
gives the message starting by systemctl deluged.service
however such a file does not exist anywhere on the filesystem and
deluged fails to start.
This is a rather serious regression if systemd is only going to start
services which have been converted to systemd.
-- Package-specific info:
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-58
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1+b1
ii libblkid1 2.25.2-4
ii libc6 2.19-13
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-3
ii libgcrypt20 1.6.2-4+b1
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2+b3
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-8
ii mount 2.25.2-4
ii sysv-rc 2.88dsf-58
ii udev 215-8
ii util-linux 2.25.2-4
Versions of packages systemd recommends:
ii dbus 1.8.12-1
ii libpam-systemd 215-8
Versions of packages systemd suggests:
pn systemd-ui <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 29.12.2014 um 10:23 schrieb 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.
Ok, closing the bug report then.
--
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
--- End Message ---
