Works on Orange Pi 5 Plus running Ubuntu 24.04

[hearthmatt]

This isn't a question but I thought it may be useful.

Having successfully run raspiBackup on my RaspberryPi 4 to a Synology NAS I thought I would try it on my OrangePi 5 Plus with Ubuntu 24.04. From the command line it works perfectly with the --unsupportedEnvironment switch. However it fails using the Regular Backup option from raspiBackupInstallUI with what looks like an authority problem accessing /run/user/1000/docs and /run/user/1000/gvfs.

I overcame this issue by running it from the system-wide crontab in /etc/crontab and specifying "root" in the user name.

[framps]

Thank you very much for sharing your experience. I know raspiBackup is used on unsupported environments successfully by a lot of folks but as long as I cannot test the environment I don't support these environments officially. But that's why I added the --unsupportedEnvironment option 😉

However it fails using the Regular Backup option from raspiBackupInstallUI with what looks like an authority problem accessing /run/user/1000/docs and /run/user/1000/gvfs.

Jut to make sure I get you: If you invoke raspiBackup on the command line everything works fine. If systemd is used to start raspiBackup you get some errors. Or did yo install raspiBackup to use crond?

Your workaround is to invoke raspiBackup via cron as user root. You may try to install raspiBackup and have raspiBackup to use crond. If you use option -t crond in the raspiBackupInstallUI invocation crond is used by raspiBackup instead of systemd.

What's the error you get when you use the raspiBackup way to invoke raspiBackup scheduled?

[hearthmatt]

Yes, if I invoke the backup via the command line using: sudo raspiBackup --unsupportedEnvironment then it works fine. If it runs via the default install option systemd then it fails. I didn't know about the -t crond option.

The log with the failure has been overwritten so I'll try to generate a new one.

[framps]

I didn't know about the -t crond option.

A long time crond was used by raspiBackup. But when I added systemd support and made this the default I still kept the crond support for backward compatibility reasons. See Invoke installer without menus from the commandline. You even can switch back and forth but you loose the scheduling information.

I'll try to generate a new one.

Thank you very much. I just want to check whether there is a general issue or an issue with Ubuntu 24.04 because systemd services are running with root and that's what you do with crond as a workaround. I'm wondering why you get an error with systemd but not with crond.

[hearthmatt]

I have attached:

1. Output from the raspiBackup.service whilst running and after the failure
2. raspiBackup.log
3. raspiBackup.msg - not detailed though
   raspiBackup_service.txt
   raspiBackup.log
   raspiBackup.msg.txt

Note that for the working crontab setup I used the system crontab in /etc/crontab and specified root as the user.

[framps]

Thank you very much for the logs.

I cannot promise I fix this issue but if it's a low hanging fruit I will 😉

That's what I get on my Ubuntu on a Raspberry4:

ubuntu@ubuntu-24-04-desktop64:~$ mount | grep sda
/dev/sda2 on / type ext4 (rw,relatime,discard,stripe=8191)
/dev/sda2 on /var/snap/firefox/common/host-hunspell type ext4 (ro,noexec,noatime,discard,stripe=8191)
/dev/sda1 on /boot/firmware type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)

That's what I see in your debug log:

20240528-144551 DBG 6394:                  /dev/nvme0n1p1 on / type ext4 (rw,relatime)
20240528-144551 DBG 6394:                  /dev/nvme0n1p1 on /var/snap/firefox/common/host-hunspell type ext4 (ro,noexec,noatime)

There is just one partition instead of two on a Raspberry.

raspiBackup fails because it's not detecting the bootpartition. If there exists no bootpartition it's expected to find cmdline.txt on either find /boot or /boot/firmware which doesn't exist on your system. It seems this test is a bit too strong and I should relax the test.

Could you please show me the result of following commands on your system and post the result?

for d in /boot /boot/firmware; do [ -d "$d" ] && echo "$d exists"; done
sudo find / -name cmdline.txt

[hearthmatt]

I get the following:

$ for d in /boot /boot/firmware; do [ -d "$d" ] && echo "$d exists"; done
/boot exists
$ sudo find / -name cmdline.txt
find: ‘/proc/504749’: No such file or directory
find: ‘/run/user/1000/doc’: Permission denied
find: ‘/run/user/1000/gvfs’: Permission denied

