Droid999

Found nullmailer - and it's indeed working, as is the email notifications for Deluge - I had mistyped the smtp port. Thanks

Hi - great docker - thanks for your work on it. Is it possible to include some sort of email package in the image - something like nullmailer or sendmail. The deluge notifications don't seem to work via email - and I've written a script to run on completion -but it needs some sort of email transport program. I ran pacman -S nullmailer - but it failed to install. Thanks. :: Proceed with installation? [Y/n] y warning: no /var/cache/pacman/pkg/ cache exists, creating... :: Retrieving packages... nullmailer-2.2-3-x86_64 85.1 KiB 22.2 KiB/s 00:04 [##################################] 100% error: failed retrieving file 'nullmailer-2.2-3-x86_64.pkg.tar.zst' from ftp.sh.cvut.cz : Protocol "rsync" not supported or disabled in libcurl (1/1) checking keys in keyring [##################################] 100% (1/1) checking package integrity [##################################] 100% (1/1) loading package files [##################################] 100% (1/1) checking for file conflicts [##################################] 100% (1/1) checking available disk space [##################################] 100% :: Processing package changes... (1/1) installing nullmailer [##################################] 100% :: Running post-transaction hooks... (1/4) Creating system user accounts... Creating group 'nullmail' with GID 984. Creating user 'nullmail' (nullmailer MTA) with UID 984 and GID 984. (2/4) Reloading system manager configuration... Skipped: Current root is not booted. (3/4) Creating temporary files... /usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to replace specifiers in '/var/log/journal/%m': Package not installed /usr/lib/tmpfiles.d/systemd.conf:23: Failed to replace specifiers in '/run/log/journal/%m': Package not installed /usr/lib/tmpfiles.d/systemd.conf:25: Failed to replace specifiers in '/run/log/journal/%m': Package not installed /usr/lib/tmpfiles.d/systemd.conf:26: Failed to replace specifiers in '/run/log/journal/%m/*.journal*': Package not installed /usr/lib/tmpfiles.d/systemd.conf:29: Failed to replace specifiers in '/var/log/journal/%m': Package not installed /usr/lib/tmpfiles.d/systemd.conf:30: Failed to replace specifiers in '/var/log/journal/%m/system.journal': Package not installed /usr/lib/tmpfiles.d/systemd.conf:32: Failed to replace specifiers in '/var/log/journal/%m': Package not installed /usr/lib/tmpfiles.d/systemd.conf:33: Failed to replace specifiers in '/var/log/journal/%m/system.journal': Package not installed (4/4) Arming ConditionNeedsUpdate...

SOLVED: So the "Path" setting for logs isn't a directory path - it's the name of a file. By setting the variable to /log/file.log - the app now writes to that file - not creating logfiles under that directory as I assumed it was going to do. autobrr - Unable to write log file. What are the permissions required to allow autobrr to write out logfiles and files. I have /logs mapped to /mnt/user/x/logs with permissions drwxrwxrwx nobody:users - but the docker logfile shows: zerolog: could not write event: can't rename log file: rename /logs /logs-2023-03-09T01-02-54.677: permission denied The directory /mnt/user/appdata/ shows: drwxr-xr-x 1 nobody users 98 Mar 9 11:49 autobrr/ Any ideas on why the docker can't write logfiles. The docker setting has /logs set to read/write, slave - the same setting as for appdata.

Thanks for the reply. In this instance, a docker won't work - rdiff-backup doesn't appear to have an option to specify a port to run on - so the docker on unraid can only be accessed via the unraid address and port - so this won't work. Spinning up a VM just to run one command seems a little excessive, plus the VM will need to have all the shares mounted so rdiff-backup can see them. In the end, I just ended up NFS mounting the shares from unraid to the remote NAS and doing a rdiff-backup locally. Cheers

Hi I have a offsite NAS that will be my backup server - it reaches out and pulls data from the unraid box using rdiff-backup. However, both machine require the rdiff-backup program installed - I got it running on the remote machine, but have hit a wall trying to get it onto the unraid box. root@unraid:~# pip3 install rdiff-backup Collecting rdiff-backup Using cached rdiff-backup-2.0.5.tar.gz (456 kB) Requirement already satisfied: setuptools in /usr/lib64/python3.9/site-packages (from rdiff-backup) (63.2.0) Using legacy 'setup.py install' for rdiff-backup, since package 'wheel' is not installed. Installing collected packages: rdiff-backup Running setup.py install for rdiff-backup ... error ERROR: Command errored out with exit status 1: command: /usr/bin/python3 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-cmxy5xl5/rdiff-backup_985e6dfcedc44e439cdd253ac4d5537f/setup.py'"'"'; __file__='"'"'/tmp/pip-install-cmxy5xl5/rdiff-backup_985e6dfcedc44e439cdd253ac4d5537f/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-yiw55yzo/install-record.txt --single-version-externally-managed --compile --install-headers /usr/include/python3.9/rdiff-backup cwd: /tmp/pip-install-cmxy5xl5/rdiff-backup_985e6dfcedc44e439cdd253ac4d5537f/ Complete output (59 lines): /usr/lib64/python3.9/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer. warnings.warn( WARNING: The wheel package is not available. WARNING: The wheel package is not available. WARNING: The wheel package is not available. WARNING: The wheel package is not available. WARNING: The wheel package is not available. running install /usr/lib64/python3.9/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( running build running build_py running build_templates templating tools/rdiff-backup.spec.template -> build/rdiff-backup.spec creating build templating tools/rdiff-backup.spec.template-fedora -> build/rdiff-backup.fedora.spec templating docs/rdiff-backup.1 -> build/rdiff-backup.1 templating docs/rdiff-backup-statistics.1 -> build/rdiff-backup-statistics.1 creating build/lib.linux-x86_64-cpython-39 creating build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/win_acls.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/increment.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/Security.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/log.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/connection.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/librsync.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/manage.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/eas_acls.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/TempFile.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/longname.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/Rdiff.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/Globals.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/robust.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/selection.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/restore.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/backup.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/rorpiter.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/iterfile.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/SetConnections.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/user_group.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/Time.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/regress.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/FilenameMapping.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/__init__.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/metadata.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/Main.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/Hardlink.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/fs_abilities.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/hash.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/statistics.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/rpath.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup copying src/rdiff_backup/compare.py -> build/lib.linux-x86_64-cpython-39/rdiff_backup running build_ext building 'rdiff_backup.C' extension creating build/temp.linux-x86_64-cpython-39 creating build/temp.linux-x86_64-cpython-39/src gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/usr/include/python3.9 -c src/cmodule.c -o build/temp.linux-x86_64-cpython-39/src/cmodule.o /usr/libexec/gcc/x86_64-slackware-linux/9.2.0/cc1: error while loading shared libraries: libisl.so.22: cannot open shared object file: No such file or directory error: command '/usr/bin/gcc' failed with exit code 1 ---------------------------------------- ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import io, os, sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-cmxy5xl5/rdiff-backup_985e6dfcedc44e439cdd253ac4d5537f/setup.py'"'"'; __file__='"'"'/tmp/pip-install-cmxy5xl5/rdiff-backup_985e6dfcedc44e439cdd253ac4d5537f/setup.py'"'"';f = getattr(tokenize, '"'"'open'"'"', open)(__file__) if os.path.exists(__file__) else io.StringIO('"'"'from setuptools import setup; setup()'"'"');code = f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-yiw55yzo/install-record.txt --single-version-externally-managed --compile --install-headers /usr/include/python3.9/rdiff-backup Check the logs for full command output. root@unraid:~# ls -l Clearly missing the libisl.so library file - but I can't find it anywhere. How can I install either rdiff-backup or the missing file? Thanks.

Solved. The plugins page is checking network connectivity by calling http://www.msftncsi.com/ncsi.txt. This is flagged as a Windows 10 Telemetry site in my proxy filter, and therefore blocked. Unraid thinks there is no network connectivity, and doesn't attempt to get the status of plugins. This functionality is within the file /usr/local/emhttp/plugins/dynamix.plugin.manager/include/PluginHelpers.php function check_plugin($arg, &$ncsi) { // Get network connection status indicator (NCSI) if ($ncsi===null) passthru("wget --quiet --spider --timeout=10 --tries=1 http://www.msftncsi.com/ncsi.txt",$ncsi); return $ncsi===0 ? plugin('check',$arg) : false; } By whitelisting the msftncsi.com domain, the Plugins page displays the Status correctly.

Ok - found what's causing it. I'm running a Squid Proxy, when this is off then the plugins page updates correctly - when it's on - the Status is Unknown. There is a setting to not cache certain domains - anyone know which domain the plugins page queries to get its updates?

@Squid - Any ideas on how to resolve this? Thanks.

Apps works no problems - screen shot attached for Statistics.

For the past few weeks all my plugins and the Update OS page have a status of "Unknown". I have tried a reboot with no change. I have also checked that the box has working Internet, which it has. I also got my weekly email yesterday telling me all the plugins that require updating. Running 6.8.2. Any idea on how to solve this ? or is there a command line to upgrade plugins via the terminal ?

I had to do amd_iommu=off to get it to work properly. Now booting with all disks available using 6.7.1-rc1 01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe SATA 6Gb/s Controller (rev 11)