Posts by gadric

    This guide was inspired by the [GUIDE] Use Telegram as notification service by subzero79. I used Telegram for a long time. But due to a more privacy and data protection approach of Signal, I switched to Signal Messenger.

    What you need

    • A free phone number
    • curl
    • Remote ssh access with sudo access
    • Docker

    Signal does not offer a bot service, so we need to have an extra number to act as the bot. There are a couple of service providers which offers free phone numbers. Should be easy to obtain an extra number.

    Once you have the extra number, connect to your OMV instance via ssh and then install docker:

    sudo apt-get update
    sudo apt-get install docker-ce docker-ce-cli

    bbernhard created a signal-cli wrapper which offers a rest-api: This will be used to send the notifications over Signal.

    To start the port using this command

    docker run \
    --name "/signal-cli-rest-api" \
    --volume "<config_path>:/home/.local/share/signal-cli" \
    --restart "unless-stopped" \
    --port "8080:8080" \

    To register the number, follow the official guide:…ob/master/doc/

    Once this is done, we can create our script

    nano /usr/share/openmediavault/notification/sink.d/10signal

    Then paste this content into the file:

    Save the file

    Then the script needs to be made executable:

    chmod 700 /usr/share/openmediavault/notification/sink.d/10signal

    Can you try moving: /usr/lib/systemd/system-sleep/autoshutdown-restart to /lib/systemd/system-sleep/autoshutdown-restart as in the 5.1.7 update we move to systemd start-up what than pm-utils. if this work you should see the script (above autoshutdown-restart) write a log entry to /var/log/autoshutdown.log on the restart if this is not logged the the scripts if still falling for some reason. Also can you verify you are using 'systemctl suspend' command.

    Please leave feedback if the above works and raze bug in:…enmediavault-autoshutdown and i jump on a fix ASAP

    I got this working, but not with this solution.

    In /usr/lib/systemd/system-sleep/ and in /lib/systemd/system-sleep/ the same file existed.

    What I did: chmod +x /lib/systemd/system-sleep/autoshutdown-restart not the /usr/... .

    Now it seems to work again.


    I have a problem with the most recent version of autoshutdown plugin. If worked perfect since a couple of years. With the most recent version (5.1.7) it behaves strange. When the system wakes up from sleep mode, then the plugin is inactive. `systemctl status autoshutdown.service` Shows `inactive`. In this state, my system wont get back to sleep again. I have to activate is manually.

    Any ideas?


    I have been using custom notification with telegram following this guide: [GUIDE] Use Telegram as notification service. This works very good also with OMV5.

    However, I am thinking to switch to Signal Messenger. I thought I could use a similar approach. I have duplicated the Telegram OMV sink.d file and inserted this code for signal:

    echo -e "${OMV_NOTIFICATION_SUBJECT} on the ${OMV_NOTIFICATION_DATE} \n\n $(cat ${OMV_NOTIFICATION_MESSAGE_FILE})" |signal-cli -u $sender send $recipiant

    However, this script seems not to be triggered.

    I tested already manual message sending with signal which works very well. Also using this commands it works without any issues:

    export OMV_NOTIFICATION_DATE=testdate
    export OMV_NOTIFICATION_MESSAGE_FILE=/tmp/testfile

    Any idea why it does not work automatically with custom notification and sink scripts?


    Since a couple of days I ran into a strange „problem“. In OMV WebGUI or using df in the console, it reports my /dev/sda1 mounted in /boot/efi as nearly full

    However, Checking with du, orgparted  reports something completed different:

    root@xxxxxxxx:~# du -sh /boot/efi/
    5.2M /boot/efi/

    I already purged old Kernels and also did apt-get autoremove and rebooted a couple of times. Nothing helped so far.

    Anyone has an idea?

    3.7.6 appears to have fixed everything but the Diff script is still issuing the same error at line 490.

    Same error here.

    ah I see. Maybe the unisonFS plugin is the problem. Can you please post your fstab config ? I would like to check if something in my config is wrong.

    my config look is this:

    /srv/dev-disk-by-label-xxxx:/srv/dev-disk-by-label-xxxx:/srv/dev-disk-by-label-xxxx:/srv/dev-disk-by-label-xxxx:/srv/dev-disk-by-label-xxxx:/srv/dev-disk-by-label-xxxx /srv/yyyyyyyyyyyyyyyyyyyyyyyyyyy fuse.mergerfs defaults,allow_other,direct_io,use_ino,category.create=mfs,minfreespace=500G 0 0


    I am running OMV Server (latest OMV4 version) with the most recent version of Plex Media Server (version, non-docker). All my media is on a unisonfilesystem drive. Yesterday I saw that mergerfs has an update to version 2.26.2 (previous version: 2.25.1). After upgrade, Plex is not able to find any files. It always says "File not available". I can play everything with VLC or MPC. Media files on drives outside UnionFS is also works with Plex.

    Now I downgraded mergerfs to version 2.25.1 again and everything works fine.

    Anyone has the same problem or know a solution?

    I tried the script yesterday and it works like a charm. Thank you for publishing the guide.

    However, it does not send the notification e-mails from "scheduled jobs" as a telegram message to me. Is the e-mail notification in "scheduled jobs" not integrated in the default notification agent?


    I justed reinstall OMV 3.0 as my system HDD crashed. I also reinstalled the lastest letsencrypt version. The setup works fine and I can also generate a valid certificate. However, I am not able to create a cron job. When I try to enter the omv-letsencrypt command in the shell, it says that the command does not exists. A reinstall of the plugin did not help. Is this a bug?

    best regards,