Yes... Again, PiHole works fine. What I'm after is what has or hasn't chanched when I ran omv-firstaid so that regular docker networking doesn't work....
Posts by tordenflesk
-
-
Yeah, that's a cut'n'paste thing. Anyways, it's regular containers that needed to add network_mode: host
-
Only the pihole one and that's set up like this:
Code
Display Moreversion: '2' services: pihole: container_name: pihole image: jacklul/pihole:latest hostname: DNS-PHL01 mac_address: d0:ca:ab:cd:ef:02 ports: - 443/tcp - 53/tcp - 53/udp - 80/tcp - 22/tcp environment: - TZ=Europe/Oslo - FTLCONF_REPLY_ADDR4=10.0.0.2 - FTLCONF_webserver_api_password=XXXXXXXX - FTLCONF_dns_revServers=true,10.0.0.0,10.0.0.1#53,localdomain - BLOCKLISTS_URL=https://v.firebog.net/hosts/lists.php?type=tick - ALLOWLISTS_URL=https://raw.githubusercontent.com/anudeepND/whitelist/master/domains/whitelist.txt - REGEX_BLACKLIST_URL=https://raw.githubusercontent.com/mmotti/pihole-regex/master/regex.list volumes: - /Docker_Config/PIHOLE:/etc/pihole:rw - /Docker_Config/PIHOLE/DNS/:/etc/dnsmasq.d/ - /Docker_Config/PIHOLE/pihole-updatelists:/etc/pihole-updatelists networks: Pihole_DNS: ipv4_address: 10.0.0.2 restart: always networks: Pihole_DNS: external: true -
Apologies for necroing, but I'm having a very similar issue after moving OMV to a new host. Ran OMV-firstaid and everything else seems to be working fine, however most containers won't resolve DNS unless I set network_mode: host
-
Nope, still happened. fresh install seemed perfectly stable overnight. Now back to the restored backup and disabled all scheduled tasks, rsync jobs and removed hd-idle (I'm suspecting the drive(s) might not be quite able to resume from idle)
-
New (expensive freight and customs) eMMC-module installed, restored from backup. The system has been semi-functional for a while (one data-disk flips to read-only after anywhere from 1 hour to 2 days).
I "re-built" the unit (moved drives, re-seated connectors etc.) and it was stable for 6+ hours.
This morning it's back to data-disks not mounting, long boots and the web-ui not letting me log in.
I might just have to restore the backup again and avoid updates for a while to see if there's an issue there.
-
-
output of dpkg --verify:
Code
Display Moremissing /etc/default/smartmontools.distrib missing /etc/smartd.conf.distrib ??5?????? c /etc/logrotate.conf ??5?????? c /etc/logrotate.d/btmp ??5?????? c /etc/logrotate.d/wtmp ??5?????? c /etc/skel/.bashrc ??5?????? c /etc/logrotate.d/proftpd-core ??5?????? c /etc/logrotate.d/php7.3-fpm ??5?????? c /etc/logrotate.d/php7.4-fpm missing /etc/default/monit.distrib ??5?????? c /etc/logrotate.d/monit missing /etc/monit/monitrc.distrib missing /usr/lib/arm-linux-gnueabihf/gtk-3.0 missing /usr/lib/arm-linux-gnueabihf/gtk-3.0/3.0.0 missing /etc/collectd/collectd.conf.distrib ??5?????? c /etc/logrotate.d/chrony missing /etc/cron-apt missing /etc/cron-apt/action.d missing c /etc/cron-apt/action.d/0-update missing c /etc/cron-apt/action.d/3-download missing /etc/cron-apt/config.distrib missing /etc/cron-apt/config.d missing /etc/cron-apt/mailmsg.d missing c /etc/cron.d/cron-apt ??5?????? c /etc/default/openmediavault ??5?????? c /etc/logrotate.d/openmediavault-rsync missing /etc/default/rrdcached.distrib ??5?????? c /etc/logrotate.d/rsyslog ??5?????? c /etc/logrotate.d/nginx missing /etc/hdparm.conf.distrib ??5?????? c /etc/systemd/journald.conf missing /etc/systemd/logind.conf.distrib ??5?????? c /etc/resolvconf/resolv.conf.d/head ??5?????? c /etc/lvm/lvm.conf ??5?????? c /etc/logrotate.d/omv-backup-command ??5?????? c /etc/fuse.conf missing /etc/default/wsdd.distrib ??5?????? c /etc/logrotate.d/unattended-upgrades ??5?????? c /etc/logrotate.d/salt-common missing /usr/share/icons/Adwaita ??5?????? c /etc/default/hd-idle ??5?????? c /etc/logrotate.d/hd-idle ??5?????? c /etc/default/rng-tools-debian ??5?????? c /etc/davfs2/secrets missing c /etc/logrotate.d/proftpd-basic ??5?????? c /etc/watchdog.conf missing /etc/avahi/avahi-daemon.conf.distrib missing /etc/default/avahi-daemon.distrib ??5?????? c /etc/sysctl.conf missing c /etc/logcheck/violations.ignore.d/rng-tools missing c /etc/logcheck/ignore.d.server/rng-tools missing c /etc/default/rng-tools ??5?????? /etc/issue ??5?????? /etc/issue.net ??5?????? /etc/os-release ??5?????? /usr/share/doc/base-files/changelog.gz ??5?????? /etc/armbian-release ??5?????? c /usr/lib/armbian/armbian-apt-updates ??5?????? c /etc/initramfs-tools/initramfs.conf missing /etc/cron.daily/mdadm.distrib ??5?????? c /etc/logrotate.d/samba ??5?????? c /etc/systemd/resolved.conf -
check dmesg for error
https://pastebin.com/raw/WiXVVxZw
No idea whether this one's relevant:
Code[ 2.916072] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_0 not found [ 2.916085] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_1 not foundSome I/O errors on my data drives, not sure if they're new to the situation.
Code[ 36.108292] I/O error, dev sdb, sector 7814034080 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 67.250369] I/O error, dev sdb, sector 32 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 119.709057] I/O error, dev sda, sector 128 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 147.442759] I/O error, dev sdb, sector 64 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2 [ 208.668734] I/O error, dev sdb, sector 7814036992 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2Code[ 198.141420] /dev/disk/by-uuid/15c056a7-04d3-4082-a4c5-a93bf7d0bbc3: Can't lookup blockdev [ 198.193557] /dev/disk/by-uuid/bf6a6cf0-b5d3-43b0-88ad-5b555c2ae69c: Can't lookup blockdev -
Only root and tmp are mounted according to btop.
omv-firstaid -> Configure workbench gives me this error:
ERROR: Failed to connect /var/lib/openmediavault/engined.sock: [Errno 2] No such file or directory
similar Error 500 Failed to connect to socket: No such file or directory
when attempting to log in to the web-ui.
reboots also take ~30 minutes...
-
Yes, but I've already read those the first time they get sent to me, again during omv-upgrade so a third time is "spam"
-
I've already hit the upgrade button / ran omv-upgrade. I don't need e-mails telling me what I've just done.
-
Yes, I'm sorry. That seems to have fixed it.
-
-
8 updates in the web UI, 0 running omv-upgrade.
These updates are the version that's already been installed.
-
The upgrade "fixed" it, I'm guessing similarly to an reboot. Not having high hopes. Just waiting now.
-
The only error that I'm able to see is:
Codecollectd[1675]: statvfs(/srv/mergerfs/BACKUP3) failed: Transport endpoint is not connected -
What version of mergerfs? Are you exporting it via NFS? Have you updated to the latest version?
Code
Display Moreopenmediavault-mergerfs 6.3.7 mergerfs: Installed: 2.35.0~debian-bullseye Candidate: 2.35.0~debian-bullseye Version table: *** 2.35.0~debian-bullseye 100 100 /var/lib/dpkg/status 2.34.1~debian-bullseye 500 500 http://adelolmo.github.io/bullseye bullseye/main armhf Packages 2.33.5~debian-bullseye 500 500 https://openmediavault-plugin-developers.github.io/packages/debian shaitan/main armhf Packages 2.31.0-1 500 500 http://deb.debian.org/debian bullseye/main armhf PackagesSMB, no NFS
-
Indeed, in that case it seems unlikely.
Other possibilities occur to me:
Something to do with power states, I don't know if you have the drives set to sleep after a certain amount of time.
Something related to some intensive activity on the server that could cause this.
I would look in the logs for what is happening at the time the drives are unmounted.
The drives are available and working via alternative SMB-shares. It's mergerFS that fails.
Which specific logs?
-
They're both available outside of MergerFS and have been rock solid up until about a month ago. Seems unlikely.
