Testing 0.7.0-beta

[aakerbeere]

Maybe the setup is unsuported and i don't know if the issues relate to this:
Running "Debian GNU/Linux 12.8 (bookworm)" on "Machine: Type: ARM System: Raspberry Pi 4 Model B Rev 1.4", "Memory: RAM: total: 7.69 GiB used: 6.27 GiB (81.5%)", "ext4", default partitioning.

Upgrading:
"--- RBK0114I: Besuche https://www.linux-tips-and-tricks.de/de/versionshistorie/ um die Änderungen in der neuen Version kennenzulernen."
The message leads to "https://www.linux-tips-and-tricks.de/de/versionshistorie/" for the versions history. The URL is deprecated. Should be "https://github.com/framps/raspiBackup/releases".

A error shows up where merging previous and new versions of the "conf"-file:
--- RBK0240I: Aktuelle Konfiguration /usr/local/etc/raspiBackup.conf wird in /usr/local/etc/raspiBackup.conf.bak gesichert.
/usr/local/bin/raspiBackup.sh: Zeile 2472: ((: raspiBackup.conf.save.1: Syntaxfehler: Ungültiger arithmetischer Operator. (Fehlerverursachendes Zeichen ist ".conf.save.1").
--- RBK0244I: Zusammengefügte Konfiguration /usr/local/etc/raspiBackup.conf.merged nach /usr/local/etc/raspiBackup.conf kopiert und aktiviert.

Testing backup:
Scheduled nightly task to QNAP on local Network, triggered by timer daemon.

1. attempt:
   The first run of backup with this beta took extremly long (~16h) to finish compared to previous tasks with predecessor (~2h). A eMail message was composed and sent.

2. attempt:
   Did not run:
   sudo systemctl status raspiBackup.service
   × raspiBackup.service - Run raspiBackup
   Loaded: loaded (/etc/systemd/system/raspiBackup.service; static)
   Active: failed (Result: exit-code) since Sat 2024-11-30 01:12:20 CET; 11h ago
   Duration: 2min 19.905s
   TriggeredBy: ● raspiBackup.timer
   Main PID: 28770 (code=exited, status=131)
   CPU: 3.128s

Nov 30 01:12:17 rpi4nc sudo[29375]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Nov 30 01:12:17 rpi4nc raspiBackup.sh[28850]: Job for avahi-daemon.service failed because the control process exited with error code.
Nov 30 01:12:17 rpi4nc raspiBackup.sh[28850]: See "systemctl status avahi-daemon.service" and "journalctl -xeu avahi-daemon.service" for details.
Nov 30 01:12:19 rpi4nc sudo[29375]: pam_unix(sudo:session): session closed for user root
Nov 30 01:12:20 rpi4nc raspiBackup[29953]: Stopped 0.7.0-beta (2767035). rc 131
Nov 30 01:12:20 rpi4nc raspiBackup.sh[28850]: msmtp: cannot locate host mail.gmx.net: Temporary failure in name resolution
Nov 30 01:12:20 rpi4nc raspiBackup.sh[28850]: msmtp: could not send mail (account default from /root/.msmtprc)
Nov 30 01:12:20 rpi4nc systemd[1]: raspiBackup.service: Main process exited, code=exited, status=131/n/a
Nov 30 01:12:20 rpi4nc systemd[1]: raspiBackup.service: Failed with result 'exit-code'.
Nov 30 01:12:20 rpi4nc systemd[1]: raspiBackup.service: Consumed 3.128s CPU time.

journalctl -xeu avahi-daemon.service:
░░ The job identifier is 24525.
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: Process 23599 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: Found user 'avahi' (UID 108) and group 'avahi' (GID 113).
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: Successfully dropped root privileges.
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: avahi-daemon 0.8 starting up.
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: dbus_bus_get_private(): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expir>
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: WARNING: Failed to contact D-Bus daemon.
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: avahi-daemon 0.8 exiting.
Nov 30 01:12:17 rpi4nc systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/EXCEPTION

sudo systemctl status avahi-daemon.service
× avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Sat 2024-11-30 01:12:17 CET; 11h ago
Duration: 4h 32min 33.061s
TriggeredBy: ● avahi-daemon.socket
Main PID: 29377 (code=exited, status=255/EXCEPTION)
Status: "avahi-daemon 0.8 exiting."
CPU: 14ms

Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: Found user 'avahi' (UID 108) and group 'avahi' (GID 113).
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: Successfully dropped root privileges.
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: avahi-daemon 0.8 starting up.
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: dbus_bus_get_private(): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expir>
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: WARNING: Failed to contact D-Bus daemon.
Nov 30 01:12:17 rpi4nc avahi-daemon[29377]: avahi-daemon 0.8 exiting.
Nov 30 01:12:17 rpi4nc systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/EXCEPTION
Nov 30 01:12:17 rpi4nc systemd[1]: avahi-daemon.service: Failed with result 'exit-code'.
Nov 30 01:12:17 rpi4nc systemd[1]: Failed to start avahi-daemon.service - Avahi mDNS/DNS-SD Stack.

sudo apt install libnss-mdns
sudo apt install avahi-autoipd

3. attempt
   3.5h. Successful. Ran as expected. A mail message was created and sent.

4. attempt
   4h. Successful. Ran as expected. A mail message was created and sent.

5. attempt
   4h. Successful. Ran as expected. A mail message was created and sent.

6. attempt
   4h. Successful. Ran as expected. A mail message was created and sent.

... and so on

Testing restore:
Starting Backup-OS from SD-Card. Updating to the most recent condition.
sudo apt install libnss-mdns
sudo apt install avahi-autoipd
Starting restore
Restore successful. No issues.

Reverting productive raspiBackup on SSD and backup OS on SD-Card to previously used version using -V

[framps]

Thank you very much for testing the beta 👍

The message leads to "https://www.linux-tips-and-tricks.de/de/versionshistorie/" for the versions history. The URL is deprecated. Should be "https://github.com/framps/raspiBackup/releases".

Good catch. Fixed 😉

A error shows up where merging previous and new versions of the "conf"-file:
--- RBK0240I: Aktuelle Konfiguration /usr/local/etc/raspiBackup.conf wird in /usr/local/etc/raspiBackup.conf.bak gesichert.
/usr/local/bin/raspiBackup.sh: Zeile 2472: ((: raspiBackup.conf.save.1: Syntaxfehler: Ungültiger arithmetischer Operator. (Fehlerverursachendes Zeichen ist ".conf.save.1").
--- RBK0244I: Zusammengefügte Konfiguration /usr/local/etc/raspiBackup.conf.merged nach /usr/local/etc/raspiBackup.conf kopiert und aktiviert.

I don't expect you kept the log because in line 2472 there is no .save file used. Did you saved config files in this directory and gave them .save.1 extension? raspiBackup doesn't use these extensions. Maybe you can show the contents of /usr//local/etc ?

Did you upgrade from 0.6.9 or 0.6.9.1 or an earlier version?

1. The first run of backup with this beta took extremly long (~16h) to finish compared to previous tasks with predecessor (~2h).

That's expected because now the os name is included in the backup directory name the first backup is a full rsync backup. All following backups are delta backups and will terminate much faster.

Restore successful. No issues.

Great. Thank you again for your test.

Maybe you find some time to test the new feature to restore not all partitions and use option -00 to execute a rsync restore to an already existing and populated partition? The new feature is documented here

[aakerbeere]

thx @framps for spending time

I don't expect you kept the log

Don't know. I expect you're talking about the log created during the upgrade. If you tell me where to look for, maybe i find it.

Did you saved config files in this directory and gave them .save.1 extension?

Maybe. Don't remember.

show the contents of

ls /usr/local/etc clamav raspiBackup.0.6.7.conf raspiBackup.conf raspiBackup.conf..bak raspiBackup.conf.bak raspiBackup.conf.new raspiBackup.conf.save raspiBackup.conf.save.1

Did you upgrade from

Upgrade has been done from 0.6.9

test the new feature

Sounds interesting. But rather than have faster restore i would prefere to have faster backup. But i will report if i do.

[framps]

ls /usr/local/etc clamav raspiBackup.0.6.7.conf raspiBackup.conf raspiBackup.conf..bak raspiBackup.conf.bak raspiBackup.conf.new raspiBackup.conf.save raspiBackup.conf.save.1

Ok. You upgraded from 0.6.7. The upgrade procedure of the config changed a little bit. At the end you should have only raspibackup.conf, raspibackup.conf.bak and maybe raspibackup.conf.n.bak where n is a number.

[aakerbeere]

@framps

I found a file "raspiBackup.log.upd" that seems to be the file having been created during the upgrade. Do you want me to upload it?

[framps]

I have no idea where this log file comes from. Looks like it was created in some earlier raspiBackup version during update. The update process changed a little bit. At least it's not created by latest release of raspiBackup. If you execute sudo raspiBakup -U you will find raspiBackup.log in you home directory. That's what I need.

[aakerbeere]

Thats where i found it. I probably renamed it myself to make sure not to be overwritten somehow. It recorded the commandline paramter "-U" and date and timestamps reflect those when i performed the upgrade. Have a look. I renamed it because of filename suffix not allowed.
raspiBackup.log.txt

[framps]

That's the log I need 👍 Hope I get some idea what went wrong.

[framps]

I found the root cause: your private backup .save and save.1. I will make the code more robust against files not created from raspiBackup.

Thank you very much for your help on this 👍