Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/etc/systemd/system/raspiBackup.timer not being created correctly. Error in OnCalendar line. #801

Open
ratsputin opened this issue Nov 3, 2024 · 4 comments
Assignees
Labels
bug Issue accepted as a bug

Comments

@ratsputin
Copy link

Fresh installation of raspiBackup with custom date/time selected. Here is the /etc/systemd/system/raspiBackup.timer file created:

Description=Timer for raspiBackup.service to start backup

[Timer]
OnCalendar=Tue*-*-* 02:00:42
# Create a backup once a week on Sunday morning at 5 am (default)
Unit=raspiBackup.service

[Install]
WantedBy=multi-user.target

There should be a space after the OnCalendar=Tue. With this error, raspiBackup will not run on schedule.

The comment following the OnCalendar line is incorrect as well, not reflecting the custom date/time. This is, of course, just a visual thing and inconsequential.

@framps
Copy link
Owner

framps commented Nov 3, 2024

A couple of days I got the same issue (see #800) and the issue was gone when the installer was upgraded. So I thought the user just had an old installer. But you wrote Fresh installation of raspiBackup which puzzles me now.

Would you please upgrade the installer as described in #800 and check if the issue is gone?

The comment following the OnCalendar line is incorrect

It's the comment of the default systemd timer template and every time update just updates the time and not the comment. But I see your point. I will remove the comment in the default template.

@framps framps self-assigned this Nov 3, 2024
@framps framps added the possible issue Detected some possible issue with raspiBackup label Nov 3, 2024
@ratsputin
Copy link
Author

As in #800, I did have to run raspiBackupInstallUI.sh -U to do the upgrade.

Once complete, I ran it again without the -U switch, changed the date to Monday and the time to 01:00, and this was the result:

[Unit]
Description=Timer for raspiBackup.service to start backup

[Timer]
OnCalendar=Mon *-*-* 01:00:42
# Create a backup once a week on Sunday morning at 5 am (default)
Unit=raspiBackup.service

[Install]
WantedBy=multi-user.target

So, it did work correctly. Apparently, installing it using the command

curl -o install -L https://raw.githubusercontent.com/framps/raspiBackup/master/installation/install.sh; sudo bash ./install

doesn't pick up the latest version of the UI? That is the command I used for the "fresh install".
This is on a Pi 3B+ with Bookworm if that matters.

@framps framps added bug Issue accepted as a bug and removed possible issue Detected some possible issue with raspiBackup labels Nov 4, 2024
@framps
Copy link
Owner

framps commented Nov 4, 2024

doesn't pick up the latest version of the UI?

I already tried to reproduce the issue when #800 was created but failed. I tried it again and again fail. I called raspiBackupInstallUI --version for the downloaded and upgraded version and both git commits are identical.

The issue seems to be related to the steps you execute when you configure raspiBackup with the installer. I think you don't have to update the installer for fix the issue. It's sufficient to stop the installer and start it again.

I installed raspiBackup and updated the time and day and everything was OK. I tried different config sequences and all the time the config file was OK. Would be great if you remember exactly the sequence of config steps you executed.

@framps
Copy link
Owner

framps commented Nov 4, 2024

I will remove the comment in the default template.

Removed right now :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue accepted as a bug
Projects
None yet
Development

No branches or pull requests

2 participants