On Tue, May 14, 2019 at 03:33:59PM +0200, Ludovic Courtès wrote:
> There are reasons to believe that this issue is fixed by the Shepherd 0.6.1:
>
> https://issues.guix.info/issue/35550
>
> Could you check somehow if the bug shows up again?
The bug disappeared for me a couple of reboots after r
Hi Leo,
Leo Famulari skribis:
> One interesting tidbit is that the PID file '/var/run/sshd.pid' is not
> created anymore. And if I create an empty PID file by hand, it is
> removed after trying to start the ssh-daemon service. Also, the sshd
> user's home '/var/run/sshd' does not exist, and is s
Hi Leo,
Leo Famulari skribis:
> Since the update to Shepherd 0.4.0, I've found that OpenSSH's sshd is
> killed almost immediately after it starts with signal 15. I confirmed
> the issue started with the Shepherd upgrade by bisecting our Git
> history.
>
> I can reproduce the issue from commit
>
On 19.07.2018 15:15, Clément Lassieur wrote:
> [...]
> Martin, could you please test it? (You just need to 'guix pull' and try
> again.) Leo, if you confirm my analysis, could you please unmerge the
> bugs?
>
> Thanks,
> Clément
>
It still does not work for me.
Attached are my guix version, dme
On Thu, Jul 19, 2018 at 04:26:59PM +0200, Clément Lassieur wrote:
> Clément Lassieur writes:
>
> > Leo, if you confirm my analysis, could you please unmerge the bugs?
>
> I did it, because Eric confirmed the fix.
Thanks, sorry for the confusion!
signature.asc
Description: PGP signature
Clément Lassieur writes:
> Leo, if you confirm my analysis, could you please unmerge the bugs?
I did it, because Eric confirmed the fix.
Clément
Heya,
Martin Castillo writes:
> On 06.05.2018 21:50, Leo Famulari wrote:
>> On Fri, May 04, 2018 at 04:01:52AM +0200, Martin Castillo wrote:
>>> Sorry, I forgot to mention that I have the same problem. But I had it
>>> already with shepherd 0.3.
>>
>> Interesting. Did it ever work for you on
On 06.05.2018 21:50, Leo Famulari wrote:
> On Fri, May 04, 2018 at 04:01:52AM +0200, Martin Castillo wrote:
>> Sorry, I forgot to mention that I have the same problem. But I had it
>> already with shepherd 0.3.
>
> Interesting. Did it ever work for you on that system?
>
> that system?
Do you
On Fri, May 04, 2018 at 04:01:52AM +0200, Martin Castillo wrote:
> Sorry, I forgot to mention that I have the same problem. But I had it
> already with shepherd 0.3.
Interesting. Did it ever work for you on that system?
signature.asc
Description: PGP signature
Sorry, I forgot to mention that I have the same problem. But I had it already
with shepherd 0.3.
On Thu, May 03, 2018 at 05:16:32PM +0200, Martin Castillo wrote:
>
>
> On 01.05.2018 22:43, Ludovic Courtès wrote:
> >> Maybe one could somehow strace herd, or change the make-kill-destructor
> >> to log every time it is being executed?
> >
> > ‘herd status sshd’ displays the last time sshd was
On 01.05.2018 22:43, Ludovic Courtès wrote:
>> Maybe one could somehow strace herd, or change the make-kill-destructor
>> to log every time it is being executed?
>
> ‘herd status sshd’ displays the last time sshd was respawned, but the
> info ‘herd’ receives actually includes the dates of all th
Martin Castillo skribis:
> (resending because I forgot to CC the list)
>
> On 06.04.2018 14:41, Leo Famulari wrote:
>>> Hmm, where could that SIGTERM come from? ‘make-kill-destructor’ uses it
>>> when a service is stopped, and otherwise it’s sent when we’re shutting
>>> the system down. But her
(resending because I forgot to CC the list)
On 06.04.2018 14:41, Leo Famulari wrote:
>> Hmm, where could that SIGTERM come from? ‘make-kill-destructor’ uses it
>> when a service is stopped, and otherwise it’s sent when we’re shutting
>> the system down. But here?…
>
> Indeed, that is the questio
Leo Famulari skribis:
> On Fri, Apr 06, 2018 at 10:21:09AM +0200, Ludovic Courtès wrote:
> [...]
>> > Server listening on 0.0.0.0 port 22.
>> > debug1: Bind to port 22 on ::.
>> > Server listening on :: port 22.
>> > Received signal 15; terminating.
>> > --
>>
>> Hmm, where could that SIGTER
On Fri, Apr 06, 2018 at 10:21:09AM +0200, Ludovic Courtès wrote:
[...]
> > Server listening on 0.0.0.0 port 22.
> > debug1: Bind to port 22 on ::.
> > Server listening on :: port 22.
> > Received signal 15; terminating.
> > --
>
> Hmm, where could that SIGTERM come from? ‘make-kill-destructor
Hi Leo,
Leo Famulari skribis:
> Since the update to Shepherd 0.4.0, I've found that OpenSSH's sshd is
> killed almost immediately after it starts with signal 15. I confirmed
> the issue started with the Shepherd upgrade by bisecting our Git
> history.
>
> I can reproduce the issue from commit
>
Since the update to Shepherd 0.4.0, I've found that OpenSSH's sshd is
killed almost immediately after it starts with signal 15. I confirmed
the issue started with the Shepherd upgrade by bisecting our Git
history.
I can reproduce the issue from commit
b6beda1d6b9093a8493b5c3cde33ed522242c451 (gnu:
18 matches
Mail list logo
