Roi

Ehm... No... Thank you! Temporary fix applied...

I am seeing this for two days now. The container seems to be updates. So this must be a new problem. borgmatic 1.7.5 apprise 1.2.0 crond: crond (busybox 1.35.0) started, log level 8 crond: USER root pid 14 cmd borgmatic -c /etc/borgmatic.d/config.yaml 2>&1 Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/borg/archiver.py", line 38, in <module> from . import helpers File "/usr/local/lib/python3.10/site-packages/borg/helpers/__init__.py", line 9, in <module> from .checks import * # NOQA File "/usr/local/lib/python3.10/site-packages/borg/helpers/checks.py", line 4, in <module> from .errors import Error File "/usr/local/lib/python3.10/site-packages/borg/helpers/errors.py", line 3, in <module> import borg.crypto.low_level ImportError: Error loading shared library libcrypto.so.1.1: No such file or directory (needed by /usr/local/lib/python3.10/site-packages/borg/crypto/low_level.cpython-310-x86_64-linux-gnu.so) /etc/borgmatic.d/config.yaml: Error getting local Borg version Command '('borg', '--version')' returned non-zero exit status 2. /etc/borgmatic.d/config.yaml: Error running configuration file summary: /etc/borgmatic.d/config.yaml: Error running configuration file /etc/borgmatic.d/config.yaml: Error getting local Borg version Command '('borg', '--version')' returned non-zero exit status 2. Need some help? https://torsion.org/borgmatic/#issues

Yes. But I cannot say if it is the Unraid upgrade or the reboot since migrating from NerdPack to NerdTools.

I run 6.11.2 since today. NerdTools ist the most current version from November 1st. Yesterday borgbackup still worked on 6.11.1 - maybe there was also another dependency which supplied libffi.so.7 here, too?

Well, borgbackup is included and does not need to be included. It was also included in NerdPack. But now it does not work anymore. I think that is a different topic then.

Well, borgbackup and borgmatic is a difference. In NerdTools you can install borgbackup, which provides the "borg" binary.

I am also having the same problem with borgbackup and libffi.so.7 and will follow here, too, as borgbackup is very important for me as well.

Ah wow thank you. That did not come to my attention, yet. Great! So I can use borgbackup in the meantime like before. As described it would be better to have borgbackup inside a Docker container for security reasons, so I would like to stick to my suggestion adding an SSH daemon and borgbackup to this container.

Hello, I want to bring this issue up again. I looked into it today and still did not find a solution which works for me. So no settings inside CrushFTP and also no option for the Docker container (as I am not the biggest Docker user this also can be PEBCAK ). Can someone help? Thank you and regards, Roi

Hello, as Nerdpack is gone I wanted to ask if it is possible to add borgbackup and an SSH server to this Docker. I used the borgbackup package from Nerdpack and the system SSH server to offer a Borgbackupserver to some of my servers on the internet. Unfortunately with Nerdpack gone and especially because this was not the best idea from the start using the system SSH server itself I am looking for a better solution here. Maybe @stridemat questions/issues are heading into the same direction. Regards, Roi

Mit der 6.10.2 funktioniert der Login nun... Wobei ich im Changelog nichts passendes finde, was dazu gefixt wurde.

It works with 6.10.2 - although I cannot see a fix matching my problem in the changelog.

Here you are. :-) It is 6.9.2 anonymized - as I would to update and restart the machine again which I can only do if nobody from the family is around. I use https://172.27.0.5 to login. But I did not USE_SSL="yes" until today, so I had the problem with http and https. I also tried to use the internal DNS name which did not work, too. The error message was, that either username or password is invalid. I also saw a message in syslog, unsuccessful login or something, I do not recall the exact phrase. But I found it in the php scripts for the website. Oh and I also changed the root password to a simple password "pass" which did also not work. basis-diagnostics-20220523-2055.zip

Went back to 6.9.2 and it worked right away. I was using USE_SSL="no", so this was not the problem here.

Okay, war wirklich einfach. Bin nun wieder zurück auf 6.9.2 und konnte mich direkt einloggen. USE_SSL war bei mir übrigens auf "no". Zertifikat löschen oder auf "yes" stellen hat auch nichts geholfen. Da ist was weird... Schade... Und wie gesagt, mit meiner anderen Kiste geht's.