Question

0

"Client Critical Interface eth0/2 is down or doesn't have any link-local address" while starting a service after the network is up

rated 0 times [ 0] [ 0] / answers: 1 / hits: 2533 / 1 Year ago, sun, may 7, 2023, 6:47:04

I'm trying to start an upstart job after making sure networking interfaces are up.

This is what I have now:

start on started network-interface INTERFACE=eth0

stop on runlevel [!2345]



pre-start script

    test -x /usr/sbin/dibbler-client || { stop; exit 0; }

    test -c /dev/null || { stop; exit 0; }



end script



exec /usr/sbin/dibbler-client start 2>&1 > /dev/null

The problem is that dibbler is obviously started too soon since i'm getting Client Critical Interface eth0/2 is down or doesn't have any link-local address.
Is there a simple way of solving this with events or i'd have to do it in the pre-start ?
I'm using only /etc/networking/interfaces and the networking script for configuration. So no network manager.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

ugeeport

Add To Favorites

Follow

Total Points: 181

Total Questions: 108

Total Answers: 99

Location: El Salvador

Member since Tue, Jun 29, 2021

3 Years ago

ugeeport questions

1 how do I fix youtube-dl: running it gives error message about incorrect syntax

Sun, Jun 20, 21, 16:51, 3 Years ago

1 Graphics Issue Since Update, Kubuntu Plasma, Seems Worse With Greater System Resource Use

Sat, Nov 20, 21, 10:59, 3 Years ago

1 Recompile 20.04 HWE kernel?

Sat, Jul 23, 22, 19:06, 2 Years ago

1 How do get grid workspaces in ubuntu 20.10?

Wed, Oct 12, 22, 02:26, 2 Years ago

1 How can I create a custom terminal command with a variable argument?

Mon, Aug 29, 22, 22:50, 2 Years ago

View All

answered 1 Year ago kneducator · Accepted Answer

The main problem was that the ipv6 wasn't started even though the interface was up.

Doing some browsing there was a suggestion to start the ipv6 module right during boot by editing the /etc/modules .

Another solution is supposedly to enable the inactive-mode in the dibbler configuration /etc/dibbler/client.conf

I wanted to do it purely in upstart script so here's the .conf file that I tested and seems to be working:

# dibbler-client

#

# The dibbler dhcpv6 client



description     "dibbler-client"



start on (started network-interface

          or started network-manager

          or started networking)

stop on runlevel [!2345]



pre-start script

    test -x /usr/sbin/dibbler-client || { stop; exit 0; }

    test -c /dev/null || { stop; exit 0; }



    TIMEOUT=50 #5 second timeout - eatch iteration sleeps for 1/10th of a second

    LOG_FILE=/tmp/dibbler_upstart.log



    until [ $TIMEOUT -eq 0 ]; do

        if ip addr show dev eth0 | grep -e 'inet6.*link.$'; then

                echo "Detected inet6 link-local, exiting" >> $LOG_FILE

                ip addr show dev eth0 >> $LOG_FILE

                exit 0;

        fi

        TIMEOUT=$((TIMEOUT-1))

        sleep .1

    done



    echo "Timeout waiting for IP address" >> $LOG_FILE

    exit 1;



end script



exec /usr/sbin/dibbler-client start 2>&1 > /dev/null

If someone knows how to detect ipv6 status with events that would be a cleaner solution.