Posts by odragon

  • Nut UPS plugin spamming syslog when using as network client

    I noticed recently that my syslog was being flooding (every 15 seconds, but still) with errors about nut.


    Problem is my UPS is setup with a nut server on a remote host. And it works just fine. I've had power outages in the past year and the omv server would shutdown as requested.


    For some reason the nut server is still looking for a local UPS.


    Could it be the nut.conf?

    Code
    root@hostname:/etc/nut# cat ups.conf

# This file is auto-generated by openmediavault (https://www.openmediavault.org)

# WARNING: Do not edit this file, your changes will get lost.
[apcsmt1500]
driver = usbhid-ups
port = auto

  • Upgrade 6 to 7 issues with Helio4

    I ran into a few issues upgrading my Helios4 from OMV6 to 7. Some I was able to resolve on my own. I'll post them anyway in case someone runs into the same issues.


    The first one was that the network interface changed name from eth0 to end1. So networking was down after reboot. Had to login through the serial console. I then renamed and modified /etc/network/interfaces.d/1-eth0. Then flush (iptables -F) and fix the firewall rules.


    Next were a few services that failed to start:

    • fancontrol
    • helios4-wol
    • nut-driver@apcsmt1500

    Fancontrol was easy enough to fix: I installed the fancontrol package manually. I still have the openmediavault-helios4 5.0 plugin installed, but it doesn't seem to be available at omv-extras.org...


    helios4-wol is set to eth0 and I can't seem to find its config. Is that a remnant of the openmediavault-helios4 plugin?


    Finally the nut driver, I'm not so sure what's happening. It's in some sort of boot loop where it just tries to start over and over again with these errors in syslog:


    Code
    2024-03-18T22:56:29.802295-04:00 localhost nut-driver@apcsmt1500[3528]: Network UPS Tools - Generic HID driver 0.47 (2.8.0)
2024-03-18T22:56:29.802481-04:00 localhost nut-driver@apcsmt1500[3528]: USB communication driver (libusb 1.0) 0.43
2024-03-18T22:56:29.802594-04:00 localhost nut-driver@apcsmt1500[3528]: libusb1: Could not open any HID devices: insufficient permissions on everything
2024-03-18T22:56:29.802694-04:00 localhost nut-driver@apcsmt1500[3528]: No matching HID UPS found
2024-03-18T22:56:29.803053-04:00 localhost nut-driver@apcsmt1500[3527]: Driver failed to start (exit status=1)
2024-03-18T22:56:29.805010-04:00 localhost nut-driver@apcsmt1500[3527]: Network UPS Tools - UPS driver controller 2.8.0
2024-03-18T22:56:29.805249-04:00 localhost systemd[1]: nut-driver@apcsmt1500.service: Control process exited, code=exited, status=1/FAILURE
2024-03-18T22:56:29.805434-04:00 localhost systemd[1]: nut-driver@apcsmt1500.service: Failed with result 'exit-code'.
2024-03-18T22:56:29.805716-04:00 localhost systemd[1]: Failed to start nut-driver@apcsmt1500.service - Network UPS Tools - device driver for NUT device 'apcsmt1500'.
2024-03-18T22:56:43.711336-04:00 localhost systemd[1]: Stopped nut-driver@apcsmt1500.service - Network UPS Tools - device driver for NUT device 'apcsmt1500'.

    The thing is, it's not plugged-in via USB. It's managed by another machine and monitored through network.


    If someone has an idea, please let me know.


    Thanks.

  • OMV not mounting NFS on boot

    I have a similar setup. I used different mount options though.


    I used type 'nfs' instead of 'nfs4', and I have the following options: defaults,vers=4,rw,noexec


    In any case I would try with as few options as possible to have a working setup. Then add more one by one until you can reproduce the issue.

  • Update to Debian 12 (Bookworm)

    In what could only be described as naïve stupidity, I thought it would be a great idea to try and "upgrade" to Debian 12. Obviously it didn't work.


    Therefore I thought I would come here and ask for forgiveness... I mean advice. The openmediavault package auto uninstalled due to dependencies issues. Now when I try to re-install it it wants nothing to do with me because:

    Code
    The following packages have unmet dependencies:
 php-common : Breaks: php7.4-common but 7.4.33-1+deb11u4 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

    That's great, but I'm not sure why php7.4-common needs installing...


    I'm not very knowledgeable with Debian packaging, but looking at the output below, I don't see php-common. Now I checked on https://packages.debian.org/bookworm/php-common, and searching around a bit, it looks like most php modules depend on php-common. Fair enough. Still can't figure out who needs php7.4-common though...

    Any ideas of things to try that could help?


    Thank you so very very much.

  • Notifications SMTP postifx settings apply fails

    Turns out postfix does not like the hostname to be "localhost." Makes sense I suppose. I don't recall setting it to localhost though. Maybe I never set it before and it just used the default value, or it got overwritten during the update from OMV5 to OMV6. Either way, seems like a usability issue with OMV.


    Thanks for the help. Notifications work now!

  • Notifications SMTP postifx settings apply fails

    Ah... hostfile. Duh!


    Following the trail :

    Code
    odragon@omb:~$ cat /etc/hosts
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
127.0.0.1 localhost.localdomain localhost
127.0.1.1               localhost

  • Notifications SMTP postifx settings apply fails

    Quote from Agricola

    So notifications worked fine when it was on OMV5? How did you upgrade?

    No. I did not have notifications set prior to now.


    Quote from macom

    What is the output of


    postfix set-permissions?

    The output is the following:


    postfix: fatal: parameter inet_interfaces: no local interface found for 127.0.1.1


    That would indeed explain the error. My localhost is 127.0.0.1:


    Code
    odragon@omv:~$ ifconfig