[framps]

Ok. Thank you very much. /boot exists on your system. But no cmdline.txt which is expected right now by raspiBackup.

You don't use the official Ubuntu image published for Raspberries.

Where downloaded you the image from (URL please 😉) Just to get an idea whether it's worth to add some code to enable raspiBackup to accept Ubuntu without cmdline.txt. I then will create a branch for you to test the mod 😉

[hearthmatt]

The image was from here: https://joshua-riek.github.io/ubuntu-rockchip-download/boards/orangepi-5-plus.html

[framps]

It's interesting to see there is some guy who publishes Ubuntu 24-02 images for various platforms.

I'm going to create a less restrictive branch for you now to test if it works on an Orange HW. But not today any more ... it's too late. Will keep you updated.

[hearthmatt]

Fyi, its the most stable Ubuntu image I've used so far for the Orange Pi. I've had lots of issues even with the images from the manufacturer.

[framps]

Here we are 😉

Please execute

curl -s https://raw.githubusercontent.com/framps/raspiBackup/master/scripts/raspiBackupDownloadFromGit.sh | bash -s -- orange

to download the updated code and try whether it now works with systemd. If not please provide the debug log again.

[hearthmatt]

Thanks I'll be able to give it a try early next week.

[framps]

Thank you very much. Take your time ...

[hearthmatt]

Hi, it ran OK from the command line but failed via systemd.

Got the following from the systemd service:

