Re: Problems with recent versions of s6-rc

I just found myself being extremely careless this time: when I said "the alpine testing repository", I really meant `edge/testing', but s6-rc v0.2.1.1 should be in `edge/main', so probably I just installed s6-rc v0.2.0.1 from `v3.6/main', and rediscovered the original problems with the old alpine

Re: Problems with recent versions of s6-rc

The s6-rc-compile segfault and the s6-rc failure still occur with `s6-rc 0.2.1.1-r0' from the alpine testing repository. -- My current OpenPGP key: RSA4096/0x227E8CAAB7AA186C (expires: 2020.10.19) 7077 7781 B859 5166 AE07 0286 227E 8CAA B7AA 186C

Re: Problems with recent versions of s6-rc

Thanks. Seems I need to pin the s6-related packages at alpine 3.5.x on my servers for a longer time... On Sun, Jun 04, 2017 at 11:21:30AM +, Laurent Bercot wrote: > We have confirmed that it is an Alpine problem. We're not sure > exactly where the problem occurs (the usual suspect, grsec,

Re: Problems with recent versions of s6-rc

Hello, is there any progress on this issue? We have confirmed that it is an Alpine problem. We're not sure exactly where the problem occurs (the usual suspect, grsec, has been innocented), but we know it's related to the Alpine package build and to virtualization. In any case, the s6-rc code

Re: Problems with recent versions of s6-rc

Hello, is there any progress on this issue? On Fri, May 26, 2017 at 04:00:06AM +, Laurent Bercot wrote: > Tomorrow I'll report that to the Alpine devs, and investigate what > could have gone wrong. And I'll have to either pay more attention to > Alpine quality control, or drop maintenance

Re: Problems with recent versions of s6-rc

Not even in a VirtualBox VM? Seems more interesting than I thought... I hadn't tried... I cannot reproduce when compiling everything by hand on my machines, but I followed the procedure you outlined and I am indeed able to reproduce on a Virtualbox VM running the Alpine packages. The fact

Re: Problems with recent versions of s6-rc

On Fri, May 26, 2017 at 12:15:39AM +, Laurent Bercot wrote: > When it's about debug information such as strace outputs ;) > Except that when you send a file to a mailing-list Well this is the problem I neglected: it is

Re: Problems with recent versions of s6-rc

Well I think pastebins really tend to be unreliable (most importantly, content disappearing at unexpected time), so small files (whether text or binary, as long as they are relevant) are best posted directly to the mail list No. When it's about debug information such as strace outputs, the

Re: Problems with recent versions of s6-rc

Well I think pastebins really tend to be unreliable (most importantly, content disappearing at unexpected time), so small files (whether text or binary, as long as they are relevant) are best posted directly to the mail list; and since compression saves space, tarballs and zipballs are suitable

Re: Problems with recent versions of s6-rc

A person on this list kindly told that no attachment appeared; but actually I *did* attach a gzip'ed version of the log as `rc-err.log.gz', so we are perhaps facing a problem with some steps in the mail delivery. It is intentional that binary attachments are stripped when sent to the list. I

Re: Problems with recent versions of s6-rc

A person on this list kindly told that no attachment appeared; but actually I *did* attach a gzip'ed version of the log as `rc-err.log.gz', so we are perhaps facing a problem with some steps in the mail delivery. Attached is a tgz version; please do tell me if it disappears again. On Thu, May 25,

Re: Problems with recent versions of s6-rc

After reboot-looping a test VM for many times, this is also reproduced successfully; attached is the log. On Thu, May 25, 2017 at 09:07:26PM +0800, Casper Ti. Vector wrote: > The issue with `s6-rc' seems to be difficult to reproduce when `s6-rc' > is debugged by strace, so I am unable to produce

Re: Problems with recent versions of s6-rc

Not even in a VirtualBox VM? Seems more interesting than I thought... Attached is the logs of `s6-rc-compile' for the three cases. The issue with `s6-rc' seems to be difficult to reproduce when `s6-rc' is debugged by strace, so I am unable to produce a log for it now. On Thu, May 25, 2017 at

Re: Problems with recent versions of s6-rc

I experienced this when updating Alpine from v3.5.2 to v3.6.0 on these machines; the v3.6.0 release have already covered skalibs v2.5.1.1. Can you then please send me a strace of the failing programs? I can't reproduce. -- Laurent

Re: Problems with recent versions of s6-rc

On Thu, May 25, 2017 at 10:17:22AM +, Laurent Bercot wrote: > All the problems you report should be fixed with skalibs-2.5.1.1, which > should already be available in Alpine. Are you still experiencing issues > with skalibs-2.5.1.1 ? I experienced this when updating Alpine from v3.5.2 to

Re: Problems with recent versions of s6-rc

All the problems you report should be fixed with skalibs-2.5.1.1, which should already be available in Alpine. Are you still experiencing issues with skalibs-2.5.1.1 ? * Incompatibility of the compiled database: s6-rc commit 543c1405 breaks the backwards compatibility of the compiled

Re: Problems with recent versions of s6-rc

Additionally, on my machines, which now use freshly compiled databases, when running `s6-rc -u change default' in `rc.init', with a small but significant probability (one in a few) the procedure ends up with this error: > s6-svlisten1: fatal: unable to ftrigr_update: Broken pipe > s6-rc: warning: