Can't save network settings?

    • OMV 4.x

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

    • Can't save network settings?

      I updated the firmware on my Aquantia card today and after that, I can't configure the card in OMV.
      OMV-firstaid doesn't work either and I get the same error message there.
      Everything seems to be working fine still, so not sure what's going on.
      The card is not in the list of network interfaces in the OMV UI though.
      Any suggestions as to what have gone wrong and how to possibly solve it?

      Source Code

      1. Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; monit monitor collectd 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection refused
      2. Error #0:
      3. OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; monit monitor collectd 2>&1' with exit code '1': Cannot create socket to [localhost]:2812 -- Connection refused in /usr/share/php/openmediavault/system/process.inc:182
      4. Stack trace:
      5. #0 /usr/share/php/openmediavault/system/monit.inc(115): OMV\System\Process->execute()
      6. #1 /usr/share/php/openmediavault/system/monit.inc(82): OMV\System\Monit->action('monitor', false)
      7. #2 /usr/share/openmediavault/engined/module/collectd.inc(81): OMV\System\Monit->monitor()
      8. #3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleCollectd->startService()
      9. #4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      10. #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      11. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      12. #7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatus1H...', '/tmp/bgoutputhm...')
      13. #8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      14. #9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
      15. #10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      16. #11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      17. #12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
      18. #13 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
      19. #14 {main}
      Display All
      OMV 4.x, Gigabyte Z270N-WiFi, i7-6700K@3GHz, 16GB DDR4-3000, 4x 4TB Toshiba N300, 1x 60GB Corsair GT SSD (OS drive), 10Gbps Aquantia Ethernet
    • TheLostSwede wrote:

      Any suggestions as to what have gone wrong and how to possibly solve it?
      Did it change the device name? What is the output of: ip a
      omv 5.1.0 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.5
      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!
    • Nothing change, the UI kind of hangs and tells me I need to save the settings, but it can't be saved, so I have to revert the settings.
      OMV-firstaid comes out with the same "Failed to execute command" error.
      enp1s0 is the Aquantia card.

      Source Code

      1. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
      2. link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      3. inet 127.0.0.1/8 scope host lo
      4. valid_lft forever preferred_lft forever
      5. inet6 ::1/128 scope host
      6. valid_lft forever preferred_lft forever
      7. 2: enp7s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
      8. link/ether 1c:1b:0d:99:bf:cb brd ff:ff:ff:ff:ff:ff
      9. 3: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
      10. link/ether 1c:1b:0d:99:bf:cd brd ff:ff:ff:ff:ff:ff
      11. 4: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
      12. link/ether 00:17:b6:00:18:29 brd ff:ff:ff:ff:ff:ff
      13. inet 192.168.1.250/24 brd 192.168.1.255 scope global enp1s0
      14. valid_lft forever preferred_lft forever
      15. 5: wlp8s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
      16. link/ether 00:28:f8:3b:d7:a6 brd ff:ff:ff:ff:ff:ff
      17. 6: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
      18. link/ether 02:42:6f:85:e2:65 brd ff:ff:ff:ff:ff:ff
      19. inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
      20. valid_lft forever preferred_lft forever
      Display All
      OMV 4.x, Gigabyte Z270N-WiFi, i7-6700K@3GHz, 16GB DDR4-3000, 4x 4TB Toshiba N300, 1x 60GB Corsair GT SSD (OS drive), 10Gbps Aquantia Ethernet
    • I don't see anything strange. Seems to be having a problem reconfiguring collectd. I have monitoring disabled on all of my systems. So, I can't help much.
      omv 5.1.0 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.5
      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!
    • Well, I'm at a total loss, but I can't change any settings, which is annoying, as I wanted to change the MTU size, but as it's not possible to save any changes, or even add the specific interface in the UI...
      OMV 4.x, Gigabyte Z270N-WiFi, i7-6700K@3GHz, 16GB DDR4-3000, 4x 4TB Toshiba N300, 1x 60GB Corsair GT SSD (OS drive), 10Gbps Aquantia Ethernet
    • TheLostSwede wrote:

      Well, I'm at a total loss, but I can't change any settings, which is annoying, as I wanted to change the MTU size, but as it's not possible to save any changes, or even add the specific interface in the UI...
      File an issue on github. Until then, you can manually edit /etc/network/interfaces
      omv 5.1.0 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.5
      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!
    • ryecoaaron wrote:

      TheLostSwede wrote:

      Well, I'm at a total loss, but I can't change any settings, which is annoying, as I wanted to change the MTU size, but as it's not possible to save any changes, or even add the specific interface in the UI...
      File an issue on github. Until then, you can manually edit /etc/network/interfaces
      You know, these are things "normal" people simply don't do.
      I'm not a software developer. I just expect this stuff to work...
      OMV 4.x, Gigabyte Z270N-WiFi, i7-6700K@3GHz, 16GB DDR4-3000, 4x 4TB Toshiba N300, 1x 60GB Corsair GT SSD (OS drive), 10Gbps Aquantia Ethernet
    • TheLostSwede wrote:

      You know, these are things "normal" people simply don't do.
      Filing an issue on github or editing the interfaces file or both? Filing an issue is definitely something "normal" users have done. "normal" people don't upgrade firmware on network adapaters or change MTUs. You have always seemed like a bit more of an advanced user. So, I thought editing the normal Debian interfaces file was a reasonable request to get your system working.

      TheLostSwede wrote:

      I'm not a software developer.
      Why would you have to be a software developer to file a bug report? I'm not the OMV developer and I think you might have hit a bug. So, filing a bug report is the best thing to do. Since it is your system and could potentially help with the fix, you are the best one to do it. If you want to send me an Aquantia 10GBe card, I will do it.

      TheLostSwede wrote:

      I just expect this stuff to work...
      Wasn't it working before you upgraded the firmware? Are you sure nothing went wrong with the firmware update? Are you sure the newer firmware isn't having a problem with the driver? I will make sure you get your purchase price returned to you...
      omv 5.1.0 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.5
      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!
    • Well, I just updated the driver, still can't add the card in the UI, nor make any changes through omv-firstaid...
      Same error message.

      The reason I upgraded the firmware is because Aquantia has had some issues with past firmwares and although things have worked, I've had issues with fairly high latency on these cards compared to normal Gigabit. Admittedly it doesn't really affect transfer between the NAS and my PC, but at the same time, I have a habit of keeping my firmwares up to date, regardless of the product. In many cases, it prevents security issues. Besides, I hadn't updated this card for the better part of two years, so I figured it was high time. And no, nothing went wrong during the firmware upgrade, as both cards are working and can communicate with each other.

      The card clearly still works, the issue is with the error message I get when trying to make any changes through OMV.

      So who am I supposed to contact if not OMV about the issue? Especially as having installed the latest drivers from Aquantia, solved nothing.
      I thought the point of this forum, was to report issues and not having to use some third party service.

      I really loath how hard it is to do, what should be simple things, like updating drivers, in Linux. Every time, I spend hours and hours doing simple tasks.
      Beyond this issue, everything else, is mostly working, well, except every time there's an update for Docker, something breaks...

      Sorry, I'm too attached to these cards, as I went through a whole heap of trouble getting them at the time.

      And I hope you understand that although I'm venting frustration here, it's not aimed at you, since you actually try really hard to help people on the forums. I just find the way a lot of things are done the Linux world very frustrating.
      OMV 4.x, Gigabyte Z270N-WiFi, i7-6700K@3GHz, 16GB DDR4-3000, 4x 4TB Toshiba N300, 1x 60GB Corsair GT SSD (OS drive), 10Gbps Aquantia Ethernet
    • TheLostSwede wrote:

      The card clearly still works, the issue is with the error message I get when trying to make any changes through OMV.
      Hence why I said it was an OMV bug best fixed by filing an issue - github.com/OpenMediaVault/openmediavault/issues

      TheLostSwede wrote:

      So who am I supposed to contact if not OMV about the issue? Especially as having installed the latest drivers from Aquantia, solved nothing.
      I thought the point of this forum, was to report issues and not having to use some third party service.
      Here is the misunderstanding... I said file an issue and you took it as some other party. The forum is meant to discuss issue and reporting an issue on github formalizes the bug report (link above) and gives it a better chance of being seen by Volker.

      TheLostSwede wrote:

      I really loath how hard it is to do, what should be simple things, like updating drivers, in Linux. Every time, I spend hours and hours doing simple tasks.
      Most people don't have to update drives because that happens with kernel updates. When using cards not well supported by Linux, you have this problem. Nothing OMV or really Linux can do if the manufacturer won't mainline the drivers. Windows is bad at this too.

      TheLostSwede wrote:

      Beyond this issue, everything else, is mostly working, well, except every time there's an update for Docker, something breaks...
      Odd. I don't have this issues with mine. Hell, I even have my Ubuntu docker host on auto-patch and reboot. My containers just come back up and work. Sounds like some of the containers you are using are the problem.

      TheLostSwede wrote:

      Sorry, I'm too attached to these cards, as I went through a whole heap of trouble getting them at the time.
      I have cheap, old 10GBe mellanox cards that work flawlessly in Linux...

      TheLostSwede wrote:

      And I hope you understand that although I'm venting frustration here, it's not aimed at you, since you actually try really hard to help people on the forums. I just find the way a lot of things are done the Linux world very frustrating.
      If you choose to use hardware that isn't well supported in Linux, OMV can't magically make them better. The fact you hit a bug in OMV is just a coincidence. I understand venting but when directed at the person helping you (yes, it seemed that way), it is like biting the hand that feeds you.

      And Linux seems frustrating to you because Windows has ruined your mindset. OMV tries to make things "easier" like windows but it can't do everything especially since you are talking about a one man project compared to Microsoft.
      omv 5.1.0 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.1.5
      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!