Beiträge von pbartko

pbartko · 29. Dezember 2021

No services exposed to internet, local network only. Strange thing is how it increases cpu usage linearly over time.

pbartko · 29. Dezember 2021

My OMV5 server has been running well for over a year now. Last week, I rebooted the system after installing a new docker image for Home Assistant. Today I looked at the System performance charts to look at system loads with the new docker image and found something disturbing. As the system ran continuously for over a year, the CPU usage steadily crept up over time to 40% by last week when I rebooted the server. Is this normal? I wish I had noticed this before rebooting the server so I could have checked TOP to find out what software was actually using all that CPU. In all fairness, I'm not sure it was OMV, as I also have a few docker containers running (Plex, Portainer, Duplicati).

Thanks

pbartko · 8. Februar 2020

Some more Diagnostics today:

There are two network adapters on the MOBO. I tried the other one, with the same results, no network connection after reboot.

After a reboot, running "systemctl status systemd-networkd" command results in the following output:

Code

root@lord-yu:~# systemctl status systemd-networkd
â systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2020-02-08 17:18:44 EST; 2min 43s ago
     Docs: man:systemd-networkd.service(8)
  Process: 466 ExecStart=/lib/systemd/systemd-networkd (code=exited, status=1/FAILURE)
 Main PID: 466 (code=exited, status=1/FAILURE)


Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: systemd-networkd.service: Service has no hold-off time (Res
tartSec=0), scheduling restart.
Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: systemd-networkd.service: Scheduled restart job, restart co
unter is at 5.
Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: Stopped Network Service.
Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: systemd-networkd.service: Start request repeated too quickl
y.
Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
Feb 08 17:18:44 lord-yu.bartserver.com systemd[1]: Failed to start Network Service.

Alles anzeigen

After running omv-firstaid and setting a static ip address to 192.168.1.85, output is:

Code

root@lord-yu:~# systemctl status systemd-networkd
â systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2020-02-08 17:22:57 EST; 3min 50s ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 2133 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 2.0M
   CGroup: /system.slice/systemd-networkd.service
           ââ2133 /lib/systemd/systemd-networkd


Feb 08 17:22:57 lord-yu.bartserver.com systemd[1]: Starting Network Service...
Feb 08 17:22:57 lord-yu.bartserver.com systemd-networkd[2133]: Enumeration completed
Feb 08 17:22:57 lord-yu.bartserver.com systemd[1]: Started Network Service.
Feb 08 17:22:57 lord-yu.bartserver.com systemd-networkd[2133]: enp2s0: Gained carrier
Feb 08 17:22:57 lord-yu.bartserver.com systemd-networkd[2133]: enp2s0: Configured

Alles anzeigen

Question is, why is it failing at startup but runs after using omv-firstaid?

Any help is much appreciated!

Thanks,

Pete

pbartko · 7. Februar 2020

I've recently setup a new OMV5 installation to replace my OMV3 server that's been running now for several years. However, I am having trouble setting the IP address. I set a static address of 192.168.1.85 using the GUI, but after a reboot, there is no network connection. I have to login to the console and use omv-firstaid to reset the network connection. The system will be fine then up until a reboot.

I've checked /etc/sytemd/network folder for the adapter entry, it looks correct:

Code: /etc/systemd/network/10-openmediavault-eno1.network

root@lord-yu:/etc/systemd/network# cat 10-openmediavault-eno1.network
[Match]
Name=eno1


[Network]
Address=192.168.1.85/24
Gateway=192.168.1.1
IPv6AcceptRA=no
LinkLocalAddressing=no
DNS=8.8.8.8
Domains=bartserver.com


[Link]


[IPv6Prefix]

Alles anzeigen

results of ip addr after reboot:

Code

root@lord-yu:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether fc:aa:14:2b:e4:f0 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether fc:aa:14:2b:e4:f2 brd ff:ff:ff:ff:ff:ff
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:de:fc:d7:3b brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
6: vethb091296@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether 9a:01:07:ce:e2:1d brd ff:ff:ff:ff:ff:ff link-netnsid 0

Alles anzeigen

results of ip addr after omv-firstaid:

Code

root@lord-yu:~# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether fc:aa:14:2b:e4:f0 brd ff:ff:ff:ff:ff:ff
3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether fc:aa:14:2b:e4:f2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.85/24 brd 192.168.1.255 scope global eno1
       valid_lft forever preferred_lft forever
4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:42:28:16:bd:fa brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
6: vethdbc5309@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default
    link/ether 8a:5e:23:22:45:5a brd ff:ff:ff:ff:ff:ff link-netnsid 0

Alles anzeigen

As you can see, eno1 ip address is not set until after running omv-firsaid. Can anyone give me suggestions on what else to check?

Thanks,

Pete

Beiträge von pbartko

CPU Usage Leak?

CPU Usage Leak?

OMV 5 no network connection after reboot

OMV 5 no network connection after reboot