Hi,
On 26/01/17 21:49, Michael Biebl wrote:
> Am 26.01.2017 um 15:44 schrieb Michael Biebl:
>> Am 18.01.2017 um 14:31 schrieb James Cowgill:
>
>>> After debugging a bit I found this commit which seems likely to be the
>>> cause. I haven't actually tested 215 with the patch though:
>>>
Am 26.01.2017 um 15:44 schrieb Michael Biebl:
> Am 18.01.2017 um 14:31 schrieb James Cowgill:
>> After debugging a bit I found this commit which seems likely to be the
>> cause. I haven't actually tested 215 with the patch though:
>>
Hi James
Am 18.01.2017 um 14:31 schrieb James Cowgill:
> I've checked for this bug across various mips machines, and it is only
> present on the big-endian machines running jessie. I then managed to
> bisect it to somewhere between 215 and 217.
>
> After debugging a bit I found this commit which
Processing control commands:
> fixed -1 217-1
Bug #774430 [systemd] systemd: service incorrectly marked as not reloadable
Marked as fixed in versions systemd/217-1.
--
774430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: fixed -1 217-1
Hi,
On 22/12/16 01:03, Michael Biebl wrote:
> Hi James
>
> Am 22.12.2016 um 01:48 schrieb James Cowgill:
>
>> # dpkg -s systemd | grep ^Version
>> Version: 232-7
>>
>
> Could you test with v215 from jessie as well on this system?
> It would be good to know if this
]] Michael Biebl
Hi Michael,
thanks for looking into this.
> Tollef, can you run
> systemctl reload syslog-ng.service
> and see if that works?
It seems to work:
: tfheen@minkus ~ > sudo systemctl reload syslog-ng.service
: tfheen@minkus ~ > echo $?
0
--
Tollef Fog Heen
UNIX is user
Hi James
Am 22.12.2016 um 01:48 schrieb James Cowgill:
> # dpkg -s systemd | grep ^Version
> Version: 232-7
>
Could you test with v215 from jessie as well on this system?
It would be good to know if this issue has already been fixed upstream.
Running a git bisect might then help to identify
Hi,
On 21/12/16 23:49, Michael Biebl wrote:
> Something I just noticed: All boolean properties are no, not just CanReload.
> And checking on minkus, this seems to happen for other services as well,
> like
>
> $ systemctl show ssh.service | grep no$
> PermissionsStartOnly=no
>
Am 22.12.2016 um 01:16 schrieb Michael Biebl:
> More odd issues:
>
> biebl@minkus:~$ systemctl status
> ● minkus
> State: running
> Jobs: 7833565 queued
>Failed: 7833565 units
> Since: Do 1970-01-01 00:00:07 UTC; 46 years 11 months ago
At this point I'm pretty much stuck as I
Am 22.12.2016 um 00:49 schrieb Michael Biebl:
> Digging deeper, I wonder whether this is just a presentation issue, i.e.
> the output of systemctl show simply being wrong but the internal
> representation actually being correct.
> When checking systemd-analyze dump, it seems to show the correct
Am 02.01.2015 um 19:11 schrieb Tollef Fog Heen:
> minkus% sudo systemctl show syslog-ng.service | cat
...
> CanStart=no
> CanStop=no
> CanReload=no
> CanIsolate=no
> StopWhenUnneeded=no
> RefuseManualStart=no
> RefuseManualStop=no
> AllowIsolate=no
> DefaultDependencies=no
>
I'm experience the same, also with syslog-ng on a Debian/Jessie system
(powerpc, upgraded from Debian/Wheezy not too long ago):
# dpkg-query --status syslog-ng-core systemd | egrep ^Package\|^Version
Package: syslog-ng-core
Version: 3.5.6-2+b1
Package: systemd
Version: 215-17
# systemctl -p
12 matches
Mail list logo
