Error with static ip on rock64

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

    • Error with static ip on rock64

      Here I am, I just got my Rock64 board and installed a fresh OMV 4 (ayufan).

      The first thing was to edit the IP address and set a static one. I did it via WebGUI but it stucks in "Apply loop", the same as all the users above (this issue also broke all other configuration menu, every time you apply a new setting or enable a service OMV give back the attached error).

      The curious thing was that the static IP addess was set in /etc/network/interfaces with no effect. To "solve" 'Apply loop' I must revert it to DHCP.

      Now the webgui is reachable both through the static IP and the DHCP IP.

      Source Code

      1. # Include additional interface stanzas.
      2. source-directory interfaces.d
      3. # The loopback network interface
      4. auto lo
      5. iface lo inet loopback
      6. # eth0 network interface
      7. auto eth0
      8. allow-hotplug eth0
      9. iface eth0 inet static
      10. address 192.168.178.27
      11. gateway 192.168.178.1
      12. netmask 255.255.255.0
      13. dns-nameservers 192.168.178.1
      14. iface eth0 inet6 manual
      15. pre-down ip -6 addr flush dev $IFACE
      Display All


      I also tried "omv-firstaid" to edit the network interface but got a nice error right after I choose option 1:

      Source Code

      1. ERROR: dialog-like terminated due to an error: the dialog-like program exited with status 3 (which was passed to it as the DIALOG_ERROR environment variable). Sometimes, the reason is simply that dialog was given a height or width parameter that is too big for the terminal in use. Its output, with leading and trailing whitespace stripped, was:
      2. Error: Expected at least 5 tokens for --menu, have 4.
      3. Use --help to list options.


      I tried to change the micro SD with a new one, same result.
      Images
      • err.png

        35.43 kB, 352×175, viewed 161 times
    • zdelarosa00 wrote:

      I also have this issue!, I'm thinking of moving to OMV 3.x now since I read your reply... I read your post and you clearly know a ton more, if you haven't figured out then I'm almost lost... I didn't want to start a thread in fear of mods saying this issue has been addressed but configuring network is a pain so far with my diy nas... I followed every step and troubleshooted everything, I even started configuring the admin page throught ethernet and yet this NAS distro does not get the simplest config done.

      I attach few screenshots of my issue codes.
      The problem is that something went wrong on your system during installation or upgrade. There is a fake start-stop-daemon error warning. Search the forum or Google how to fix that Debian issue.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Ciccius wrote:

      I also tried "omv-firstaid" to edit the network interface but got a nice error right after I choose option 1:
      Can not reproduce this issue :(
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Can not reproduce the static ip issue except that i have to manually set the interface down to make 'systemctl restart networking' happy. But this seems to be a Debian problem that can't be solved by OMV. OMV5 is now using systemd for network configuration, so this issue should be fixed in future.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Ciccius wrote:

      votdev wrote:

      Ciccius wrote:

      I also tried "omv-firstaid" to edit the network interface but got a nice error right after I choose option 1:
      Can not reproduce this issue :(
      How can I help you to debug this issue? Need some log files? If so, what files?

      Thanks!
      First question, are you up-to-date with the updates? I really can't reproduce this, either i'm setting up a static and DHCP interface. Are you using any backport packages? Maybe dialog has been changed in a newer version? Note, OMV does not support backports because of this reason.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • votdev wrote:

      First question, are you up-to-date with the updates? I really can't reproduce this, either i'm setting up a static and DHCP interface. Are you using any backport packages? Maybe dialog has been changed in a newer version? Note, OMV does not support backports because of this reason.

      I just downloaded latest image from ayufan space (github.com/ayufan-rock64/linux-build/releases) : stretch-openmediavault-rock64-0.7.9-1067-armhf.img.xz

      Just a quick recap: right after the first boot, I tried to change IP and didn't works. Than I reverted to DHCP and begun to change other settings: at this point i saw many updates in "update menu" from WebGUI. Once update were done I tried to run 'omv-firstaid' again but no luck!

      I didn't install any other plugin, I didn't attach any drive yet to the board! XD
    • I can't reproduce this in the Vagrant box used for testing and delevoping (based on AMD64), so i am sure the problems coming from the image. I don't know how this image is build and which customizations are done to the Debian system, so i am out at this point because everything seems to work on an official Debian system build via Vagrant.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Ciccius wrote:

      Thank you votdev, I'll try another image, maybe 64 bits version or the official OMV image for Rock64.
      Are you really trying to setup bonded network adapters on the rock64?
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Ciccius wrote:

      No, just the physical interface eth0.
      Ok. I moved this to its own thread since that other thread was caused by a bonding issue. I highly doubt the issue with your rock64 is the image. I have a rockpro64 from ayufan (same build script) with a static ip and it works fine. What settings are you using? screenshots are good.
      omv 4.1.22 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.15
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Sorry for the late answer, I was a little busy.

      I restarted from eth0 in DHCP mode and tried to set it to static IP.


      1. I set static IP (not in the image, I set also DNS to the same IP of gateway)
















      2. When OMV ask to apply the new setting, after few seconds this error popup



      3. I ran the 2 commands suggested in the popup:

      systemctl status networking.service




      journalctl -xe

      Source Code

      1. Oct 03 23:52:18 rock64 systemd[1]: Starting Raise network interfaces...
      2. -- Subject: Unit networking.service has begun start-up
      3. -- Defined-By: systemd
      4. -- Support: https://www.debian.org/support
      5. --
      6. -- Unit networking.service has begun starting up.
      7. Oct 03 23:52:18 rock64 dhclient[6299]: Internet Systems Consortium DHCP Client 4.3.5
      8. Oct 03 23:52:18 rock64 ifup[6258]: Internet Systems Consortium DHCP Client 4.3.5
      9. Oct 03 23:52:18 rock64 ifup[6258]: Copyright 2004-2016 Internet Systems Consortium.
      10. Oct 03 23:52:18 rock64 ifup[6258]: All rights reserved.
      11. Oct 03 23:52:18 rock64 ifup[6258]: For info, please visit https://www.isc.org/software/dhcp/
      12. Oct 03 23:52:18 rock64 dhclient[6299]: Copyright 2004-2016 Internet Systems Consortium.
      13. Oct 03 23:52:18 rock64 dhclient[6299]: All rights reserved.
      14. Oct 03 23:52:18 rock64 dhclient[6299]: For info, please visit https://www.isc.org/software/dhcp/
      15. Oct 03 23:52:18 rock64 dhclient[6299]:
      16. Oct 03 23:52:18 rock64 dhclient[6299]: Listening on LPF/eth0/2e:c5:9e:99:39:81
      17. Oct 03 23:52:18 rock64 ifup[6258]: Listening on LPF/eth0/2e:c5:9e:99:39:81
      18. Oct 03 23:52:18 rock64 ifup[6258]: Sending on LPF/eth0/2e:c5:9e:99:39:81
      19. Oct 03 23:52:18 rock64 ifup[6258]: Sending on Socket/fallback
      20. Oct 03 23:52:18 rock64 ifup[6258]: DHCPREQUEST of 192.168.178.59 on eth0 to 255.255.255.255 port 67
      21. Oct 03 23:52:18 rock64 dhclient[6299]: Sending on LPF/eth0/2e:c5:9e:99:39:81
      22. Oct 03 23:52:18 rock64 ifup[6258]: DHCPACK of 192.168.178.59 from 192.168.178.1
      23. Oct 03 23:52:18 rock64 dhclient[6299]: Sending on Socket/fallback
      24. Oct 03 23:52:18 rock64 dhclient[6299]: DHCPREQUEST of 192.168.178.59 on eth0 to 255.255.255.255 port 67
      25. Oct 03 23:52:18 rock64 dhclient[6299]: DHCPACK of 192.168.178.59 from 192.168.178.1
      26. Oct 03 23:52:18 rock64 NetworkManager[1012]: <info> [1538603538.3367] manager: NetworkManager state is now CONNECTED_GLOBAL
      27. Oct 03 23:52:18 rock64 dbus[993]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop
      28. .nm-dispatcher.service'
      29. Oct 03 23:52:18 rock64 systemd[1]: Starting Network Manager Script Dispatcher Service...
      30. -- Subject: Unit NetworkManager-dispatcher.service has begun start-up
      31. -- Defined-By: systemd
      32. -- Support: https://www.debian.org/support
      33. --
      34. -- Unit NetworkManager-dispatcher.service has begun starting up.
      35. Oct 03 23:52:18 rock64 dbus[993]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
      36. Oct 03 23:52:18 rock64 nm-dispatcher[6311]: req:1 'connectivity-change': new request (2 scripts)
      37. Oct 03 23:52:18 rock64 nm-dispatcher[6311]: req:1 'connectivity-change': start running ordered scripts...
      38. Oct 03 23:52:18 rock64 systemd[1]: Started Network Manager Script Dispatcher Service.
      39. -- Subject: Unit NetworkManager-dispatcher.service has finished start-up
      40. -- Defined-By: systemd
      41. -- Support: https://www.debian.org/support
      42. --
      43. -- Unit NetworkManager-dispatcher.service has finished starting up.
      44. --
      45. -- The start-up result is done.
      46. Oct 03 23:52:18 rock64 systemd[1]: Reloading Samba SMB Daemon.
      47. -- Subject: Unit smbd.service has begun reloading its configuration
      48. -- Defined-By: systemd
      49. -- Support: https://www.debian.org/support
      50. --
      51. -- Unit smbd.service has begun reloading its configuration
      52. Oct 03 23:52:18 rock64 systemd[1]: Reloaded Samba SMB Daemon.
      53. -- Subject: Unit smbd.service has finished reloading its configuration
      54. -- Defined-By: systemd
      55. -- Support: https://www.debian.org/support
      56. --
      57. -- Unit smbd.service has finished reloading its configuration
      58. --
      59. -- The result is done.
      60. Oct 03 23:52:18 rock64 ifup[6258]: RTNETLINK answers: File exists
      61. Oct 03 23:52:18 rock64 systemd[1]: Stopping LSB: Start NTP daemon...
      62. -- Subject: Unit ntp.service has begun shutting down
      63. -- Defined-By: systemd
      64. -- Support: https://www.debian.org/support
      65. --
      66. -- Unit ntp.service has begun shutting down.
      67. Oct 03 23:52:18 rock64 ntpd[5610]: ntpd exiting on signal 15 (Terminated)
      68. Oct 03 23:52:18 rock64 ntpd[5610]: 192.168.178.1 local addr 192.168.178.59 -> <null>
      69. Oct 03 23:52:18 rock64 ntp[6347]: Stopping NTP server: ntpd.
      70. Oct 03 23:52:18 rock64 systemd[1]: Stopped LSB: Start NTP daemon.
      71. -- Subject: Unit ntp.service has finished shutting down
      72. -- Defined-By: systemd
      73. -- Support: https://www.debian.org/support
      74. --
      75. -- Unit ntp.service has finished shutting down.
      76. Oct 03 23:52:18 rock64 systemd[1]: Starting LSB: Start NTP daemon...
      77. -- Subject: Unit ntp.service has begun start-up
      78. -- Defined-By: systemd
      79. -- Support: https://www.debian.org/support
      80. --
      81. -- Unit ntp.service has begun starting up.
      82. Oct 03 23:52:18 rock64 ntpd[6368]: ntpd 4.2.8p10@1.3728-o Sun Feb 25 22:00:44 UTC 2018 (1): Starting
      83. Oct 03 23:52:18 rock64 ntpd[6368]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /run/ntp.conf.dhcp -u 105:109
      84. Oct 03 23:52:18 rock64 ntp[6358]: Starting NTP server: ntpd.
      85. Oct 03 23:52:18 rock64 systemd[1]: Started LSB: Start NTP daemon.
      86. -- Subject: Unit ntp.service has finished start-up
      87. -- Defined-By: systemd
      88. -- Support: https://www.debian.org/support
      89. --
      90. -- Unit ntp.service has finished starting up.
      91. --
      92. -- The start-up result is done.
      93. Oct 03 23:52:18 rock64 ntpd[6371]: proto: precision = 0.875 usec (-20)
      94. Oct 03 23:52:18 rock64 ntpd[6371]: restrict 0.0.0.0: KOD does nothing without LIMITED.
      95. Oct 03 23:52:18 rock64 ntpd[6371]: restrict ::: KOD does nothing without LIMITED.
      96. Oct 03 23:52:18 rock64 ntpd[6371]: Listen and drop on 0 v6wildcard [::]:123
      97. Oct 03 23:52:18 rock64 ntpd[6371]: Listen and drop on 1 v4wildcard 0.0.0.0:123
      98. Oct 03 23:52:18 rock64 ntpd[6371]: Listen normally on 2 lo 127.0.0.1:123
      99. Oct 03 23:52:18 rock64 ntpd[6371]: Listen normally on 3 eth0 192.168.178.59:123
      100. Oct 03 23:52:18 rock64 ntpd[6371]: Listen normally on 4 eth0 192.168.178.27:123
      101. Oct 03 23:52:18 rock64 ntpd[6371]: Listen normally on 5 lo [::1]:123
      102. Oct 03 23:52:18 rock64 ntpd[6371]: Listening on routing socket on fd #22 for interface updates
      103. Oct 03 23:52:18 rock64 ifup[6258]: Warning: systemd-timesyncd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
      104. Oct 03 23:52:18 rock64 dhclient[6299]: bound to 192.168.178.59 -- renewal in 422242 seconds.
      105. Oct 03 23:52:18 rock64 ifup[6258]: bound to 192.168.178.59 -- renewal in 422242 seconds.
      106. Oct 03 23:52:18 rock64 systemd[1]: Reloading OpenBSD Secure Shell server.
      107. -- Subject: Unit ssh.service has begun reloading its configuration
      108. -- Defined-By: systemd
      109. -- Support: https://www.debian.org/support
      110. --
      111. -- Unit ssh.service has begun reloading its configuration
      112. Oct 03 23:52:18 rock64 systemd[1]: Reloaded OpenBSD Secure Shell server.
      113. -- Subject: Unit ssh.service has finished reloading its configuration
      114. -- Defined-By: systemd
      115. -- Support: https://www.debian.org/support
      116. --
      117. -- Unit ssh.service has finished reloading its configuration
      118. --
      119. -- The result is done.
      120. Oct 03 23:52:18 rock64 sshd[1530]: Received SIGHUP; restarting.
      121. Oct 03 23:52:18 rock64 sshd[1530]: Server listening on 0.0.0.0 port 22.
      122. Oct 03 23:52:18 rock64 sshd[1530]: Server listening on :: port 22.
      123. Oct 03 23:52:19 rock64 ifup[6258]: RTNETLINK answers: File exists
      124. Oct 03 23:52:19 rock64 ifup[6258]: ifup: failed to bring up eth0
      125. Oct 03 23:52:19 rock64 NetworkManager[1012]: <info> [1538603539.1338] manager: NetworkManager state is now DISCONNECTED
      126. Oct 03 23:52:19 rock64 nm-dispatcher[6311]: req:2 'connectivity-change': new request (2 scripts)
      127. Oct 03 23:52:19 rock64 nm-dispatcher[6311]: req:2 'connectivity-change': start running ordered scripts...
      128. Oct 03 23:52:19 rock64 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
      129. Oct 03 23:52:19 rock64 systemd[1]: Failed to start Raise network interfaces.
      130. -- Subject: Unit networking.service has failed
      131. -- Defined-By: systemd
      132. -- Support: https://www.debian.org/support
      133. --
      134. -- Unit networking.service has failed.
      135. --
      136. -- The result is failed.
      137. Oct 03 23:52:19 rock64 systemd[1]: networking.service: Unit entered failed state.
      138. Oct 03 23:52:19 rock64 systemd[1]: networking.service: Failed with result 'exit-code'.
      Display All
      Have a look at lines 99 and 100:


      99. Oct 03 23:52:18 rock64 ntpd[6371]: Listen normally on 3 eth0 192.168.178.59:123
      100. Oct 03 23:52:18 rock64 ntpd[6371]: Listen normally on 4 eth0 192.168.178.27:123

      The first (192.168.178.59) is the IP that eth0 got in DHCP mode while the latter is the static one. Trying to open the web GUI, OMV reply from both!


      4. Last step, I restore the default. OVM reset eth0 to DHCP and /etc/network/interfaces is set as the following:


      Source Code

      1. # Include additional interface stanzas.
      2. source-directory interfaces.d
      3. # The loopback network interface
      4. auto lo
      5. iface lo inet loopback
      6. # eth0 network interface
      7. auto eth0
      8. allow-hotplug eth0
      9. iface eth0 inet static
      10. address 192.168.178.27
      11. gateway 192.168.178.1
      12. netmask 255.255.255.0
      13. dns-nameservers 192.168.178.1
      14. iface eth0 inet6 manual
      15. pre-down ip -6 addr flush dev $IFACE
      Display All


      ... and in /etc/network/interfaces.d/eth0 :


      Source Code

      1. allow-hotplug eth0
      2. iface eth0 inet dhcp


      I googled around about "RTNETLINK answers: File exists" error (line 123 in journalctl log) and tried several "solution", from reboot to 'ip addr flush dev eth0', but no way.


      Any ideas?


      Thanks!
    • Ciccius wrote:

      from reboot to 'ip addr flush dev eth0', but no way.
      Someone had the issue a few days ago an ip addr flush dev eth0 worked for them, if that didn't work I suggested running omv-firstaid from the command line and I think it's option 1: Configure Network Interface
      It may well error, it did when I changed my hardware, but I just rebooted with shutdown -r now and it worked fine.
      Raid is not a backup! Would you go skydiving without a parachute?

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

    • geaves wrote:

      if that didn't work I suggested running omv-firstaid from the command line and I think it's option 1: Configure Network Interface

      It was one of my first try but there is another issue in omv-firstaid panel:

      Source Code

      1. ERROR: dialog-like terminated due to an error: the dialog-like program exited with status 3 (which was passed to it as the DIALOG_ERROR environment variable). Sometimes, the reason is simply that dialog was given a height or width parameter that is too big for the terminal in use. Its output, with leading and trailing whitespace stripped, was:
      2. Error: Expected at least 5 tokens for --menu, have 4.
      3. Use --help to list options.

      Thanks.
    • Ciccius wrote:

      Thanks @geaves for the hint, I'll try it once at home (as a noob, I tried "ip addr flush dev eth0" from a ssh session and lost the connection to the device. Luckly I was in my living room and the device few meters from me :) )
      You really should do this directly on the device with a screen and keyboard :)

      If you can do that running omv-firstaid directly on the machine might just work.
      Raid is not a backup! Would you go skydiving without a parachute?

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

    • geaves wrote:

      If I had read the thread through I can see that the omv-firstaid can't be replicated :(
      However, doing some more searching try this ip addr flush dev eth0 followed by /etc/init.d/networking restart

      I wouldn't reboot yet, but try the gui if can be accessed.

      Ok, there is what I did:

      1. I reverted everything to default (net interface set to DHCP)
      2. Despite step 1. in /etc/network/interfaces there was still the configuration for static IP. That was ok for me.
      3. in /etc/network/interfaces.d/eth0 I commented the line iface eth0 inet dhcp
      4. I ran the command ip addr flush dev eth0 and then /etc/init.d/networking restart (this time directly from the device :P )
      5. I checked the web interface: 192.168.178.59 (DHCP IP address) was no longer available, 192.168.178.27 (static IP) was up and running. No reboot needed.

      Now in the web gui there was still DB value of net interface, I simply edited it to the new value. This time there was no error. :)


      On the other side, the first option of omv-firstaid gave the same error. :(


      Thank you!