Carl749862

Hi, I'm trying to do a rsnapshot backup of an unraid share to a backup disk setup as a pool device. It seems to get terminated after 3 hours each time. Any clues as to what could be doing this? I'm new to this so could be an error in config and crontab so included those. Thanks, Carl [2022-10-17T00:00:00] /usr/bin/rsnapshot beta: started [2022-10-17T00:00:00] echo 221 > /var/run/rsnapshot.pid [2022-10-17T00:00:00] mkdir -m 0755 -p /.snapshots/beta.0/localhost/ [2022-10-17T00:00:07] /usr/bin/rsync -a --delete --numeric-ids --relative --delete-excluded /data/Carl/ /.snapshots/beta.0/localhost/Carl [2022-10-17T03:00:05] /usr/bin/rsnapshot beta: ERROR: rsnapshot was sent TERM signal... cleaning up [2022-10-17T03:00:05] rm -f /var/run/rsnapshot.pid # do daily/weekly/monthly maintenance # min hour day month weekday command */15 * * * * run-parts /etc/periodic/15min 0 * * * * run-parts /etc/periodic/hourly 0 2 * * * run-parts /etc/periodic/daily 0 3 * * 6 run-parts /etc/periodic/weekly 0 5 1 * * run-parts /etc/periodic/monthly # rsnapshot examples 00 00 * * * rsnapshot beta 00 23 * * 6 rsnapshot gamma 00 22 1 * * rsnapshot delta ################################################# # rsnapshot.conf - rsnapshot configuration file # ################################################# # # # PLEASE BE AWARE OF THE FOLLOWING RULE: # # # # This file requires tabs between elements # # # ################################################# ####################### # CONFIG FILE VERSION # ####################### config_version 1.2 ########################### # SNAPSHOT ROOT DIRECTORY # ########################### # All snapshots will be stored under this root directory. # snapshot_root /.snapshots/ # If no_create_root is enabled, rsnapshot will not automatically create the # snapshot_root directory. This is particularly useful if you are backing # up to removable media, such as a FireWire or USB drive. # no_create_root 1 ################################# # EXTERNAL PROGRAM DEPENDENCIES # ################################# # LINUX USERS: Be sure to uncomment "cmd_cp". This gives you extra features. # EVERYONE ELSE: Leave "cmd_cp" commented out for compatibility. # # See the README file or the man page for more details. # cmd_cp /bin/cp # uncomment this to use the rm program instead of the built-in perl routine. # cmd_rm /bin/rm # rsync must be enabled for anything to work. This is the only command that # must be enabled. # cmd_rsync /usr/bin/rsync # Uncomment this to enable remote ssh backups over rsync. # cmd_ssh /usr/bin/ssh # Comment this out to disable syslog support. # cmd_logger /usr/bin/logger # Uncomment this to specify the path to "du" for disk usage checks. # If you have an older version of "du", you may also want to check the # "du_args" parameter below. # cmd_du /usr/bin/du # Uncomment this to specify the path to rsnapshot-diff. # cmd_rsnapshot_diff /usr/bin/rsnapshot-diff # Specify the path to a script (and any optional arguments) to run right # before rsnapshot syncs files # #cmd_preexec /path/to/preexec/script # Specify the path to a script (and any optional arguments) to run right # after rsnapshot syncs files # #cmd_postexec /path/to/postexec/script # Paths to lvcreate, lvremove, mount and umount commands, for use with # Linux LVMs. # #linux_lvm_cmd_lvcreate /path/to/lvcreate #linux_lvm_cmd_lvremove /path/to/lvremove #linux_lvm_cmd_mount /bin/mount #linux_lvm_cmd_umount /bin/umount ######################################### # BACKUP LEVELS / INTERVALS # # Must be unique and in ascending order # # e.g. alpha, beta, gamma, etc. # ######################################### #retain alpha 6 retain beta 7 retain gamma 4 retain delta 3 ############################################ # GLOBAL OPTIONS # # All are optional, with sensible defaults # ############################################ # Verbose level, 1 through 5. # 1 Quiet Print fatal errors only # 2 Default Print errors and warnings only # 3 Verbose Show equivalent shell commands being executed # 4 Extra Verbose Show extra verbose information # 5 Debug mode Everything # verbose 5 # Same as "verbose" above, but controls the amount of data sent to the # logfile, if one is being used. The default is 3. # loglevel 5 # If you enable this, data will be written to the file you specify. The # amount of data written is controlled by the "loglevel" parameter. # logfile /config/rsnapshot.log # If enabled, rsnapshot will write a lockfile to prevent two instances # from running simultaneously (and messing up the snapshot_root). # If you enable this, make sure the lockfile directory is not world # writable. Otherwise anyone can prevent the program from running. # lockfile /var/run/rsnapshot.pid # By default, rsnapshot check lockfile, check if PID is running # and if not, consider lockfile as stale, then start # Enabling this stop rsnapshot if PID in lockfile is not running # #stop_on_stale_lockfile 0 # Default rsync args. All rsync commands have at least these options set. # #rsync_short_args -a #rsync_long_args --delete --numeric-ids --relative --delete-excluded # ssh has no args passed by default, but you can specify some here. # #ssh_args -p 22 # Default arguments for the "du" program (for disk space reporting). # The GNU version of "du" is preferred. See the man page for more details. # If your version of "du" doesn't support the -h flag, try -k flag instead. # #du_args -csh # If this is enabled, rsync won't span filesystem partitions within a # backup point. This essentially passes the -x option to rsync. # The default is 0 (off). # #one_fs 0 # The include and exclude parameters, if enabled, simply get passed directly # to rsync. If you have multiple include/exclude patterns, put each one on a # separate line. Please look up the --include and --exclude options in the # rsync man page for more details on how to specify file name patterns. # #include ??? #include ??? #exclude ??? #exclude ??? # The include_file and exclude_file parameters, if enabled, simply get # passed directly to rsync. Please look up the --include-from and # --exclude-from options in the rsync man page for more details. # #include_file /path/to/include/file #exclude_file /path/to/exclude/file # If your version of rsync supports --link-dest, consider enabling this. # This is the best way to support special files (FIFOs, etc) cross-platform. # The default is 0 (off). # link_dest 1 # When sync_first is enabled, it changes the default behaviour of rsnapshot. # Normally, when rsnapshot is called with its lowest interval # (i.e.: "rsnapshot alpha"), it will sync files AND rotate the lowest # intervals. With sync_first enabled, "rsnapshot sync" handles the file sync, # and all interval calls simply rotate files. See the man page for more # details. The default is 0 (off). # #sync_first 0 # If enabled, rsnapshot will move the oldest directory for each interval # to [interval_name].delete, then it will remove the lockfile and delete # that directory just before it exits. The default is 0 (off). # #use_lazy_deletes 0 # Number of rsync re-tries. If you experience any network problems or # network card issues that tend to cause ssh to fail with errors like # "Corrupted MAC on input", for example, set this to a non-zero value # to have the rsync operation re-tried. # #rsync_numtries 0 # LVM parameters. Used to backup with creating lvm snapshot before backup # and removing it after. This should ensure consistency of data in some special # cases # # LVM snapshot(s) size (lvcreate --size option). # #linux_lvm_snapshotsize 100M # Name to be used when creating the LVM logical volume snapshot(s). # #linux_lvm_snapshotname rsnapshot # Path to the LVM Volume Groups. # #linux_lvm_vgpath /dev # Mount point to use to temporarily mount the snapshot(s). # #linux_lvm_mountpath /path/to/mount/lvm/snapshot/during/backup ############################### ### BACKUP POINTS / SCRIPTS ### ############################### # LOCALHOST backup /data/Carl localhost/ #backup /home/ localhost/ #backup /etc/ localhost/ #backup /usr/local/ localhost/ #backup /var/log/rsnapshot localhost/ #backup /etc/passwd localhost/ #backup /home/foo/My Documents/ localhost/ #backup /foo/bar/ localhost/ one_fs=1,rsync_short_args=-urltvpog #backup_script /usr/local/bin/backup_pgsql.sh localhost/postgres/ # You must set linux_lvm_* parameters below before using lvm snapshots #backup lvm://vg0/xen-home/ lvm-vg0/xen-home/ # EXAMPLE.COM #backup_exec /bin/date "+ backup of example.com started at %c" #backup [email protected]:/home/ example.com/ +rsync_long_args=--bwlimit=16,exclude=core #backup [email protected]:/etc/ example.com/ exclude=mtab,exclude=core #backup_exec ssh [email protected] "mysqldump -A > /var/db/dump/mysql.sql" #backup [email protected]:/var/db/dump/ example.com/ #backup_exec /bin/date "+ backup of example.com ended at %c" # CVS.SOURCEFORGE.NET #backup_script /usr/local/bin/backup_rsnapshot_cvsroot.sh rsnapshot.cvs.sourceforge.net/ # RSYNC.SAMBA.ORG #backup rsync://rsync.samba.org/rsyncftp/ rsync.samba.org/rsyncftp/

