Found the culprit: a clock skew due to incorrect options in invocation
of hwclock(8). Not sure whether it will be worth trying to work around
such PEBKAC from the s6 / s6-rc side :|
On Mon, Aug 15, 2016 at 11:39:48PM +0800, Casper Ti. Vector wrote:
> On an Alpine Linux system managed using s6 (2.3.0.0) / s6-rc (0.0.3.0)
> with a fairly complex service set, if the following commands
> # echo _at_@ > /run/service/s6-svscan-log/fifo
> # tail /run/uncaught-logs/current
> are inserted before `s6-rc -u change blahblah' in the stage2 script, a
> corresponding line gets printed; however, after the s6-rc invocation,
> the same commands do not result in corresponding test line being
> printed.
>
> After the system is fully up (after the s6-rc invocation, so
> above-mentioned test fails), the following commands
> # s6-svc -k /run/service/s6-svscan-log
> # s6-svstat /run/service/s6-svscan-log
> prints
> > down (SIGKILL) 0 seconds, normally up, want up, ready 0 seconds
>
> After the SIGKILL, if the following command
> # s6-svc -u /run/service/s6-svscan-log
> is run, then the catch-all logger accepts logs again, and auto-restart
> of that service also works again.
>
> Please feel free to ask for more information when necessary.
--
My current OpenPGP key:
RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19)
7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C
Received on Mon Aug 15 2016 - 18:41:27 UTC