Error: Connection activation failed: Device not managed by NetworkManager or unavailable












0














I have a CentOS server that is currently using eth1 network interface. I am trying to change it to eth0 and have configured it but when I try ifup eth0 I get this error message:



Error: Connection activation failed: Device not managed by NetworkManager or unavailable


The contents of /etc/sysconfig/network-scripts/ifcfg-eth0 are as follows:



DEVICE=eth0
TYPE=Ethernet
UUID=6519f5da-294a-45e3-b9dc-b8aa12c5fda3
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME="System eth0"
HWADDR=00:19:99:D5:56:95
PEERDNS=yes
PEERROUTES=yes
LAST_CONNECT=1509619482


Please can someone help in getting eth0 up?










share|improve this question














bumped to the homepage by Community 5 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.




















    0














    I have a CentOS server that is currently using eth1 network interface. I am trying to change it to eth0 and have configured it but when I try ifup eth0 I get this error message:



    Error: Connection activation failed: Device not managed by NetworkManager or unavailable


    The contents of /etc/sysconfig/network-scripts/ifcfg-eth0 are as follows:



    DEVICE=eth0
    TYPE=Ethernet
    UUID=6519f5da-294a-45e3-b9dc-b8aa12c5fda3
    ONBOOT=yes
    NM_CONTROLLED=yes
    BOOTPROTO=dhcp
    DEFROUTE=yes
    IPV4_FAILURE_FATAL=yes
    IPV6INIT=no
    NAME="System eth0"
    HWADDR=00:19:99:D5:56:95
    PEERDNS=yes
    PEERROUTES=yes
    LAST_CONNECT=1509619482


    Please can someone help in getting eth0 up?










    share|improve this question














    bumped to the homepage by Community 5 mins ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.


















      0












      0








      0







      I have a CentOS server that is currently using eth1 network interface. I am trying to change it to eth0 and have configured it but when I try ifup eth0 I get this error message:



      Error: Connection activation failed: Device not managed by NetworkManager or unavailable


      The contents of /etc/sysconfig/network-scripts/ifcfg-eth0 are as follows:



      DEVICE=eth0
      TYPE=Ethernet
      UUID=6519f5da-294a-45e3-b9dc-b8aa12c5fda3
      ONBOOT=yes
      NM_CONTROLLED=yes
      BOOTPROTO=dhcp
      DEFROUTE=yes
      IPV4_FAILURE_FATAL=yes
      IPV6INIT=no
      NAME="System eth0"
      HWADDR=00:19:99:D5:56:95
      PEERDNS=yes
      PEERROUTES=yes
      LAST_CONNECT=1509619482


      Please can someone help in getting eth0 up?










      share|improve this question













      I have a CentOS server that is currently using eth1 network interface. I am trying to change it to eth0 and have configured it but when I try ifup eth0 I get this error message:



      Error: Connection activation failed: Device not managed by NetworkManager or unavailable


      The contents of /etc/sysconfig/network-scripts/ifcfg-eth0 are as follows:



      DEVICE=eth0
      TYPE=Ethernet
      UUID=6519f5da-294a-45e3-b9dc-b8aa12c5fda3
      ONBOOT=yes
      NM_CONTROLLED=yes
      BOOTPROTO=dhcp
      DEFROUTE=yes
      IPV4_FAILURE_FATAL=yes
      IPV6INIT=no
      NAME="System eth0"
      HWADDR=00:19:99:D5:56:95
      PEERDNS=yes
      PEERROUTES=yes
      LAST_CONNECT=1509619482


      Please can someone help in getting eth0 up?







      centos networking






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 6 '17 at 18:24









      JackJack

      112




      112





      bumped to the homepage by Community 5 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 5 mins ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
























          2 Answers
          2






          active

          oldest

          votes


















          0














          system-config-network



          select the eth0 device and hit the Edit button
          and uncheck the "Controlled by network manager" check box and check the box for Activating the port when the computer starts up. Save and quit in there.



          Now run system-config-services and stop/disable NetworkManager and start/enabled network service.



          This works for me






          share|improve this answer





























            0














            If you run ifconfig -a or ip link show as root, does the eth0 interface appear in the output? Does it have the MAC address that ís specified in the /etc/sysconfig/network-scripts/ifcfg-eth0 file on the HWADDR= line?



            If it is not there at all, then the driver for the NIC has probably not been loaded yet, or has a problem that prevents it from loading.
            If it has an unexpected name, you may have a problem with NIC naming.



            If the NIC is there with the expected name, but refuses to activate, it might be a firmware loading problem: some NICs require firmware to work, and if the necessary firmware file is not available, the driver cannot activate the NIC. If this is the problem, then the dmesg | less listing will usually contain one or more messages indicating that the system cannot load a specific firmware file. Once you know the name of the firmware file, you can search for it. Make sure the linux-firmware-<YYYYMMDD>-<version number> RPM package is installed: it includes a large collection of firmware files for various hardware.






            share|improve this answer





















              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "106"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402891%2ferror-connection-activation-failed-device-not-managed-by-networkmanager-or-una%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              system-config-network



              select the eth0 device and hit the Edit button
              and uncheck the "Controlled by network manager" check box and check the box for Activating the port when the computer starts up. Save and quit in there.



              Now run system-config-services and stop/disable NetworkManager and start/enabled network service.



              This works for me






              share|improve this answer


























                0














                system-config-network



                select the eth0 device and hit the Edit button
                and uncheck the "Controlled by network manager" check box and check the box for Activating the port when the computer starts up. Save and quit in there.



                Now run system-config-services and stop/disable NetworkManager and start/enabled network service.



                This works for me






                share|improve this answer
























                  0












                  0








                  0






                  system-config-network



                  select the eth0 device and hit the Edit button
                  and uncheck the "Controlled by network manager" check box and check the box for Activating the port when the computer starts up. Save and quit in there.



                  Now run system-config-services and stop/disable NetworkManager and start/enabled network service.



                  This works for me






                  share|improve this answer












                  system-config-network



                  select the eth0 device and hit the Edit button
                  and uncheck the "Controlled by network manager" check box and check the box for Activating the port when the computer starts up. Save and quit in there.



                  Now run system-config-services and stop/disable NetworkManager and start/enabled network service.



                  This works for me







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Mar 30 '18 at 5:42









                  Marimuthu SMarimuthu S

                  1




                  1

























                      0














                      If you run ifconfig -a or ip link show as root, does the eth0 interface appear in the output? Does it have the MAC address that ís specified in the /etc/sysconfig/network-scripts/ifcfg-eth0 file on the HWADDR= line?



                      If it is not there at all, then the driver for the NIC has probably not been loaded yet, or has a problem that prevents it from loading.
                      If it has an unexpected name, you may have a problem with NIC naming.



                      If the NIC is there with the expected name, but refuses to activate, it might be a firmware loading problem: some NICs require firmware to work, and if the necessary firmware file is not available, the driver cannot activate the NIC. If this is the problem, then the dmesg | less listing will usually contain one or more messages indicating that the system cannot load a specific firmware file. Once you know the name of the firmware file, you can search for it. Make sure the linux-firmware-<YYYYMMDD>-<version number> RPM package is installed: it includes a large collection of firmware files for various hardware.






                      share|improve this answer


























                        0














                        If you run ifconfig -a or ip link show as root, does the eth0 interface appear in the output? Does it have the MAC address that ís specified in the /etc/sysconfig/network-scripts/ifcfg-eth0 file on the HWADDR= line?



                        If it is not there at all, then the driver for the NIC has probably not been loaded yet, or has a problem that prevents it from loading.
                        If it has an unexpected name, you may have a problem with NIC naming.



                        If the NIC is there with the expected name, but refuses to activate, it might be a firmware loading problem: some NICs require firmware to work, and if the necessary firmware file is not available, the driver cannot activate the NIC. If this is the problem, then the dmesg | less listing will usually contain one or more messages indicating that the system cannot load a specific firmware file. Once you know the name of the firmware file, you can search for it. Make sure the linux-firmware-<YYYYMMDD>-<version number> RPM package is installed: it includes a large collection of firmware files for various hardware.






                        share|improve this answer
























                          0












                          0








                          0






                          If you run ifconfig -a or ip link show as root, does the eth0 interface appear in the output? Does it have the MAC address that ís specified in the /etc/sysconfig/network-scripts/ifcfg-eth0 file on the HWADDR= line?



                          If it is not there at all, then the driver for the NIC has probably not been loaded yet, or has a problem that prevents it from loading.
                          If it has an unexpected name, you may have a problem with NIC naming.



                          If the NIC is there with the expected name, but refuses to activate, it might be a firmware loading problem: some NICs require firmware to work, and if the necessary firmware file is not available, the driver cannot activate the NIC. If this is the problem, then the dmesg | less listing will usually contain one or more messages indicating that the system cannot load a specific firmware file. Once you know the name of the firmware file, you can search for it. Make sure the linux-firmware-<YYYYMMDD>-<version number> RPM package is installed: it includes a large collection of firmware files for various hardware.






                          share|improve this answer












                          If you run ifconfig -a or ip link show as root, does the eth0 interface appear in the output? Does it have the MAC address that ís specified in the /etc/sysconfig/network-scripts/ifcfg-eth0 file on the HWADDR= line?



                          If it is not there at all, then the driver for the NIC has probably not been loaded yet, or has a problem that prevents it from loading.
                          If it has an unexpected name, you may have a problem with NIC naming.



                          If the NIC is there with the expected name, but refuses to activate, it might be a firmware loading problem: some NICs require firmware to work, and if the necessary firmware file is not available, the driver cannot activate the NIC. If this is the problem, then the dmesg | less listing will usually contain one or more messages indicating that the system cannot load a specific firmware file. Once you know the name of the firmware file, you can search for it. Make sure the linux-firmware-<YYYYMMDD>-<version number> RPM package is installed: it includes a large collection of firmware files for various hardware.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered May 31 '18 at 11:16









                          telcoMtelcoM

                          16k12143




                          16k12143






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Unix & Linux Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f402891%2ferror-connection-activation-failed-device-not-managed-by-networkmanager-or-una%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              CARDNET

                              Boot-repair Failure: Unable to locate package grub-common:i386

                              濃尾地震