Also the contents of my appdata seems like it looks like it has the right config see attached and files etc, I've tried restoring various versions from as far back as a week. Could there be a permissions issue causing it not to be able to read this? The thing I recently changed was removing a cache drive, but I set the cache settings to move from cache back to array and ran mover and ensured the cache drive was empty before removing.

Thanks, feel free to move to docker sub forum, didn't spot that. Attached the diagnostics and here are the commands: Plex root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='Plex1' --net='host' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'PLEX_CLAIM'='claim-XXXXXXX' -e 'PLEX_UID'='99' -e 'PLEX_GID'='100' -e 'VERSION'='latest' -v '/mnt/user/appdata/plex/Transcode':'/transcode':'rw' -v '/mnt/user/Plex/':'/data':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' 'plexinc/pms-docker' a5678a18a3cff6c493bdd97331a7d8da Log: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 40-plex-first-run: executing... Attempting to obtain server token from claim token % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed Plex Media Server first run setup complete [cont-init.d] 40-plex-first-run: exited 0. [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... [cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0. [cont-init.d] 50-plex-update: executing... [cont-init.d] 50-plex-update: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Sync root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='Sync1' --net='host' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'TCP_PORT_8888'='8888' -e 'TCP_PORT_5555'='5555' -e 'UDP_PORT_3838'='3838' -v '/mnt/user/Carl/':'/home/Carl':'rw' -v '/mnt/user/Plex/':'/home/Plex':'rw' -v '/mnt/user/Seedbox/':'/home/Seedbox':'rw' -v '/mnt/user/appdata/sync':'/config':'rw' 'limetech/sync' 4ff603bffbcfafe651dac6c20fc9ce7414caa Log: *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/config.sh... dpkg-query: package 'tzdata' is not installed and no information is available Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. /usr/sbin/dpkg-reconfigure: tzdata is not installed *** /etc/my_init.d/config.sh failed with status 1 *** Killing all processes... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/config.sh... *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 10 Jan 22 10:12:56 SLOTH syslog-ng[19]: syslog-ng starting up; version='3.5.6' sloth-diagnostics-20210122-1002.zip

Hi, Somehow I seem to have messed up my docker containers (Resilio Sync/Plex etc). I've been doing some maintenance so must have done something to upset them as they were previously working fine. Now whenever I log into them it's like they are brand new and are ignoring the config in appdata, asking me to setup a new Plex server and same on Sync. I'd been using the CA Backup/Restore Appdata so have a weeks worth of backups, but even if I restore those and setup a new docker container it is still the same. It's almost like it's not using what's in appdata at all even though if I look in appdata it looks fine with config files etc. The paths in the docker container configs seem fine and pointing to /config/ -> mnt/user/appdata/sync etc which is correct. I'm fairly new to unraid so might be missing something obvious, anything I should check? Cheers, Carl