Hi Dmitry--
On Fri 2017-01-06 03:39:01 -0500, Dmitry Bogatov wrote:
> [2011-09-14 15:33] Daniel Kahn Gillmor <[email protected]>
>>
>> part 1 text/plain 808
>> Package: runit
>> Version: 2.1.1-6.2
>>
>> I have a runit-monitored service that bundles a kvm instance and a
>> screen instance.
>>
>> Upon stopping that service with "sv stop foo" and then trying to restart
>> it with "sv start foo", i get these error messages in runsvdir's ARGV
>> buffer:
>>
>> runsv foo: fatal:, to setup filedescriptor for ./run: file descriptor
>> not open?
>>
>> I managed to work around the problem with:
>>
>> update-service --remove /etc/sv/foo
>> update-service --add /etc/sv/foo
>>
>> which i assume started an entirely new runsv process. I now suspect
>> that the old runsv process was in some horrible state where it had
>> somehow exhausted its old set of file descriptors.
>>
>> I have no idea how the runsv process could have gotten that way, and i
>> regret that i didn't inspect the process in more detail at the time :(
>
> control: tags -1 +moreinfo
>
> Can you please try to check this issue with runit_2.1.2-9?
This bug report is from more than 5 years ago, and i wasn't able to
diagnose it then. i don't think i've seen a recurrence of the problem,
but i never knew how to reproduce it directly, and i certainly don't
know how to test it today, sorry :/
i filed the bug report in the hopes that either (a) i'd hear a quick,
simple explanation from the maintainer (which didn't happen) or at least
(b) it would provide a place for discussion if other people were seeing
the same problem (but either no one else saw the same problem, or no one
else bothered to follow up about it).
So feel free to close this bug report as unfixable since it's a cold
case at this point :(
--dkg
