ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Restarting networking service fails - Ubuntu 16.04

    IT Discussion
    linux ubuntu ubuntu 16.04
    5
    22
    22.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      Markferron
      last edited by

      Oh and the error hah...

      itdept@IT-DHCP:~$ systemctl status networking.service
      ● networking.service - Raise network interfaces
         Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
        Drop-In: /run/systemd/generator/networking.service.d
                 └─50-insserv.conf-$network.conf
         Active: failed (Result: exit-code) since Tue 2018-10-23 14:33:55 EDT; 8min ago
           Docs: man:interfaces(5)
        Process: 2227 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
        Process: 2221 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited
       Main PID: 2227 (code=exited, status=1/FAILURE)
      
      Oct 23 14:33:55 IT-DHCP systemd[1]: Starting Raise network interfaces...
      Oct 23 14:33:55 IT-DHCP ifup[2227]: RTNETLINK answers: File exists
      Oct 23 14:33:55 IT-DHCP ifup[2227]: Failed to bring up ens4.
      Oct 23 14:33:55 IT-DHCP systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
      Oct 23 14:33:55 IT-DHCP systemd[1]: Failed to start Raise network interfaces.
      Oct 23 14:33:55 IT-DHCP systemd[1]: networking.service: Unit entered failed state.
      Oct 23 14:33:55 IT-DHCP systemd[1]: networking.service: Failed with result 'exit-code'.
      lines 1-17/17 (END)
      
      
      1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller
        last edited by

        What does ...

        sudo ifup -v ens4
        

        ... produce as output?

        M 1 Reply Last reply Reply Quote 0
        • M
          Markferron @scottalanmiller
          last edited by

          @scottalanmiller

          itdept@IT-DHCP:~$ sudo ifup -v ens4
          Configuring interface ens4=ens4 (inet)
          /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
          run-parts: executing /etc/network/if-pre-up.d/ethtool
          run-parts: executing /etc/network/if-pre-up.d/ifenslave
          + [ inet = meta ]
          + IF_BOND_SLAVES=
          + [  ]
          + [  ]
          + [ -z  ]
          + exit
          run-parts: executing /etc/network/if-pre-up.d/vlan
          /bin/ip addr add 10.0.33.110/255.255.224.0 broadcast 10.0.63.255          dev en
          RTNETLINK answers: File exists
          Failed to bring up ens4.
          itdept@IT-DHCP:~$
          
          
          1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller
            last edited by

            @Markferron said in Restarting networking service fails - Ubuntu 16.04:

            RTNETLINK answers: File exists

            Are you perhaps running Network Manager on there?

            1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller
              last edited by

              Try...

              sudo ifdown ens4
              sudo ifup -v ens4
              
              M 1 Reply Last reply Reply Quote 0
              • black3dynamiteB
                black3dynamite
                last edited by

                sudo systemctl restart NetworkManager.service

                1 Reply Last reply Reply Quote 0
                • black3dynamiteB
                  black3dynamite
                  last edited by black3dynamite

                  You misspelled dns-nameserver

                  M 1 Reply Last reply Reply Quote 1
                  • M
                    Markferron @scottalanmiller
                    last edited by

                    @scottalanmiller
                    I think it worked...at least I don't see angry red text or the word fail anywhere...

                    itdept@IT-DHCP:~$ sudo ifdown ens4
                    itdept@IT-DHCP:~$ sudo ifup -v ens4
                    Configuring interface ens4=ens4 (inet)
                    /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
                    run-parts: executing /etc/network/if-pre-up.d/ethtool
                    run-parts: executing /etc/network/if-pre-up.d/ifenslave
                    + [ inet = meta ]
                    + IF_BOND_SLAVES=
                    + [  ]
                    + [  ]
                    + [ -z  ]
                    + exit
                    run-parts: executing /etc/network/if-pre-up.d/vlan
                    /bin/ip addr add 10.0.33.110/255.255.224.0 broadcast 10.0.63.255          dev en                                                                                        s4 label ens4
                    /bin/ip link set dev ens4   up
                     /bin/ip route add default via 10.0.32.2  dev ens4 onlink
                    /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d
                    run-parts: executing /etc/network/if-up.d/000resolvconf
                    run-parts: executing /etc/network/if-up.d/ethtool
                    run-parts: executing /etc/network/if-up.d/ifenslave
                    + [ inet = meta ]
                    + [  ]
                    run-parts: executing /etc/network/if-up.d/ip
                    run-parts: executing /etc/network/if-up.d/openssh-server
                    run-parts: executing /etc/network/if-up.d/upstart
                    run-parts: executing /e
                    
                    1 Reply Last reply Reply Quote 0
                    • M
                      Markferron @black3dynamite
                      last edited by

                      @black3dynamite Yikes that's embarrassing...thank you.

                      1 Reply Last reply Reply Quote 1
                      • dafyreD
                        dafyre
                        last edited by

                        @Markferron -- the little things that will come back and bite you.

                        M 1 Reply Last reply Reply Quote 1
                        • M
                          Markferron @dafyre
                          last edited by

                          @dafyre said in Restarting networking service fails - Ubuntu 16.04:

                          @Markferron -- the little things that will come back and bite you.

                          You've dealt with me too much. It's too easy for you.

                          dafyreD 1 Reply Last reply Reply Quote 0
                          • dafyreD
                            dafyre @Markferron
                            last edited by

                            @Markferron said in Restarting networking service fails - Ubuntu 16.04:

                            @dafyre said in Restarting networking service fails - Ubuntu 16.04:

                            @Markferron -- the little things that will come back and bite you.

                            You've dealt with me too much. It's too easy for you.

                            Not so much that, as I've been bitten in my (*@)&#$ more times than I care to count.

                            scottalanmillerS 1 Reply Last reply Reply Quote 2
                            • scottalanmillerS
                              scottalanmiller @dafyre
                              last edited by

                              @dafyre said in Restarting networking service fails - Ubuntu 16.04:

                              @Markferron said in Restarting networking service fails - Ubuntu 16.04:

                              @dafyre said in Restarting networking service fails - Ubuntu 16.04:

                              @Markferron -- the little things that will come back and bite you.

                              You've dealt with me too much. It's too easy for you.

                              Not so much that, as I've been bitten in my (*@)&#$ more times than I care to count.

                              Mark, stop biting him!

                              1 Reply Last reply Reply Quote 2
                              • DustinB3403D
                                DustinB3403
                                last edited by

                                Okay I'll bite, why the hell are you deploying 16.04?!

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  Markferron @DustinB3403
                                  last edited by

                                  @DustinB3403 said in Restarting networking service fails - Ubuntu 16.04:

                                  Okay I'll bite, why the hell are you deploying 16.04?!

                                  I'm having issues with 18, and I need to get something up and running quickly. Do plan on moving it to 18 though.

                                  DustinB3403D black3dynamiteB scottalanmillerS 3 Replies Last reply Reply Quote 0
                                  • DustinB3403D
                                    DustinB3403 @Markferron
                                    last edited by

                                    @markferron wouldn't the fix here be to fix the issue in 18?

                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      Markferron @DustinB3403
                                      last edited by

                                      @DustinB3403
                                      Hah, probably. Figured this would be the quicker route.

                                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                                      • black3dynamiteB
                                        black3dynamite @Markferron
                                        last edited by black3dynamite

                                        @Markferron said in Restarting networking service fails - Ubuntu 16.04:

                                        @DustinB3403 said in Restarting networking service fails - Ubuntu 16.04:

                                        Okay I'll bite, why the hell are you deploying 16.04?!

                                        I'm having issues with 18, and I need to get something up and running quickly. Do plan on moving it to 18 though.

                                        Network works a little different with 18.04 and up. Netplan is how you manage your network configuration.
                                        https://netplan.io/

                                        1 Reply Last reply Reply Quote 0
                                        • scottalanmillerS
                                          scottalanmiller @Markferron
                                          last edited by

                                          @Markferron said in Restarting networking service fails - Ubuntu 16.04:

                                          @DustinB3403 said in Restarting networking service fails - Ubuntu 16.04:

                                          Okay I'll bite, why the hell are you deploying 16.04?!

                                          I'm having issues with 18, and I need to get something up and running quickly. Do plan on moving it to 18 though.

                                          You had issues on 16.04, too.

                                          1 Reply Last reply Reply Quote 0
                                          • scottalanmillerS
                                            scottalanmiller @Markferron
                                            last edited by

                                            @Markferron said in Restarting networking service fails - Ubuntu 16.04:

                                            @DustinB3403
                                            Hah, probably. Figured this would be the quicker route.

                                            Once in a great while that is true, generally working on things that are current is faster. Often in the short run, almost always in the long run.

                                            18.10 is out. So you are a full four versions behind now.

                                            1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post