sudo systemctl status raspiBackup
[sudo] password for :
× raspiBackup.service - Creation of a Raspberry backup with raspiBackup
Loaded: loaded (/etc/systemd/system/raspiBackup.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-06-03 16:10:28 EDT; 2h 26min ago
Duration: 1h 54min 26.824s
TriggeredBy: ● raspiBackup.timer
Process: 1028950 ExecStart=/home//raspiBackup.sh --unsupportedEnvironment (code=exited, status=102)
Main PID: 1028950 (code=exited, status=102)
CPU: 1min 45.093s

Jun 03 14:16:01 orangepi systemd[1]: Started raspiBackup.service - Creation of a Raspberry backup with raspiBackup.
Jun 03 16:10:15 orangepi raspiBackup.sh[1029030]: find: './run/user/1000/doc': Permission denied
Jun 03 16:10:15 orangepi raspiBackup.sh[1029030]: find: './run/user/1000/gvfs': Permission denied
Jun 03 16:10:15 orangepi sSMTP[1037527]: Creating SSL connection to host
Jun 03 16:10:26 orangepi sSMTP[1037527]: SSL connection using ECDHE_RSA_AES_256_GCM_SHA384
Jun 03 16:10:28 orangepi sSMTP[1037527]: Sent mail for root@orangepi (221 2.0.0 closing connection 6a1803df08f44-6aee168f08fsm28607426d6.53 ->
Jun 03 16:10:28 orangepi systemd[1]: raspiBackup.service: Main process exited, code=exited, status=102/n/a
Jun 03 16:10:28 orangepi systemd[1]: raspiBackup.service: Failed with result 'exit-code'.
Jun 03 16:10:28 orangepi systemd[1]: raspiBackup.service: Consumed 1min 45.093s CPU time, 478.6M memory peak.

This is the log:
[raspiBackup.log](https://github.com/user-attachments/files/15540630/raspiBackup.log)

raspiBackup.msg contents:

cat raspiBackup.msg
!!! RBK0269W: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
!!! RBK0268W: @@@ Unsupported environment @@@
!!! RBK0269W: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
--- RBK0009I: orangepi: raspiBackup.sh V0.6.9.1-orange - 2024-05-30 (829edd8) started at Mon Jun  3 14:16:02 EDT 2024.
--- RBK0116I: Using config file /usr/local/etc/raspiBackup.conf.
??? RBK0142E: Unable to detect boot device. Please report this issue on https://github.com/framps/raspiBackup/issues or https://www.linux-tips-and-tricks.de/en/rmessages
--- RBK0033I: Please wait until cleanup has finished.
--- RBK0043I: Removing incomplete backup in /orangepibackup/orangepi/orangepi-rsync-backup-20240603-141601. This may take some time. Please be patient.
??? RBK0005E: Backup failed. Check previous error messages for details.
--- RBK0010I: orangepi: raspiBackup.sh V0.6.9.1-orange - 2024-05-30 (829edd8) stopped at Mon Jun  3 16:10:15 EDT 2024 with rc 102.
--- RBK0167I: Sending email.
--- RBK0026I: Debug logfile saved in /root/raspiBackup.log.

[framps]

😢 I was confident it will work now for you. Because of this I didn't add any debug statements and unfortunately don't know why my fix doesn't work 😢

I'm AFH the next week and not able to work on this. I will check and provide a version with more debug statements when I'm back.

This proves it was a valid decision to add the --unsupportedEnvironment option. If you have the HW/SW handy it's quite easy to verify everything works as expected - but otherwise you have to use debug logs which is much more time consuming.

Don't worry about this - I will give it another shot and hope I will locate the root cause of your issue. But if I will fail again I will stop - I handle only low hanging fruits if there is an --unsupportedEnvironment . I hope you understand this 😉

[hearthmatt]

No problem, I am a retired software developer and I know what a PIA chasing obscure bugs can be without the full picture. I am just happy that I have found something that works for me and it's easy to set up in crontab. I'm only using the OrangePi because I couldn't get hold of a raspberryPi during the shortage. Thank you for trying.

[framps]

I found and fixed the coding bug. Please try again.

[hearthmatt]

Hi,This works from the command line. I’ll try it from systemctl tonight. On Jun 14, 2024, at 2:36 PM, framp ***@***.***> wrote: I found and fixed the coding bug. Please try again. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[framps]

Keep in mind you have to add the option --unsupportedEnvironment in /etc/systemd/system/raspiBackup.service ExecStart line 😉

[hearthmatt]

Success! I've attached the log file if you need to check anything.

Thank you for doing this, I appreciate your efforts.

raspiBackup.log

sudo systemctl status raspiBackup
○ raspiBackup.service - Creation of a Raspberry backup with raspiBackup
Loaded: loaded (/etc/systemd/system/raspiBackup.service; enabled; preset: enabled)
Active: inactive (dead) since Sun 2024-06-16 21:34:41 EDT; 27min ago
Duration: 4h 8min 58.527s
TriggeredBy: ● raspiBackup.timer
Process: 1588632 ExecStart=/home/matthew/raspiBackup.sh --unsupportedEnvironment (code=exited, status=0/SUCCESS)
Main PID: 1588632 (code=exited, status=0/SUCCESS)
CPU: 7min 8.579s

Jun 16 20:09:24 orangepi raspiBackup.sh[1588712]: Stopping 'snapd.service', but its triggering units are still active:
Jun 16 20:09:24 orangepi raspiBackup.sh[1588712]: snapd.socket
Jun 16 20:09:39 orangepi raspiBackup.sh[1588712]: Stopping 'docker.service', but its triggering units are still active:
Jun 16 20:09:39 orangepi raspiBackup.sh[1588712]: docker.socket
Jun 16 21:34:27 orangepi raspiBackup[1607397]: Stopped 0.6.9.1-orange (88c16ec). rc 0
Jun 16 21:34:28 orangepi sSMTP[1607450]: Creating SSL connection to host
Jun 16 21:34:38 orangepi sSMTP[1607450]: SSL connection using ECDHE_RSA_AES_256_GCM_SHA384
Jun 16 21:34:40 orangepi sSMTP[1607450]: Sent mail for root@orangepi (221 2.0.0 closing connection d75a77b69052e-4421772802fsm33775491cf.58 - gsmtp) uid=0 usernam>
Jun 16 21:34:41 orangepi systemd[1]: raspiBackup.service: Deactivated successfully.
Jun 16 21:34:41 orangepi systemd[1]: raspiBackup.service: Consumed 7min 8.579s CPU time, 528.3M memory peak.

[framps]

Great it works now. The change will be available in next release of raspiBackup.