[Update Your Legacy SSL Certificate Now!]

10 minutes ago, ljm42 said:

 

You'll want to see the heading titled "Action needed for Unraid 6.9 and earlier"

Thank you! I mistakenly assumed that I was on the latest version.

[Update Your Legacy SSL Certificate Now!]

When I try to enter 'use_ssl no' at an SSH prompt, I get the following error: -bash: use_ssl: command not found

[[Plugin] CA Appdata Backup / Restore v2]

2 hours ago, Squid said:

Can you save the attached file onto your flash drive, then

cp /boot/backup.php /usr/local/emhttp/plugins/ca.backup2/scripts/backup.php
/usr/local/emhttp/plugins/ca.backup2/scripts/backup.php > /boot/backupdiag.log

After you get back a command prompt, post backupdiag.log on the flash drive here.

backup.php

After 2 hours of running, the dockers came back up this time. So, I'm not sure if this is a relevant log file but I've attached it anyways.

 

I'll let it run tonight and see if it works better.

backupdiag.log

[[Plugin] CA Appdata Backup / Restore v2]

1 minute ago, scubieman said:

Can you post your settings? 

 

[[Plugin] CA Appdata Backup / Restore v2]

1 minute ago, Squid said:

And you are running unRaid 6.6.x and v2018.11.17a of the plugin?

Correct

[[Plugin] CA Appdata Backup / Restore v2]

2 minutes ago, Squid said:

Post this for me

 

cat /var/lib/docker/unraid-autostart

root@Tower:~# cat /var/lib/docker/unraid-autostart
binhex-nzbhydra2
binhex-plexpass
binhex-radarr
binhex-sabnzbd
binhex-sonarr
Netdata
ombi
organizr

[[Plugin] CA Appdata Backup / Restore v2]

33 minutes ago, Squid said:

The syslog is sufficient.  Also, what is your unRaid version, and are the containers actually running but the Docker Tab says that they aren't?

Unraid 6.6.5. I have confirmed that the docker containers are definitely not running. They do start up when I manually start them though.

 

Here are all of the CA Backup/Restore messages from my syslog from last night:

 

    Line 2960: Dec  2 05:00:01 Tower CA Backup/Restore: #######################################
    Line 2961: Dec  2 05:00:01 Tower CA Backup/Restore: Community Applications appData Backup
    Line 2962: Dec  2 05:00:01 Tower CA Backup/Restore: Applications will be unavailable during
    Line 2963: Dec  2 05:00:01 Tower CA Backup/Restore: this process.  They will automatically
    Line 2964: Dec  2 05:00:01 Tower CA Backup/Restore: be restarted upon completion.
    Line 2965: Dec  2 05:00:01 Tower CA Backup/Restore: #######################################
    Line 2966: Dec  2 05:00:01 Tower CA Backup/Restore: Stopping binhex-nzbhydra2
    Line 2975: Dec  2 05:00:05 Tower CA Backup/Restore: docker stop -t 120 binhex-nzbhydra2
    Line 2976: Dec  2 05:00:05 Tower CA Backup/Restore: Stopping binhex-plexpass
    Line 2977: Dec  2 05:00:06 Tower CA Backup/Restore: docker stop -t 120 binhex-plexpass
    Line 2978: Dec  2 05:00:06 Tower CA Backup/Restore: Stopping binhex-radarr
    Line 2987: Dec  2 05:00:09 Tower CA Backup/Restore: docker stop -t 120 binhex-radarr
    Line 2988: Dec  2 05:00:09 Tower CA Backup/Restore: Stopping binhex-sabnzbd
    Line 2997: Dec  2 05:00:11 Tower CA Backup/Restore: docker stop -t 120 binhex-sabnzbd
    Line 2998: Dec  2 05:00:11 Tower CA Backup/Restore: Stopping binhex-sonarr
    Line 3007: Dec  2 05:00:14 Tower CA Backup/Restore: docker stop -t 120 binhex-sonarr
    Line 3008: Dec  2 05:00:14 Tower CA Backup/Restore: Stopping Netdata
    Line 3009: Dec  2 05:00:17 Tower CA Backup/Restore: docker stop -t 120 Netdata
    Line 3010: Dec  2 05:00:17 Tower CA Backup/Restore: Stopping ombi
    Line 3019: Dec  2 05:00:24 Tower CA Backup/Restore: docker stop -t 120 ombi
    Line 3020: Dec  2 05:00:24 Tower CA Backup/Restore: Stopping organizr
    Line 3029: Dec  2 05:00:31 Tower CA Backup/Restore: docker stop -t 120 organizr
    Line 3030: Dec  2 05:00:31 Tower CA Backup/Restore: Stopping tautulli
    Line 3039: Dec  2 05:00:38 Tower CA Backup/Restore: docker stop -t 120 tautulli
    Line 3040: Dec  2 05:00:38 Tower CA Backup/Restore: Backing Up appData from /mnt/user/appdata/ to /mnt/user/CommunityApplicationsAppdataBackup/[email protected]
    Line 3041: Dec  2 05:00:48 Tower CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar -cvaf '/mnt/user/CommunityApplicationsAppdataBackup/[email protected]/CA_backup.tar.gz' --exclude 'docker.img'  * >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress
    Line 3142: Dec  2 05:51:35 Tower CA Backup/Restore: Backup Complete
    Line 3143: Dec  2 05:51:35 Tower CA Backup/Restore: Verifying backup
    Line 3144: Dec  2 05:51:35 Tower CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar --diff -C '/mnt/user/appdata/' -af '/mnt/user/CommunityApplicationsAppdataBackup/[email protected]/CA_backup.tar.gz' > /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log & echo $! > /tmp/ca.backup2/tempFiles/verifyInProgress
    Line 3150: Dec  2 06:07:09 Tower CA Backup/Restore: #######################
    Line 3151: Dec  2 06:07:09 Tower CA Backup/Restore: appData Backup complete
    Line 3152: Dec  2 06:07:09 Tower CA Backup/Restore: #######################
    Line 3153: Dec  2 06:07:09 Tower CA Backup/Restore: Backup / Restore Completed
 

[[Plugin] CA Appdata Backup / Restore v2]

24 minutes ago, scubieman said:

Pretty sure if you go into the settings of this you can turn it on. I think off by default.

 

I don't see anything about turning auto restart on or off in the settings.

[[Plugin] CA Appdata Backup / Restore v2]

Starting last week I noticed that when CA Appdata Backup/Restore takes down my docker containers for backup, they're not being automatically restarted. The Backup/Restore status claims that it's trying to start the containers but I don't see that in the container logs.

 

Are there log files that I should be looking at to help diagnose this?