search

teejee2008 / timeshift

System restore tool for Linux. Creates filesystem snapshots using rsync+hardlinks, or BTRFS snapshots. Supports scheduled snapshots, multiple backup levels, and exclude filters. Snapshots can be restored while system is running or from Live CD/USB.
GNU Lesser General Public License v3.0
4.68k stars 281 forks source link

Error message with Cron Timeshift hourly #596

Open Trebor87 opened 4 years ago

Trebor87 commented 4 years ago

I use Timeshift v20.03 on Manajro version Lysia 20.0 XFCE, before on 18 and 19.0

It runs well with no apparent problems and runs a Daily backup to an external HD partitioned with Ext4 for the backup size 107 Gb

Installing Timeshift creates a file in cron.d called timeshift-hourly and this generates an email containing an error message, see below.

I do not run an hourly backup, I tried before but don't need it but with or without an hourly backup the cron email runs with the same error every hour

Timeshift opens correctly and gives no error messages. I did a uninstall and a clean install, same problems

this mail contains :

_> (process:369084): GLib-GIO-CRITICAL **: 14:00:01.935: g_file_get_path: assertion 'G_IS_FILE (file)' failed

(process:369084): CRITICAL : 14:00:01.935: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed

(process:369084): CRITICAL : 14:00:01.935: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed

/dev/sdd2 is mounted at: /run/timeshift/backup, options: rw,relatime

Daily snapshots are enabled Last daily snapshot is 16 hours old_

steadfasterX commented 4 years ago

same here.. :(

qsv commented 3 years ago

As of April 2021 it seems that this is still and issue. Anyone any insight as to what is actually causing this message? I think it may be happening on almost every system. It just showed up for me when I installed sSMTP, and the "root" account can actually send a real email. I get one/hour

(process:195956): GLib-GIO-CRITICAL **: 15:00:01.941: g_file_get_path: assertion 'G_IS_FILE (file)' failed

** (process:195956): CRITICAL **: 15:00:01.941: tee_jee_file_system_path_combine: assertion 'path1 != NULL' failed

** (process:195956): CRITICAL **: 15:00:01.941: tee_jee_file_system_dir_exists: assertion 'dir_path != NULL' failed

/dev/sdc1 is mounted at: /run/timeshift/backup, options: rw,relatime
Trebor87 commented 3 years ago

Since this message, I've moved from Manjaro to Arch and no longer have this message

woodward2 commented 2 years ago

Just done a fresh install of Linux Mint MATE 20.3 (overwriting 20.2 upgraded from 19.3). These messages have appeared since the re-installation.

I have configured timeshift the same as before: NO scheduled backups, an on-demand backup is run automatically from a script before any apt-* update.

The error messages come from a nightly root cron job which runs timeshift --list as part of a cleanup script. Running the same script manually from the command line produces no errors; looks like an issue with the cron environment?

The old version of timeshift (from Mint 20.2) was 20.11.1.1+ulyssa The new version (from Mint 20.3) is 21.09.1.1+una.

koocotte commented 2 years ago

As a workaround, I tried to update /etc/cron.d/timeshift-hourly to use systemd-cat: 

SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

0 * * * * root systemd-cat --identifier=timeshift-cron --stderr-priority=err /usr/bin/timeshift --check --scripted

but the crontab is rewritten when timeshift is run.