networking.service - Error

  • Hi
    I hav some trouble while booting my machine. It takes nearly 5 minutes to boot.
    And i think i have trouble with networking.service.
    This exit's with an error.
    Here some "log's":




    journalctl -u networking.service





    Anyone a Idea ?


    THX

    Cooler Master Elite 110
    ASRock Q1900-ITX
    GeIL Green SO-DIMM 2x2GB, DDR3L-1333
    3x Western Digital WD green 3TB
    1x 60GB BOOT-SSD
    be quiet! System Power 7 300W

    • Offizieller Beitrag

    Try this


    chmod -x /etc/network/if-up.d/openmediavault-issue


    Restart networking via systemd. Anyway seems like your network is still working since I think you pasted all those logs from ssh right?


    To find out about the delay in boot try



    journalctl -b | curl -F 'sprunge=<-' http://sprunge.us


    This will give you a link so you can paste it here

  • Thanks for this hint.


    chmod -x /etc/network/if-up.d/openmediavault-issue


    works, and so the Bootdelay is gone.

    Cooler Master Elite 110
    ASRock Q1900-ITX
    GeIL Green SO-DIMM 2x2GB, DDR3L-1333
    3x Western Digital WD green 3TB
    1x 60GB BOOT-SSD
    be quiet! System Power 7 300W

  • Hi Subzero,


    could you also offer some advice about my network.service error?


    I am similarly getting a 5 minute boot delay which occurs while waiting for DHCP, however unfortunately in my case the network doesn't come up after that until I physically go to the server and enter:
    dhclient bond0
    after which the network starts immediately.


    I still had to wait 5 minutes after chmod -x /etc/network/if-up.d/openmediavault-issue


    My


    journalctl is at http://sprunge.us/LdCS
    and
    systemctlstatus networking.service is at http://sprunge.us/gQDB


    Thanks

    KnobblySnail


    OMV6 on Asrock E3C224D2I, Xeon E3-1230Lv3, 8Gb, WD Red 3Tb x3 zfs, 120GB Samsung EVO mSATA, CoolerMaster V550S, in a Fractal Design Node 304

  • Thanks, I thought the acknowledgement was coming from the DHCP server, but defining the static IP from the OMV end is an effective solution :)


    Changing to a static IP identified an advantage of my router's DHCP - it identifies the hostname to other users on the network. Manually adding the hostname and IP to the router's Static DNS list re-established access.

    KnobblySnail


    OMV6 on Asrock E3C224D2I, Xeon E3-1230Lv3, 8Gb, WD Red 3Tb x3 zfs, 120GB Samsung EVO mSATA, CoolerMaster V550S, in a Fractal Design Node 304

    Einmal editiert, zuletzt von knobblysnail () aus folgendem Grund: I imagine the hostname resolution stopped after the previous DHCP lease expired about a day after I changed to the static IP

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!