Network Error after change to Static

    • OMV 4.x
    • Network Error after change to Static

      Hi Guys,
      after changing a fresh installed OMV image the network address to a static one i get thoose 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.
      Fehler #0: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; 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. in /usr/share/php/openmediavault/system/process.inc:182Stack trace:#0 /usr/share/php/openmediavault/system/systemctl.inc(86): OMV\System\Process->execute(Array, 1)#1 /usr/share/php/openmediavault/system/systemctl.inc(146): OMV\System\SystemCtl->exec('start', NULL, false)#2 /usr/share/openmediavault/engined/module/networking.inc(44): OMV\System\SystemCtl->start()#3 /usr/share/openmediavault/engined/rpc/config.inc(194): OMVModuleNetworking->startService()#4 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)#7 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuszp...', '/tmp/bgoutputOB...')#8 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))#9 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)#10 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)#11 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)#12 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)#13 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)#14 {main}



      is someone able to help?

      dhcp is working fine




      thanks,
      Eike

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

    • you can try it, directy in /etc/network/interfaces with nano for example something like that
      # The primary network interfaceauto eth0iface eth0 inet staticaddress 192.168.0.2netmask 255.255.255.0network 192.168.0.0broadcast 192.168.0.255gateway 192.168.0.1dns-nameservers 192.168.0.3
      OMV 3.0.99 (ERASMUS). Never change a running system. If you do it anyway, better you have a backup. :D
    • Pattex wrote:

      you can try it, directy in /etc/network/interfaces with nano for example something like that
      # The primary network interfaceauto eth0iface eth0 inet staticaddress 192.168.0.2netmask 255.255.255.0network 192.168.0.0broadcast 192.168.0.255gateway 192.168.0.1dns-nameservers 192.168.0.3
      I have tried this... OMV will time out using the webui and first aid. It looks like it still rights to /etc....interface but can't confirm the change.
    • Eike wrote:

      Job for networking.service failed because the control process exited with error code. See "systemctl status networking.service" and "journalctl -xe" for details.
      This message tells you to look into the output of these two commands:

      Source Code

      1. systemctl status networking.service
      2. journalctl -xe

      Those contain information needed to diagnose the problem which is none I would assume since:

      Eike wrote:

      dhcp is working fine
      So better stay with DHCP, check whether your router allows to set a static DHCP lease for your machine and assign an easy name like omv4 for example. Then you can access your OMV install by name and not by number.
    • tkaiser wrote:

      Source Code

      1. systemctl status networking.service
      2. journalctl -xe

      1:
      root@HP-Proliant:~# systemctl status networking.service
      ● networking.service - Raise network interfaces
      Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor prese
      t: enabled)
      Active: active (exited) since Sun 2019-03-17 20:17:24 CET; 3 days
      ago
      Docs: man:interfaces(5)
      Main PID: 723 (code=exited, status=0/SUCCESS)
      Tasks: 0 (limit: 9830)
      CGroup: /system.slice/networking.service
      Mär 17 20:17:22 HP-Proliant systemd[1]: Starting Raise network interfaces...
      Mär 17 20:17:24 HP-Proliant systemd[1]: Started Raise network interfaces.
      2:
      -- The start-up result is done.
      Mär 21 00:15:01 HP-Proliant CRON[61302]: pam_unix(cron:session): session opened for user root by (ui
      d=0)
      Mär 21 00:15:01 HP-Proliant CRON[61303]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)
      Mär 21 00:15:05 HP-Proliant CRON[61302]: pam_unix(cron:session): session closed for user root
      Mär 21 00:17:01 HP-Proliant CRON[61592]: pam_unix(cron:session): session opened for user root by (ui
      d=0)
      Mär 21 00:17:01 HP-Proliant CRON[61593]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
      Mär 21 00:17:01 HP-Proliant CRON[61592]: pam_unix(cron:session): session closed for user root
      Mär 21 00:17:27 HP-Proliant rrdcached[1138]: flushing old values
      Mär 21 00:17:27 HP-Proliant rrdcached[1138]: rotating journals
      Mär 21 00:17:27 HP-Proliant rrdcached[1138]: started new journal /var/lib/rrdcached/journal/rrd.jour
      nal.1553123847.135988
      Mär 21 00:17:27 HP-Proliant rrdcached[1138]: removing old journal /var/lib/rrdcached/journal/rrd.jou
      rnal.1553116647.135965
      Mär 21 00:24:24 HP-Proliant smartd[21984]: Device: /dev/disk/by-id/ata-WDC_WD40EFRX-68WT0N0_
      WD-WCC4E6NYDDE8 [SAT], 2 Currently unreadable (pending) sectors
      Mär 21 00:30:01 HP-Proliant CRON[61812]: pam_unix(cron:session): session opened for user root by (ui
      d=0)
      Mär 21 00:30:01 HP-Proliant CRON[61813]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)
      Mär 21 00:30:04 HP-Proliant CRON[61812]: pam_unix(cron:session): session closed for user root
      Mär 21 00:39:01 HP-Proliant CRON[62215]: pam_unix(cron:session): session opened for user root by (ui
      d=0)
      Mär 21 00:39:01 HP-Proliant CRON[62216]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d
      /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
      Mär 21 00:39:01 HP-Proliant CRON[62215]: pam_unix(cron:session): session closed for user root
      Mär 21 00:39:04 HP-Proliant systemd[1]: Starting Clean php session files...
      -- Subject: Unit phpsessionclean.service has begun start-up
      -- Defined-By: systemd
      -- Support: debian.org/support
      --
      -- Unit phpsessionclean.service has begun starting up.
      Mär 21 00:39:04 HP-Proliant systemd[1]: Started Clean php session files.
      -- Subject: Unit phpsessionclean.service has finished start-up
      -- Defined-By: systemd
      -- Support: debian.org/support
      --
      -- Unit phpsessionclean.service has finished starting up.
      --
      -- The start-up result is done.
      I know there is a HDD broken

      [/quote]