Comments (14)
I was able to reproduces your issue. Would be helpful if you let me know which code level you use. Please show the output of raspiBackupInstallUI -h
.
from raspibackup.
I just fixed the issue. Please grab the latest installer code with
sudo raspiBackupInstallUI -U
Then you should get following version information:
framp@majestix:~/home/framp$ raspiBackupInstallUI --version
raspiBackupInstallUI.sh 0.4.8.1, 2024-05-12/15:43:10 - 225f671
Please verify the fix and then close the issue if everything is OK now.
from raspibackup.
I updated to the latest installer code and I don't see the error message now but unfortunately, it's still not scheduling the backup job.
I was running...
raspiBackupInstallUI.sh 0.4.8.1, 2024-04-20/16:46:32 - 5d9729b
Now I'm running...
raspiBackupInstallUI.sh 0.4.8.1, 2024-05-12/15:43:10 - 225f671
from raspibackup.
I also noticed that on the working Pis, when I change the schedule, I'm prompted with the following...
"Do you want to save the updated cron settings for raspiBackup now?"
On the one that's not working, I get this prompt instead...
"Do you want to save the updated systemd settings for raspiBackup now?"
They are all running 64-bit Bullseye.
from raspibackup.
On the one that's not working, I get this prompt instead...
Starting with raspiBackupInstallUI 0.4.8 systemd is used instead of crond to schedule the backup. Looks like your other Raspberries use raspiBackup already for a long time 😉
Please show the output of following commands:
sudo systemctl status raspiBackup.timer
sudo systemctl status raspiBackup.service
cat /etc/systemd/system/raspiBackup.timer
cat /etc/systemd/system/raspiBackup.service
from raspibackup.
Starting with raspiBackupInstallUI 0.4.8 systemd is used instead of crond to schedule the backup. Looks like your other Raspberries use raspiBackup already for a long time 😉
Definitely...for years!
sudo systemctl status raspiBackup.timer
● raspiBackup.timer - Timer for raspiBackup.service to start backup
Loaded: loaded (/etc/systemd/system/raspiBackup.timer; disabled; vendor preset: enabled)
Active: inactive (dead)
Trigger: n/a
Triggers: ● raspiBackup.service
May 12 08:55:46 pi-aware systemd[1]: Stopped Timer for raspiBackup.service to start backup.
May 12 08:57:04 pi-aware systemd[1]: Started Timer for raspiBackup.service to start backup.
May 12 08:59:02 pi-aware systemd[1]: raspiBackup.timer: Succeeded.
May 12 08:59:02 pi-aware systemd[1]: Stopped Timer for raspiBackup.service to start backup.
May 12 08:59:54 pi-aware systemd[1]: Started Timer for raspiBackup.service to start backup.
May 12 18:19:00 pi-aware systemd[1]: raspiBackup.timer: Succeeded.
May 12 18:19:00 pi-aware systemd[1]: Stopped Timer for raspiBackup.service to start backup.
May 12 18:19:32 pi-aware systemd[1]: Started Timer for raspiBackup.service to start backup.
May 12 20:12:36 pi-aware systemd[1]: raspiBackup.timer: Succeeded.
May 12 20:12:36 pi-aware systemd[1]: Stopped Timer for raspiBackup.service to start backup.
sudo systemctl status raspiBackup.service
● raspiBackup.service - Creation of a Raspberry backup with raspiBackup
Loaded: loaded (/etc/systemd/system/raspiBackup.service; disabled; vendor preset: enabled)
Active: inactive (dead)
cat /etc/systemd/system/raspiBackup.timer
[Unit]
Description=Timer for raspiBackup.service to start backup
[Timer]
OnCalendar=*-*-* 00:00:42
# Create a backup once a week on Sunday morning at 5 am (default)
Unit=raspiBackup.service
[Install]
WantedBy=multi-user.target
cat /etc/systemd/system/raspiBackup.service
[Unit]
Description=Creation of a Raspberry backup with raspiBackup
[Service]
Type=simple
ExecStart=/usr/local/bin/raspiBackup.sh
# For Use with Wrapper Script: ExecStart=/usr/local/bin/raspiBackupWrapper.sh
[Install]
WantedBy=multi-user.target
from raspibackup.
The raspiBackup timer was not activated for some unknown reasons. Please execute following commands to activate the timer:
sudo systemctl enable raspiBackup.timer
sudo systemctl start raspiBackup.timer
sudo systemctl status raspiBackup.timer
Last command should return
pi@raspberrypi:~ $ systemctl status raspiBackup.timer
● raspiBackup.timer - Timer for raspiBackup.service to start backup
Loaded: loaded (/etc/systemd/system/raspiBackup.timer; enabled; preset: en>
Active: active (waiting) since Tue 2024-05-14 10:24:29 CEST; 5s ago
Trigger: Sun 2024-05-19 08:00:42 CEST; 4 days left
Triggers: ● raspiBackup.service
May 14 10:24:29 raspberrypi systemd[1]: Started raspiBackup.timer - Timer for raspiBackup.service to start backup.
They are all running 64-bit Bullseye.
I suggest to use latest OS Bookworm if it's a new system that has been set up 😉 .
from raspibackup.
I just tested latest installer on a bullseye system and configured a schedule of 09:00 am to make sure it's not an issue on Bullseye. Everything works fine.
from raspibackup.
sudo systemctl status raspiBackup.timer
Now returns this...
● raspiBackup.timer - Timer for raspiBackup.service to start backup
Loaded: loaded (/etc/systemd/system/raspiBackup.timer; enabled; vendor preset: enabled)
Active: active (waiting) since Tue 2024-05-14 16:25:40 EDT; 1min 29s ago
Trigger: Wed 2024-05-15 00:00:42 EDT; 7h left
Triggers: ● raspiBackup.service
May 14 16:25:40 pi-aware systemd[1]: Started Timer for raspiBackup.service to start backup.
I just tested latest installer on a bullseye system and configured a schedule of 09:00 am to make sure it's not an issue on Bullseye. Everything works fine.
It's still not creating a scheduled job when I run through the sudo raspiBackupInstallUI
steps.
What are the recommended steps to completely uninstall and reinstall cleanly?
Thanks for investigating this.
from raspibackup.
Trigger: Wed 2024-05-15 00:00:42 EDT; 7h left
Now the backup will be triggered in 7h and you should get a new backup. Everything should be OK now. You also should be able to update the time with the installer.
What are the recommended steps to completely uninstall and reinstall cleanly?
I don't think it's needed because the next backup is schedule in 7 hours. But if you still want to uninstall raspiBackup and install it again (you will loose the existing raspiBackup configuration) that's the way to go:
sudo raspiBackupInstallUI -u
will uninstall raspiBackup from your system. Then use the documented curl call to install latest raspiBackup again and will include the fix for your 8 AM issue
from raspibackup.
Thanks for investigating this.
You're welcome. You found a valid issue 😉
from raspibackup.
This is working on my newest Pi now. 👍
On my other five, I ran sudo systemctl status raspiBackup.timer
and got this for output...
Unit raspiBackup.timer could not be found.
What should I do to get these set up correctly using systemd instead of crond?
from raspibackup.
Great it works now.
It's not bad to use crond instead of systemd even systemd is the standard. There are folks who prefer to use crond.
But you can switch to use systemd instead of crond very easy. The installer has an option -t
with parameters crond
and systemd
. Just invoke sudo raspiBackupInstallUI -t systemd
and raspiBackup will use systemd. If you don't like systemd use parameter crond
and you will use crond again. But please note the scheduling information is not migrated when you switch. You have to configure the schedule again.
from raspibackup.
All six Pis using systemd for scheduling now. I'm all set!
Thank you!
from raspibackup.
Related Issues (20)
- raspiBackupRestore2Image.sh bricht mit Fehler ab. Fortschrittsanzeige fehlt bei Restore. HOT 6
- "Operation not supported" after finishing backup HOT 17
- Add Spanish and Italian language HOT 12
- Unable to run regular backup (manual run ok) HOT 15
- Ignore the ugly vanished source file error HOT 1
- Installer hangs very long if there is no internetconnection when some config should be updated
- raspiBackup Hangs on 'du -s' HOT 5
- Support external mounted partitions HOT 8
- Allow to specify for partition oriented backup which partitions should be restored
- Shrink last partition when a partition oriented backup was restored HOT 4
- No UUID updated in /boot/cmdline.txt & /etc/fstab HOT 5
- Regression test of Ubuntu 24-04 desktop and server HOT 1
- Enable to restore a backup into a loop device HOT 1
- Not working on Ubuntu 24.04 LTS - Raspberry Pi 4 and 5 HOT 11
- Backup fails with error message RBK0164E HOT 4
- raspiBackup tar backup operation hangs in ls on Bookworm using cifs HOT 66
- Support external partitions in installer
- Refactor special device handling HOT 1
- Fehlercode: RBI0021E: Es kann nicht auf www.linux-tips-and-tricks.de zugegriffen werden. wget RC: 4 HOT 29
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from raspibackup.