...
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 688542  bytes 284158440 (270.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 688542  bytes 284158440 (270.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    Why does postfix think that inet_interfaces = localhost means localhost resolves to 127.0.1.1?

  • Notifications SMTP postifx settings apply fails

    Hi Agricola and thanks for the reply.


    I'm using my ISP's SMTP server, and it works great for both pfSense and Nextcloud. I don't think it's a problem with the settings. OMV seems to be having issues setting permissions on something (see log in first post). Since I can't "Apply" or "Confirm" settings, the notifications don't get enabled. There's nothing in syslog.


    Here's my /etc/postfix/main.cf if it's any use. The folder and all files in it are owned by root.


  • Notifications SMTP postifx settings apply fails

    Greetings,


    I tried to setup notifications (did not have any before) but I am unable to apply the settings after saving them. It appears to fail a step called `postfix_set_permissions`.


    Helios 4

    Debian 11 Bullseye

    OMV 6.0.31 (upgraded from v5 on Buster a few months ago without noticing other issues)


    Stacktrace and system report attached. Let me know if I forgot some information.


    Can anyone else reproduce this? Any ideas how I could debug and/or fix this?


    Thanks.

  • Trying to salvage data from dead Helios4 nas + Openmediavault

    Hi Louis.


    Strangely, I have a similar issue except I don't think lightning struck nearby. I too have been running OMV on my helios4 for several years. A couple of months ago I upgraded from Debian Bullseye to Buster without any hic ups. And now this...


    I haven't tried re-installing and formatting my SD-card yet, but I get this boot loop around 30 times and then it stops :


  • /run out of space (samba)

    Hi,


    I had created a thread about an issue (Unable to setup USB backup) but after further investigation it seems the problem was not with USB backup. After a reboot, I was able to add the shares.


    Indeed the error message was pointing in the right direction. /run was running out of space. The tmpfs has 200MB but 195MB were used. 175MB were taken by /run/samba/gencache_notrans.tdb. I did a quick search online and the only relevant information I could find about this file is an old documentation page about Samba v3, which wasn't very helpful in any case.


    Would anyone have a clue as to what the problem might be?


    I'll keep digging through the logs to see if I can find anything... and keeping an eye on free space in /run.


    Thanks for you help.


    -Olivier

  • Unable to setup USB backup

    Hi,


    I would really appreciate help resolving the following issue. I used to have all my shares backed up using the USB Backup pluging on OMV4 and it worked flawlessly. I have now upgraded to OMV 5.5.1, USB Backup Plugin 5.0.4-1, on a Helios4 running Debian Buster with four disks in RAID 10 and when I try to apply the configuration after adding share to USB backup I get the following error.


    I have tried with and without the filesystems mounted.

    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run usbbackup 2>&1' with exit code '1': helios: ---------- ID: create_usbbackup_scripts_dir Function: file.directory Name: /var/lib/openmediavault/usbbackup.d Result: True Comment: Files cleaned from directory /var/lib/openmediavault/usbbackup.d Started: 13:31:37.122086 Duration: 5.911 ms Changes: ---------- /var/lib/openmediavault/usbbackup.d/rsync-6a5bbfb8-eb50-4d7a-b670-a8b997e812c8: ---------- removed: Removed due to clean /var/lib/openmediavault/usbbackup.d/systemd-acd975cd34b1150bf746789c01c2802f: ---------- removed: Removed due to clean removed: - /var/lib/openmediavault/usbbackup.d/systemd-acd975cd34b1150bf746789c01c2802f - /var/lib/openmediavault/usbbackup.d/rsync-6a5bbfb8-eb50-4d7a-b670-a8b997e812c8 ---------- ID: remove_usbbackup_rsync_scripts Function: module.run Result: True Comment: file.find: [] Started: 13:31:37.129841 Duration: 2.857 ms Changes: ---------- file.find: ---------- ID: remove_usbbackup_systemd_scripts Function: module.run Result: True Comment: file.find: [] Started: 13:31:37.133059 Duration: 2.574 ms Changes: ---------- file.find: ---------- ID: disable_usbbackup_systemd_unitfile_openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service Function: service.disabled Name: openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service Result: False Comment: Failed when setting service openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service to not start at boot, but the service was already running Started: 13:31:37.166616 Duration: 181.292 ms Changes: ---------- ID: remove_usbbackup_systemd_unitfile_openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service Function: file.absent Name: /lib/systemd/system/openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service Result: True Comment: Removed file /lib/systemd/system/openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service Started: 13:31:37.348768 Duration: 10.04 ms Changes: ---------- removed: /lib/systemd/system/openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service ---------- ID: configure_usbbackup_rsync_script_5c18aee9-feb9-421d-97bc-07e4bdf03a82 Function: file.managed Name: /var/lib/openmediavault/usbbackup.d/rsync-5c18aee9-feb9-421d-97bc-07e4bdf03a82 Result: True Comment: File /var/lib/openmediavault/usbbackup.d/rsync-5c18aee9-feb9-421d-97bc-07e4bdf03a82 updated Started: 13:31:37.359250 Duration: 261.355 ms Changes: ---------- diff: New file mode: 0750 ---------- ID: configure_usbbackup_systemd_script_acd975cd34b1150bf746789c01c2802f Function: file.managed Name: /var/lib/openmediavault/usbbackup.d/systemd-acd975cd34b1150bf746789c01c2802f Result: True Comment: File /var/lib/openmediavault/usbbackup.d/systemd-acd975cd34b1150bf746789c01c2802f updated Started: 13:31:37.620999 Duration: 121.435 ms Changes: ---------- diff: New file mode: 0750 ---------- ID: configure_usbbackup_systemd_unitfile_acd975cd34b1150bf746789c01c2802f Function: file.managed Name: /lib/systemd/system/openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service Result: True Comment: File /lib/systemd/system/openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service updated Started: 13:31:37.742832 Duration: 73.11 ms Changes: ---------- diff: New file mode: 0644 ---------- ID: usbbackup_systemctl_daemon_reload Function: module.run Name: service.systemctl_reload Result: True Comment: Started: 13:31:37.816590 Duration: 1.79 ms Changes: ---------- ID: enable_usbbackup_systemd_unitfile_acd975cd34b1150bf746789c01c2802f Function: service.enabled Name: openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f Result: False Comment: Failed when setting service openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f to start at boot, but the service was already running. Additional information follows: Created symlink /etc/systemd/system/dev-disk-by\x2did-usb\x2d152d_USB_3.0_Device_DB98765432155\x2d0:0\x2dpart1.device.wants/openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service -> /lib/systemd/system/openmediavault-usbbackup-acd975cd34b1150bf746789c01c2802f.service. Failed to reload daemon: Refusing to reload, not enough space available on /run/systemd. Currently, 5.8M are free, but a safety buffer of 16.0M is enforced. Started: 13:31:37.818810 Duration: 188.336 ms Changes: Summary for helios ------------ Succeeded: 8 (changed=7) Failed: 2 ------------ Total states run: 10 Total run time: 848.700 ms


    I'm also getting the not enough space available on /run/systemd when running updates though that seems to complete without issues. Could that be the problem? In any case, the Show Details button gives the info attached (message too long).



    Please let me know if I can provide more information.


    Thanks again in advance for your help.


    -Olivier

  • How to restore from an omv-backup?

    Quote from ryecoaaron

    Here is a basic restore procedure using dd for the same hard drive but a change went bad:

    • Boot systemrescuecd - if you installed the iso from omv-extras, it will be in your grub menu.
    • Mount your data drive - example: mount /dev/sde1 /mnt/backup
    • Figure out where your backup file is. dd uses the .dd.gz extension - example: /mnt/backup/omvbackup/backup-omv-07-May-2018_10-36-31.dd.gz
    • Figure out what your OS drive root partiton is. Don't get this wrong! - example: /dev/sda1
    • Restore the files - example gunzip -c /mnt/backup/omvbackup/backup-omv-07-May-2018_10-36-31.dd.gz | dd of=/dev/sda1 bs=1M status=progress
    • reboot

    Hi. I hosed my system in the process of trying to upgrade from OMV 4 to OMV 5. Thankfully I have backups, but I'm having trouble restoring them. I have the following files :

    Code
    -rwxr-xr-x 1 oli oli        1171 Apr 18 00:00 backup-omv-18-Apr-2020_00-00-02.blkid
-rwxr-xr-x 1 oli oli 10508875462 Apr 18 01:51 backup-omv-18-Apr-2020_00-00-02.dd.gz
-rwxr-xr-x 1 oli oli         373 Apr 18 00:00 backup-omv-18-Apr-2020_00-00-02.fdisk
-rwxr-xr-x 1 oli oli         446 Apr 18 00:00 backup-omv-18-Apr-2020_00-00-02.grub
-rwxr-xr-x 1 oli oli         512 Apr 18 00:00 backup-omv-18-Apr-2020_00-00-02.grubparts
-rwxr-xr-x 1 oli oli        1251 Apr 18 00:00 backup-omv-18-Apr-2020_00-00-02.packages
-rwxr-xr-x 1 oli oli      739541 Apr 18 00:00 backup-omv_u-boot-18-Apr-2020_00-00-02.tar.bz

    I tried the method above, but for some reason, the dd image is bigger than my partition by 1792*512 bytes, so it gets truncated and the filesystem is corrupted. fsck is able to fix the numerous errors but I don't want to trust nothing got broken.

    Code
    Disk /dev/mmcblk0: 29.7 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xe8f118bf

Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1       8192 61710591 61702400 29.4G 83 Linux

    I tried putting in directly on the device instead of the partition but again it doesn't work (no partition table):

    Before I mess things up even more, I wanted to double-check with the forum users what they think I should do. I was thinking of restoring the grubparts, resizing the partition to accomodate the dd image and try restoring that.


    Does anyone have a better idea?


    Thanks.