Posts by devnet

    Quick question...is this supposed to be this way?


    Code
    root@mediacenter:~# systemctl list-unit-files | grep monit
    lvm2-monitor.service enabled
    mdmonitor-oneshot.service static
    mdmonitor.service static
    monit.service generated
    nut-monitor.service enabled
    openmediavault-cleanup-monit.service enabled
    ups-monitor.service masked
    mdmonitor-oneshot.timer disabled


    I'm speaking specifically of ups-monitor.service being masked.

    OK, I have figured it out.


    The install evidently kills monit or it doesn't run. I had to connect in via SSH in order to execute systemctl restart monit and then enable nut on the plugin screen and click save, then apply.


    Not sure why monit was dead...but I'll make sure that it starts with the rest of the startup services.

    I disabled backports and cleaned out the package cache. Purged nut again and reinstalled but getting the same error. I'm googling and plenty of people have had this problem but none of the solutions they are posting are working for me.

    Hello,


    I recently tried installing omv nut. I was told that I needed to fix the usrmerge problem on my system and so I installed this package and ran it with no issues. However, I am still receiving an odd error when trying to enable the nut plugin:


    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 nut 2>&1' with exit code '1':
    mediacenter.donquixote.org: ---------- ID: configure_nut_nut_conf Function: file.managed Name: /etc/nut/nut.conf Result: True Comment: File /etc/nut/nut.conf is in the correct state Started: 17:48:27.653355 Duration: 18.618 ms Changes: ---------- ID: configure_nut_ups_conf Function: file.managed Name: /etc/nut/ups.conf Result: True Comment: File /etc/nut/ups.conf is in the correct state Started: 17:48:27.672068 Duration: 5.695 ms Changes: ---------- ID: configure_nut_upsd_conf Function: file.managed Name: /etc/nut/upsd.conf Result: True Comment: File /etc/nut/upsd.conf is in the correct state Started: 17:48:27.677851 Duration: 7.321 ms Changes: ---------- ID: configure_nut_upsd_users Function: file.managed Name: /etc/nut/upsd.users Result: True Comment: File /etc/nut/upsd.users updated Started: 17:48:27.685261 Duration: 8.977 ms Changes: ---------- diff: --- +++ @@ -1,11 +1,11 @@ # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. [admin] -password = Mpy619msaiMowk54 +password = 11mgEuSHaMpMkg4B actions = set actions = fsd instcmds = ALL [monmaster] -password = 6K7X9TvVZTIIWQYX +password = N9e1SVjFDRfTLTGa upsmon master ---------- ID: configure_nut_upsmon_conf Function: file.managed Name: /etc/nut/upsmon.conf Result: True Comment: File /etc/nut/upsmon.conf updated Started: 17:48:27.694329 Duration: 12.788 ms Changes: ---------- diff: --- +++ @@ -1,6 +1,6 @@ # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. -MONITOR ups 1 monmaster 6K7X9TvVZTIIWQYX master +MONITOR ups 1 monmaster N9e1SVjFDRfTLTGa master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD "/sbin/upssched" ---------- ID: configure_nut_upssched_conf Function: file.managed Name: /etc/nut/upssched.conf Result: True Comment: File /etc/nut/upssched.conf updated Started: 17:48:27.707208 Duration: 7.497 ms Changes: ---------- diff: --- +++ @@ -12,7 +12,7 @@ AT SHUTDOWN * EXECUTE notify AT ONLINE * CANCEL-TIMER shutdown AT ONLINE * EXECUTE resume -AT ONBATT * START-TIMER shutdown 1800 +AT ONBATT * START-TIMER shutdown 30 AT ONBATT * EXECUTE shutdown-warning AT LOWBATT * START-TIMER shutdown AT LOWBATT * EXECUTE shutdown-warning ---------- ID: configure_nut_default_upssched_cmd Function: file.managed Name: /etc/default/upssched-cmd Result: True Comment: File /etc/default/upssched-cmd updated Started: 17:48:27.714793 Duration: 1.883 ms Changes: ---------- diff: --- +++ @@ -1,4 +1,4 @@ # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. OMV_NUT_UPSSCHEDCMD_EMAIL_ENABLE="NO" -OMV_NUT_UPSSCHEDCMD_SHUTDOWNTIMER=1800 +OMV_NUT_UPSSCHEDCMD_SHUTDOWNTIMER=30 ---------- ID: remove_nut_udev_serialups_rule Function: file.absent Name: /etc/udev/rules.d/99-openmediavault-nut-serialups.rules Result: True Comment: File /etc/udev/rules.d/99-openmediavault-nut-serialups.rules is not present Started: 17:48:27.716753 Duration: 0.389 ms Changes: ---------- ID: start_nut_driver_service Function: service.running Name: nut-driver Result: True Comment: Service nut-driver is already enabled, and is running Started: 17:48:27.724896 Duration: 5765.843 ms Changes: ---------- nut-driver: True ---------- ID: start_nut_server_service Function: service.running Name: nut-server Result: True Comment: Service restarted Started: 17:48:33.512857 Duration: 717.287 ms Changes: ---------- nut-server: True ---------- ID: monitor_nut_server_service Function: monit.monitor Name: nut-server Result: False Comment: An exception occurred in this state: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/state.py", line 2154, in call *cdata["args"], **cdata["kwargs"] File "/usr/lib/python3/dist-packages/salt/loader.py", line 2087, in wrapper return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/states/monit.py", line 46, in monitor if "Running" in value[name]: TypeError: string indices must be integers Started: 17:48:34.231318 Duration: 9.856 ms Changes: ---------- ID: start_nut_monitor_service Function: service.running Name: nut-monitor Result: True Comment: Service restarted Started: 17:48:34.270969 Duration: 49.039 ms Changes: ---------- nut-monitor: True ---------- ID: monitor_nut_monitor_service Function: monit.monitor Name: nut-monitor Result: False Comment: An exception occurred in this state: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/state.py", line 2154, in call *cdata["args"], **cdata["kwargs"] File "/usr/lib/python3/dist-packages/salt/loader.py", line 2087, in wrapper return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/states/monit.py", line 46, in monitor if "Running" in value[name]: TypeError: string indices must be integers Started: 17:48:34.320371 Duration: 9.65 ms Changes: Summary for mediacenter.donquixote.org ------------- Succeeded: 11 (changed=7) Failed: 2 ------------- Total states run: 13 Total run time: 6.615 s

    Specifically, I see two things that fail above:


    Code
    ID: monitor_nut_server_service Function: monit.monitor Name: nut-server Result: False Comment: An exception occurred in this state: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/state.py", line 2154, in call *cdata["args"], **cdata["kwargs"] File "/usr/lib/python3/dist-packages/salt/loader.py", line 2087, in wrapper return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/states/monit.py", line 46, in monitor if "Running" in value[name]: TypeError: string indices must be integers Started: 17:48:34.231318 Duration: 9.856 ms
    and
    ID: monitor_nut_monitor_service Function: monit.monitor Name: nut-monitor Result: False Comment: An exception occurred in this state: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/state.py", line 2154, in call *cdata["args"], **cdata["kwargs"] File "/usr/lib/python3/dist-packages/salt/loader.py", line 2087, in wrapper return f(*args, **kwargs) File "/usr/lib/python3/dist-packages/salt/states/monit.py", line 46, in monitor if "Running" in value[name]: TypeError: string indices must be integers Started: 17:48:34.320371 Duration: 9.65 ms Changes: Summary for mediacenter.donquixote.org ------------- Succeeded: 11 (changed=7) Failed: 2 ------------- Total states run: 13 Total run time: 6.615 s


    I'm not certain what to do ...these both seem to be stating line 46 of monit.py are having an issue with the enable script that runs from OMV5. Line 46 (line 3 below) looks like this:


    Code
    try:
    for key, value in result.items():
    if "Running" in value[name]:
    ret["comment"] = ("{0} is being being monitored.").format(name)
    ret["result"] = True


    This seems to be a bug? Can someone help me resolve this issue?

    Yep, paths were correct...because I rebooted the server, and things just magically came up. So very strange. It was like it couldn't see anything at all in the directory when I changed it back to where it should have been....and no amount of service restarts would force it to see. I am one of those old school folks that don't want to reboot servers EVER.


    Sometimes you gotta use the heavy hammer I guess lol.

    As it is now, this is dead in the water...no containers being recognized at all, nothing being started, can't start them manually because Docker can't see them.


    I'm not sure what's going on to be honest...it should just be able to be pointed toward a new location and pick up the data inside. I've done that before with vanilla Debian. But something else is happening here and I'm not sure what it is.

    Yep:


    Hiya,


    Yep, it is:


    Code
    root@windmill:~# cat /etc/docker/daemon.json
    {
    "data-root": "/srv/dev-disk-by-label-Storage/DockerImages"
    }



    Code
    root@windmill:~# docker images
    REPOSITORY TAG IMAGE ID CREATED SIZE
    root@windmill:~#

    Hi Guys,


    Rebooted tonight for the first time post OMV5 upgrade from 4. Upon boot, none of my containers started. Investigation shows that none of them were found (did a docker list). I went into the configuration page in OMV-Extras and found that the default path had been placed inside (/var/lib/... ). The actual path of my containers is /srv/dev-disk-by-label-Storage/DockerImages. I changed this and restarted the docker service...however, it won't recognize my previous containers and says that none are there to start.


    Can someone point me in the right direction so I don't have to recreate all my containers?

    If it can help, here's the procedure i followed to upgrade from an up-to-date ovm 4 to 5.

    There's a few differences with the one i found on this forum :

    The only issue i had after that, is related to my ftp client which wasn't correctly detecting the encoding announced by proftpd, and wasn't able to enter any folder with special character in its name. I fixed it by forcing (in my ftp client) the connection to utf-8.


    is the purge command at the top just your installed plugins or are there more listed there that need the purge?

    Hi all,


    Union Filesystem Plugin: I have a MergerFS pool setup as follows:

    Code
    /dev/sde1 1.9T 2.0G 1.9T 1% /srv/dev-disk-by-label-WD2TBTwo
    /dev/sdb1 1.9T 2.0G 1.9T 1% /srv/dev-disk-by-label-WD2TBOne
    /dev/sdc1 3.7T 1.3T 2.4T 36% /srv/dev-disk-by-label-SGT4TBTwo
    /dev/sda1 3.7T 1.3T 2.4T 36% /srv/dev-disk-by-label-SGT4TBOne


    SDC1 is parity...the other 3 are inside a MergerFS pool. So I have a motherboard replacement that needs to take place...which means I'll have to reinstall OMV on the system drive. Since MergerFS spans data across drives, what's the proper way to take a pool that was on one system and get it up and running on the other system without losing data?


    Has anyone ever done this before? Am I over-complicating things?

    OMV5 will most likely be out AFTER Buster...and will take some time to make sure it is stable. One can assume it won't come out simultaneously.


    If you look @ OMV4, it came out 11 months after Debian 9. Good rule of thumb is to assume a similar timeline.

    If you decide to not use the Pi (I wouldn't...but I built my NAS with an older i5 I had not doing anything) I recommend the Fractal Design cases...specifically, you could use a MiniITX build for the Node 304. It can fit up to 6 3.5 inch hard drives and has three fans and superior airflow. 2 x 92 silent fans and a single 140mm fan are quiet and the hard drives all have rubber mounts to absorb vibration.


    I built one with the mATX Node 804 and I couldn't be happier with the way they manage airflow and hard drive mounting.

    I've found that I can't delete shares when they are being used by other services. For example, I had docker utilizing a shared folder, I had to make sure that docker was no longer using the fileshare before I could delete it.


    Look closely at what is being used by other plugins/services...you can't delete something that is being used.