openmediavault-firewall.service fails after 4to5 upgrade

KlausR · Mar 23rd 2022

Hello,

upgrade script ran up to reboot advise, reboot succeeded, but...

- applying changes in webgui fails
- sudo systemctl list-units --failed shows 6 services failed

Code

root@evpOMV:/# sudo systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● ifup@eth0.service loaded failed failed ifup for eth0
● networking.service loaded failed failed Raise network interfaces
● openmediavault-firewall.service loaded failed failed openmediavault iptables f
● systemd-modules-load.service loaded failed failed Load Kernel Modules
● watchdog.service loaded failed failed watchdog daemon
● wd_keepalive.service loaded failed failed watchdog keepalive daemon

- and output of "systemctl status openmediavault-firewall.service" shows probs with iptables

Code

root@evpOMV:/# systemctl status openmediavault-firewall.service
● openmediavault-firewall.service - openmediavault iptables firewall service
   Loaded: loaded (/etc/systemd/system/openmediavault-firewall.service; enabled;
   Active: failed (Result: exit-code) since Wed 2022-03-23 09:17:20 CET; 1h 36mi
  Process: 853 ExecStart=/etc/iptables/openmediavault-firewall.sh start (code=ex
 Main PID: 853 (code=exited, status=1/FAILURE)

Mar 23 09:17:20 evpOMV systemd[1]: Starting openmediavault iptables firewall ser
Mar 23 09:17:20 evpOMV openmediavault-firewall.sh[853]: iptables: Operation not
Mar 23 09:17:20 evpOMV systemd[1]: openmediavault-firewall.service: Main process
Mar 23 09:17:20 evpOMV systemd[1]: openmediavault-firewall.service: Failed with
Mar 23 09:17:20 evpOMV systemd[1]: Failed to start openmediavault iptables firew
lines 1-11/11 (END)
● openmediavault-firewall.service - openmediavault iptables firewall service
   Loaded: loaded (/etc/systemd/system/openmediavault-firewall.service; enabled; vendor preset: en
   Active: failed (Result: exit-code) since Wed 2022-03-23 09:17:20 CET; 1h 36min ago
  Process: 853 ExecStart=/etc/iptables/openmediavault-firewall.sh start (code=exited, status=1/FAI
 Main PID: 853 (code=exited, status=1/FAILURE)

Mar 23 09:17:20 evpOMV systemd[1]: Starting openmediavault iptables firewall service...
Mar 23 09:17:20 evpOMV openmediavault-firewall.sh[853]: iptables: Operation not supported.
Mar 23 09:17:20 evpOMV systemd[1]: openmediavault-firewall.service: Main process exited, code=exit
Mar 23 09:17:20 evpOMV systemd[1]: openmediavault-firewall.service: Failed with result 'exit-code'
Mar 23 09:17:20 evpOMV systemd[1]: Failed to start openmediavault iptables firewall service.

Display More

How can i solve this issue?

Thanx for help in advance!

Zoki · Mar 23rd 2022

Probably you should first check, why network is not working or what kernel mudules are missing before checking openmediavaualt-firewall.

what is the status of the other failed unit and why?

KlausR · Mar 23rd 2022

Quote from Zoki

Probably you should first check, why network is not working or what kernel mudules are missing before checking openmediavaualt-firewall.

what is the status of the other failed unit and why?

Sure, but i don't know how. Still a beginner with Linux and OMV...

I didn't realized network not to be working. Apt-get-update & apt-get upgrade are ok...

Zoki · Mar 23rd 2022

systemctl status systemd-modules-load.service

...

KlausR · Mar 23rd 2022

Code

systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enable
Drop-In: /etc/systemd/system/systemd-modules-load.service.d
└─10-timeout.conf
Active: failed (Result: exit-code) since Wed 2022-03-23 09:17:01 CET; 3h 9min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 134 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 134 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

lines 1-11/11 (END)

Display More

Zoki · Mar 23rd 2022

OK, maybe I was to terse.

systemctl is the program to control system services.

systemctl start <service_name> will try to start the service

systemctl status <service_name> will give the status of the service (and somtimes adice where else to look)

systemctl stop <service_name> will stop a given service.

No try to start the failed services (from above) and post their status / error messages on by one.

KlausR · Mar 23rd 2022

Quote from Zoki

OK, maybe I was to terse.

systemctl is the program to control system services.
systemctl start <service_name> will try to start the service
systemctl status <service_name> will give the status of the service (and somtimes adice where else to look)
systemctl stop <service_name> will stop a given service.

No try to start the failed services (from above) and post their status / error messages on by one.

Display More

ok, i start with this one...

Code

root@evpOMV:/# systemctl start ifup@eth0.service
root@evpOMV:/# systemctl status ifup@eth0.service
● ifup@eth0.service - ifup for eth0
   Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-03-23 13:22:53 CET; 14s ago
  Process: 23406 ExecStart=/bin/sh -ec ifup --allow=hotplug eth0; ifquery --state eth0 (code=exite
 Main PID: 23406 (code=exited, status=1/FAILURE)

Mar 23 13:22:53 evpOMV systemd[1]: Started ifup for eth0.
Mar 23 13:22:53 evpOMV sh[23406]: iptables: Operation not supported.
Mar 23 13:22:53 evpOMV sh[23406]: run-parts: /etc/network/if-pre-up.d/openmediavault-iptables exit
Mar 23 13:22:53 evpOMV sh[23406]: ifup: failed to bring up eth0
Mar 23 13:22:53 evpOMV systemd[1]: ifup@eth0.service: Main process exited, code=exited, status=1/F
Mar 23 13:22:53 evpOMV systemd[1]: ifup@eth0.service: Failed with result 'exit-code'.

Display More

Code

root@evpOMV:/# systemctl start networking.service
Job for networking.service failed because the control process exited with error code.
See "systemctl status networking.service" and "journalctl -xe" for details.
root@evpOMV:/# systemctl status networking.service
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-03-23 13:26:24 CET; 33s ago
     Docs: man:interfaces(5)
  Process: 23540 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
 Main PID: 23540 (code=exited, status=1/FAILURE)

Mar 23 13:26:24 evpOMV systemd[1]: Starting Raise network interfaces...
Mar 23 13:26:24 evpOMV ifup[23540]: iptables: Operation not supported.
Mar 23 13:26:24 evpOMV ifup[23540]: run-parts: /etc/network/if-pre-up.d/openmediavault-iptables ex
Mar 23 13:26:24 evpOMV ifup[23540]: ifup: pre-up script failed
Mar 23 13:26:24 evpOMV systemd[1]: networking.service: Main process exited, code=exited, status=1/
Mar 23 13:26:24 evpOMV systemd[1]: networking.service: Failed with result 'exit-code'.
Mar 23 13:26:24 evpOMV systemd[1]: Failed to start Raise network interfaces.

Display More

Zoki · Mar 23rd 2022

Have ypu configured your network?

KlausR · Mar 23rd 2022

no3...

Code

root@evpOMV:/# systemctl start openmediavault-firewall.service
Job for openmediavault-firewall.service failed because the control process exited with error code.
See "systemctl status openmediavault-firewall.service" and "journalctl -xe" for details.
root@evpOMV:/# systemctl status openmediavault-firewall.service
● openmediavault-firewall.service - openmediavault iptables firewall service
   Loaded: loaded (/etc/systemd/system/openmediavault-firewall.service; enabled; vendor preset: en
   Active: failed (Result: exit-code) since Wed 2022-03-23 13:29:41 CET; 19s ago
  Process: 23650 ExecStart=/etc/iptables/openmediavault-firewall.sh start (code=exited, status=1/F
 Main PID: 23650 (code=exited, status=1/FAILURE)

Mar 23 13:29:41 evpOMV systemd[1]: Starting openmediavault iptables firewall service...
Mar 23 13:29:41 evpOMV openmediavault-firewall.sh[23650]: iptables: Operation not supported.
Mar 23 13:29:41 evpOMV systemd[1]: openmediavault-firewall.service: Main process exited, code=exit
Mar 23 13:29:41 evpOMV systemd[1]: openmediavault-firewall.service: Failed with result 'exit-code'
Mar 23 13:29:41 evpOMV systemd[1]: Failed to start openmediavault iptables firewall service.

Display More

KlausR · Mar 23rd 2022

no.4

Code

root@evpOMV:/# systemctl start systemd-modules-load.service
Job for systemd-modules-load.service failed because the control process exited with error code.
See "systemctl status systemd-modules-load.service" and "journalctl -xe" for details.
root@evpOMV:/# systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enable
  Drop-In: /etc/systemd/system/systemd-modules-load.service.d
           └─10-timeout.conf
   Active: failed (Result: exit-code) since Wed 2022-03-23 13:31:42 CET; 11s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 23912 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 23912 (code=exited, status=1/FAILURE)

Mar 23 13:31:42 evpOMV systemd[1]: Starting Load Kernel Modules...
Mar 23 13:31:42 evpOMV systemd-modules-load[23912]: Failed to find module 'mv_cesa'
Mar 23 13:31:42 evpOMV systemd[1]: systemd-modules-load.service: Main process exited, code=exited,
Mar 23 13:31:42 evpOMV systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Mar 23 13:31:42 evpOMV systemd[1]: Failed to start Load Kernel Modules.

Display More

KlausR · Mar 23rd 2022

no.5

Code

root@evpOMV:/# systemctl start watchdog.service
Job for watchdog.service failed because the control process exited with error code.
See "systemctl status watchdog.service" and "journalctl -xe" for details.
root@evpOMV:/# systemctl status watchdog.service
● watchdog.service - watchdog daemon
   Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-03-23 13:33:28 CET; 10s ago
  Process: 23970 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "
  Process: 23979 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false (code=exited, status=

Mar 23 13:33:28 evpOMV systemd[1]: Starting watchdog daemon...
Mar 23 13:33:28 evpOMV sh[23970]: modprobe: FATAL: Module softdog not found in directory /lib/modu
Mar 23 13:33:28 evpOMV systemd[1]: watchdog.service: Control process exited, code=exited, status=1
Mar 23 13:33:28 evpOMV systemd[1]: watchdog.service: Failed with result 'exit-code'.
Mar 23 13:33:28 evpOMV systemd[1]: Failed to start watchdog daemon.
Mar 23 13:33:28 evpOMV systemd[1]: watchdog.service: Triggering OnFailure= dependencies.

Display More

KlausR · Mar 23rd 2022

.. and the last one:

Code

root@evpOMV:/# systemctl start wd_keepalive.service
Job for wd_keepalive.service failed because the control process exited with error code.
See "systemctl status wd_keepalive.service" and "journalctl -xe" for details.
root@evpOMV:/# systemctl status wd_keepalive.service
● wd_keepalive.service - watchdog keepalive daemon
   Loaded: loaded (/lib/systemd/system/wd_keepalive.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-03-23 13:35:06 CET; 10s ago
  Process: 24063 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "
  Process: 24071 ExecStopPost=/bin/sh -c rm -f /run/sendsigs.omit.d/wd_keepalive.pid (code=exited,

Mar 23 13:35:06 evpOMV systemd[1]: Starting watchdog keepalive daemon...
Mar 23 13:35:06 evpOMV sh[24063]: modprobe: FATAL: Module softdog not found in directory /lib/modu
Mar 23 13:35:06 evpOMV systemd[1]: wd_keepalive.service: Control process exited, code=exited, stat
Mar 23 13:35:06 evpOMV systemd[1]: wd_keepalive.service: Failed with result 'exit-code'.
Mar 23 13:35:06 evpOMV systemd[1]: Failed to start watchdog keepalive daemon.
root@evpOMV:/# systemctl start wd_keepalive.service
Job for wd_keepalive.service failed because the control process exited with error code.
See "systemctl status wd_keepalive.service" and "journalctl -xe" for details.
root@evpOMV:/# systemctl status wd_keepalive.service
● wd_keepalive.service - watchdog keepalive daemon
   Loaded: loaded (/lib/systemd/system/wd_keepalive.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2022-03-23 13:35:06 CET; 10s ago
  Process: 24063 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "
  Process: 24071 ExecStopPost=/bin/sh -c rm -f /run/sendsigs.omit.d/wd_keepalive.pid (code=exited,

Mar 23 13:35:06 evpOMV systemd[1]: Starting watchdog keepalive daemon...
Mar 23 13:35:06 evpOMV sh[24063]: modprobe: FATAL: Module softdog not found in directory /lib/modu
Mar 23 13:35:06 evpOMV systemd[1]: wd_keepalive.service: Control process exited, code=exited, stat
Mar 23 13:35:06 evpOMV systemd[1]: wd_keepalive.service: Failed with result 'exit-code'.
Mar 23 13:35:06 evpOMV systemd[1]: Failed to start watchdog keepalive daemon.

Display More

KlausR · Mar 23rd 2022

Quote from Zoki

Have ypu configured your network?

Ipv4 ist DHCP, Ipv6 is deactivated. Else just dns-server...

Changed that now temporarily, triggered by your question, to 1.1.1.1... but change won't be accepted

Zoki · Mar 23rd 2022

Your kernel is missing modules:

- softdog

- mv_cesa

What OS are you running?

and an ip -a to list the network devices. looks like eth0 is not present. Debina changed naming conventions for network devices some time ago.

KlausR · Mar 23rd 2022

Quote from Zoki

- softdog
- mv_cesa

What OS are you running?

and an ip -a to list the network devices. looks like eth0 is not present. Debina changed naming conventions for network devices some time ago.

Display More

Hey, that's surprising. All i did was starting upgrade script from an worling omv4..

System greeting is:

Welcome to ARMBIAN 5.27 experimental Debian GNU/Linux 10 (buster) 4.9.35-v7+

Linux evpOMV 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l

Code

root@evpOMV:/# uname -a
Linux evpOMV 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux

root@evpOMV:/# cat /etc/debian_version
10.11

root@evpOMV:/# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

Display More

ip -a gives this output

Code

root@evpOMV:/# ip -a
Usage: ip [ OPTIONS ] OBJECT { COMMAND | help }
       ip [ -force ] -batch filename
where  OBJECT := { link | address | addrlabel | route | rule | neigh | ntable |
                   tunnel | tuntap | maddress | mroute | mrule | monitor | xfrm |
                   netns | l2tp | fou | macsec | tcp_metrics | token | netconf | ila |
                   vrf | sr }
       OPTIONS := { -V[ersion] | -s[tatistics] | -d[etails] | -r[esolve] |
                    -h[uman-readable] | -iec | -j[son] | -p[retty] |
                    -f[amily] { inet | inet6 | ipx | dnet | mpls | bridge | link } |
                    -4 | -6 | -I | -D | -M | -B | -0 |
                    -l[oops] { maximum-addr-flush-attempts } | -br[ief] |
                    -o[neline] | -t[imestamp] | -ts[hort] | -b[atch] [filename] |
                    -rc[vbuf] [size] | -n[etns] name | -a[ll] | -c[olor]}

Display More

Thanx a lot, Zoki

Zoki · Mar 23rd 2022

I meant ip a, no dash.

But you will have to find someone who knowa armbian, I don't.

KlausR · Mar 23rd 2022

ip a...

Code

root@evpOMV:/# root@evpOMV:/# ip a
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICASbash: root@evpOMV:/#: No such file or directory
T,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether b8:27:eb:82:b0:d7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.83.230/24 brd 192.168.83.255 scope global dynamic eth0
       valid_lft 835720sec preferred_lft 835720sec
    inet6 fe80::ba27:ebff:fe82:b0d7/64 scope link
       valid_lft forever preferred_lft forever

Display More

Quote from Zoki

But you will have to find someone who knowa armbian, I don't.

That's a pity. But i remember, Armbian was part of my first OMV image. Could you give me a hint which omv-forum i should use for armbian questions?

Zoki · Mar 23rd 2022

This forum is the right one, it is only me, who is clueless

macom, ryecoaaron can you help with armbian not updatin properly from omv4 to omv5.

Missing modules

- softdog

- mv_cesa

and ifup eth0 fails

KlausR · Mar 23rd 2022

thank you for your helpfulness, Zoki

ryecoaaron · Mar 23rd 2022

Quote from Zoki

can you help with armbian not updatin properly from omv4 to omv5.

I actually have done very few release upgrades on armbian because I have run into kernel issues and other problems. I normally write a new image and configure OMV again.

Participate now!