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 containerd.io

bbernhard created a signal-cli wrapper which offers a rest-api: https://github.com/bbernhard/signal-cli-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" \
  "bbernhard/signal-cli-rest-api:latest"

To register the number, follow the official guide: https://github.com/bbernhard/s…ob/master/doc/EXAMPLES.md

Once this is done, we can create our script

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

Then paste this content into the file:

#!/bin/bash

sender="<sender number>"
recipiant="<receiver number>"
contenttype="Content-Type: application/json"
signal_msg_url="http://127.0.0.1:8080/v2/send"

# The message file needs to altered as the new line literals does not work directly. More, monit adds a \ to the hostname. This needs to changed, too.
sed -E -i -e ':a;N;$!ba;s/\r{0,1}\n/\\n/g' -e 's|\\'"${HOSTNAME}"'|'"${HOSTNAME}"'|g' "$OMV_NOTIFICATION_MESSAGE_FILE"


content=$(cat "$OMV_NOTIFICATION_MESSAGE_FILE")

# If you want to send the message to more than 1 person, then add the number of the repcipiants in [] separated by ","
generate_msg_data()
{
  cat <<EOF
{"message": "${content}", "number": "$sender", "recipients": ["$recipiant"]}
EOF
}

curl -X POST -H "$contenttype" -d "$(generate_msg_data)" "$signal_msg_url"

Save the file

Then the script needs to be made executable:

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

Quote from nrand

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: https://github.com/OpenMediaVa…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.

Hi,

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 am now using another approach. I am using signal-cli-rest-api to wrap a REST API around the signal-cli commands. This seems to work.

Yes the script can be executed. Permission for this file is 755.

Hi,

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:

#!/bin/bash

sender="+49xxxxxx"
recipiant="+49yyyyyyy"

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_SUBJECT=test
export OMV_NOTIFICATION_DATE=testdate
export OMV_NOTIFICATION_MESSAGE_FILE=/tmp/testfile 

/usr/share/openmediavault/notification/sink.d/./20signal

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

Hi,

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

root@xxxxxxxxx:~# df -h 
Filesystem                              Size  Used Avail Use% Mounted on
udev                                    7.8G     0  7.8G   0% /dev
tmpfs                                   1.6G   12M  1.6G   1% /run
/dev/mapper/xxxxxxxx--vg-root                32G   10G   21G  34% /
tmpfs                                   7.8G     0  7.8G   0% /dev/shm
tmpfs                                   5.0M     0  5.0M   0% /run/lock
tmpfs                                   7.8G     0  7.8G   0% /sys/fs/cgroup
tmpfs                                   7.8G     0  7.8G   0% /tmp
/dev/sda2                               237M   92M  133M  41% /boot
/dev/sda1                               511M  510M  1.9M 100% /boot/efi
folder2ram                              7.8G   29M  7.8G   1% /var/log
folder2ram                              7.8G     0  7.8G   0% /var/tmp
folder2ram                              7.8G  880K  7.8G   1% /var/lib/openmediavault/rrd
folder2ram                              7.8G  1.2M  7.8G   1% /var/spool
folder2ram                              7.8G   22M  7.8G   1% /var/lib/rrdcached
folder2ram                              7.8G  4.0K  7.8G   1% /var/lib/monit
folder2ram                              7.8G  1.3M  7.8G   1% /var/cache/samba

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?

I'm also thinking about to move my Home Assistant installation from a Raspi to my OMV5 using the new official supervised installation (https://github.com/home-assistant/supervised-installer)

tbl: You seems to have some experience. Does it make any problems? The instructions itself seems to be only supported if anything else runs on the host system.

Quote from Altecice

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

Code

Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export SHELL=/bin/sh; sudo --shell --non-interactive --user=root -- /usr/sbin/omv-snapraid-diff 2>&1' with exit code '2': /usr/sbin/omv-snapraid-diff: line 490: syntax error near unexpected token `else'
/usr/sbin/omv-snapraid-diff: line 490: `else' in /usr/share/openmediavault/engined/rpc/cron.inc:175
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMVRpcServiceCron->{closure}('/tmp/bgstatus4v...', '/tmp/bgoutputiS...')
#1 /usr/share/openmediavault/engined/rpc/cron.inc(179): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#2 [internal function]: OMVRpcServiceCron->execute(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('execute', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Cron', 'execute', Array, Array, 1)
#6 {main

Display More

Same error here.

Can you try to add func.getattr=newe in the mount options of mergerfs partition?

Problem solved. The new mergerfs seems to have an issue with acl list. Needed to add the plex to users group. now works.

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

Quote from gderf

OMV 4.x is Stretch based, not Jessie.

sorry my mistake ...

Quote from gderf

I am running OMV 4.x and Plex in a docker. I too just recently upgraded to mergerfs 2.26.2~debian-stretch. I have no problems with Plex and this release of mergerfs.

also after a reboot? My problems started after reboot ...

Hi,

I am running OMV Server (latest OMV4 version) with the most recent version of Plex Media Server (version 1.15.4.994, 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?

This is weird. I have a scheduled task which starts a rsync backup job. When the job is done, it sends me a mail that tells me what files are transffered. Yesterday I got the mail, but no telegram message.

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?

Thanks it is working.

Hi all,

I just realized that the syncthing plugin seems to miss the inotify extension? Do I have to start them manually?

Best!

ah ok Thanks for the quick answer.

Hi,

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,