1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] Re: Openrc service crash

    From =?UTF-8?Q?Holger_Hoffst=c3=a4tte?=@21:1/5 to Michael on Sat Apr 8 12:10:01 2023
    On 2023-04-08 10:41, Michael wrote:
    On Saturday, 8 April 2023 09:33:23 BST Michael wrote:
    On Saturday, 8 April 2023 09:32:31 BST Michael wrote:
    On Saturday, 8 April 2023 09:28:16 BST Arve Barsnes wrote:
    On Sat, 8 Apr 2023 at 10:00, Michael <confabulate@kintzios.com> wrote: >>>>> It was probably the addition of IPv6 - as a workaround I added 'sleep >>>>> 5s'
    before the gatling init.d exec command and it now starts normally.

    If it was indeed the network that was missing, you could try changing
    the service from "need" to "after" starting the net service.

    Add to /etc/rc.conf:
    rc_gatling_after="net"

    Regards,
    Arve

    Thanks Arve, I will try it. Should this replace the "need net" string
    here, or added somewhere else?

    depend() {

    need net

    }

    Oops! Please ignore my question ... I didn't have enough coffee yet. :-)

    OK, I added rc_gatling_after="net" in rc.conf, but it didn't work. gatling crashed. However, adding 'sleep 5s' in its init.d startup script works. What
    might be causing this discrepancy?

    Without having more information, I wouldn't be surprised if it's the notorious IPv6 DAD delay:

    https://bugs.gentoo.org/831743

    cheers
    Holger

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Sat Apr 8 12:40:01 2023
    On Saturday, 8 April 2023 11:08:06 BST Holger Hoffstätte wrote:
    On 2023-04-08 10:41, Michael wrote:

    OK, I added rc_gatling_after="net" in rc.conf, but it didn't work.
    gatling
    crashed. However, adding 'sleep 5s' in its init.d startup script works. What might be causing this discrepancy?

    Without having more information, I wouldn't be surprised if it's the notorious IPv6 DAD delay:

    https://bugs.gentoo.org/831743

    cheers
    Holger

    Yes, quite likely. Although this application is configured to listen only on IPv4, the problem manifested after I moved this system on a new network port which also has IPv6.

    I've come across posts complaining about services crashing at startup, but causal attribution was somewhat conflated between 1Gb switch gear and IPv6. Since this PC was on the same 1Gbps switch before and only the addition of IPv6 coincided with this problem, I'd think the bug you mention is a more probable cause.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)