network interface set up issues

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • network interface set up issues

      Hi

      I've had a bunch of issues (describe in this post) around setting up plex. @macom been helping but we're now so far away from the original issue I think it's a separate post.

      I'm now having problems with setting up my network interfaces (which was working fine before)

      I've tried omv-first aid which wipes all the setting against the network card I've first-aided

      When I go in and re-add them and apply configuration changes it hangs for ages then I get this error:

      Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; systemctl start 'networking' 2>&1' with exit code '1': Job for networking.service failed because the control process exited with error code.See "systemctl status networking.service" and "journalctl -xe" for details.


      The network card is working because I can access OMV via the web interface.

      systemctl status networking.service returns:

      Shell-Script

      1. ● networking.service - Raise network interfaces
      2. Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
      3. Active: failed (Result: exit-code) since Thu 2016-11-03 17:36:44 GMT; 6min ago
      4. Docs: man:interfaces(5)
      5. Process: 1863 ExecStop=/sbin/ifdown -a --read-environment --exclude=lo (code=killed, signal=TERM)
      6. Process: 2110 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
      7. Process: 2105 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udeva
      8. dm settle (code=exited, status=0/SUCCESS)
      9. Main PID: 2110 (code=exited, status=1/FAILURE)
      10. Nov 03 17:36:44 nas01 systemd[1]: Starting Raise network interfaces...
      11. Nov 03 17:36:44 nas01 ifup[2110]: RTNETLINK answers: File exists
      12. Nov 03 17:36:44 nas01 ifup[2110]: ifup: failed to bring up wlp1s9
      13. Nov 03 17:36:44 nas01 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
      14. Nov 03 17:36:44 nas01 systemd[1]: Failed to start Raise network interfaces.
      15. Nov 03 17:36:44 nas01 systemd[1]: networking.service: Unit entered failed state.
      16. Nov 03 17:36:44 nas01 systemd[1]: networking.service: Failed with result 'exit-code'.
      Display All

      journalctl -xe returns:

      Shell-Script

      1. Logs begin at Thu 2016-11-03 17:16:43 GMT, end at Thu 2016-11-03 17:45:24 GMT. --
      2. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      3. to rrdcached: No such file or directory (status=2)
      4. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      5. to rrdcached: No such file or directory (status=2)
      6. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      7. to rrdcached: No such file or directory (status=2)
      8. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      9. to rrdcached: No such file or directory (status=2)
      10. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      11. to rrdcached: No such file or directory (status=2)
      12. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      13. to rrdcached: No such file or directory (status=2)
      14. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      15. to rrdcached: No such file or directory (status=2)
      16. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      17. to rrdcached: No such file or directory (status=2)
      18. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      19. to rrdcached: No such file or directory (status=2)
      20. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      21. to rrdcached: No such file or directory (status=2)
      22. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      23. to rrdcached: No such file or directory (status=2)
      24. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      25. to rrdcached: No such file or directory (status=2)
      26. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      27. to rrdcached: No such file or directory (status=2)
      28. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      29. to rrdcached: No such file or directory (status=2)
      30. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      31. to rrdcached: No such file or directory (status=2)
      32. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      33. to rrdcached: No such file or directory (status=2)
      34. Nov 03 17:40:34 nas01 collectd[1514]: rrdcached plugin: Failed to connect to RRDCacheD at unix:/var/run/rrdcached.sock: Unable to connect
      35. to rrdcached: No such file or directory (status=2)
      Display All
      note the date/time on the above which I also cannot update/ apply without getting the above error in bold


      Any thoughts. I'm a total noob so sorry if this is obvious.

      dd
    • first of all.. changing network configs while login via ssh, http or rdp most times go wrong! You pull the carpet while you stand on.
      if you use a headless PI, this makes it complex, on a Nas with desktop access its easy to change network things.
      on a Nas with Desktop call 127.0.0.1 to do configs in omv.
      But you can change ipv6 while using ipv4 and vice versa. but this is complex too.
      the easyest way is not touching default dhcp behavior after installation and do not enter/change anything about networks in omv.
      the most systems are in well working dhcp mode after installation. There is no need to play on this configs.
      don't touch netconfigs via net.
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.

      The post was edited 1 time, last by Rd65 ().

    • as i told... do the steps and it will work.
      maybe you mixup dhcp wiht dns?
      you get your adress by dhcp from the router and if your router is your dns forwarder, he knows a hostname combined wit this adress (and mac). then it dosn't matter if you get static ip (as a static lease) or a well known hostname managed by your router.
      no reason for static adresses, no reason to play on nameserver entrys. the router do it for you.
      no there is no need to reinstall.. use a backup ;)
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.
    • please do a

      $ sudo dhclient -v

      and tell me:

      $ cat /var/lib/dhcp/dhclient.leases

      these are the infos from your router about your client. if you dont want post this, doubleselfcheck the values.
      Equipment: a few Computers, lot's of waste heat, little time and a Pile of work.

      When solving problems, dig at the root instead of hacking at the leaves.