@Michael_514 Would you be able to provide the octoprint.log from your instance? Currently looking into why OctoPrint didn't exit with an error, if the backup was unsuccessful.
here it is, immediately prior to the update all the way thru completion, It seems to offer little diagnostic information pertaining to events outside the octoprint environment.
https://drive.google.com/file/d/1Smhi1E3pikbI6lKhDa2UwCJJAh51lL-X/view?usp=sharing
Hi @Michael_514, sorry for the delayed reply.
Have had a look and tested it myself, it seems OctoPrint doesn't log when you use the CLI commands. Have been through the source as well, and there is no 'non-zero' exit code when the backup fails, likely because if it was running from within OctoPrint it would break if it exited on failure. As a result, my script didn't pick up the failure in the backup (No idea why it may have failed, but that's the only logical cause) and tried to proceed.
Will be working on an update today to (hopefully!) address this and to look for some kind of error in the stdout to tell if it has worked.
Detecting system info...
OctoPi version: 0.17.0
Getting OctoPrint version...
OctoPrint version: 1.4.2
Reading installed plugins...
Traceback (most recent call last):
File "upgrade.py", line 555, in
plugin_keys = read_plugins_from_backup(backup_location)
File "upgrade.py", line 362, in read_plugins_from_backup
with zipfile.ZipFile(backup_path, 'r') as zip_ref:
File "/usr/lib/python3.7/zipfile.py", line 1204, in init
self.fp = io.open(file, filemode)
FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/.octoprint/data/backup/octoprint-backup-20200910-175925.zip'
@Shadow27374 - make sure you DO NOT run the install script as sudo. If that was not the case, then let me know.
OK i try it this evening.
Edit:
It was really only due to root privileges that the script requested later.
THX
1 Like