RE: [Release] Backup (formerly XBMC Backup) - zorro2222 - 2017-06-13
(2017-06-11, 22:14)Karellen Wrote: @zorro2222
We do not allow logs to be pasted directly into this forum. Use a pastebin site.
I have removed both your logs.
https://pastebin.com/hcBrGrfC
RE: [Release] Backup (formerly XBMC Backup) - peterg1 - 2017-06-14
I have been trying to backup my build which is currently on my nvidia shield pro.
No matter which way i try to back it up, when i try to restore it to my MacBook the screen layout settings won't have been saved.
All of the addons are there, and enabled and run fine, problem is the screen layout.
I would like to avoid having to re enter all of the settings for the menus and submenus, basically so it works properly like i've backed up the thing so it can be loaded up and will run!
Is there something i'm missing when saving to a usb,
i currently have everything ticked except custom directory 1 and 2. If i select either of these to save it has browse path??
Thanks in advance
Pete.
[Release] Backup (formerly XBMC Backup) - ed_davidson - 2017-06-15
What skin are you running? Here's how to do it. Do the backup like normal. When you want to restore, change from the skin with all your settings in. Once the restore has finished reboot and switch back. You can not restore a settings.xml or guisettings.xml while it is still in use.
Backup stuck at 24% - RomMon - 2017-07-17
In the Kodi GUI I see:
Backup - Mode: Backup:24%
userdata/addon_data/service.system.docker/docker/overlay2/l/Y...
I didn't try to interrupt the current backup (e.g. reboot, or try to kill a process).
Any idea why it is stuck? [edit, see below, it is plexpy]
What is the best next step? Just a reboot, and try a manual backup, or are there other logs I can have a look at:?
I have backup scheduled to backup on Monday morning 3:00am.
Backup was installed on July 2, and the first backup was initiated manually, and turned off in the evening.
This is installed on a Tronsmart Axa X5 Plus, using LE8 "Extended" community build (Generic)'.
I'm missing the July 17 backup:
Code: # ls -lath /storage/backup/
total 919632
drwxr-xr-x 22 root root 4.0K Jul 17 18:59 ..
-rw-r--r-- 1 root root 273.5M Jul 10 03:01 201707100300.zip
drwxr-xr-x 2 root root 4.0K Jul 10 03:01 .
-rw-r--r-- 1 root root 66.0M Jul 2 15:00 201707021500.zip
-rw-r--r-- 1 root root 558.6M Jul 2 14:59 20170702145856.tar
#
Code: # ls -lath /storage/.kodi/temp/
total 134092
-rw-r--r-- 1 root root 24.2K Jul 17 22:49 kodi.log
-rw-r--r-- 1 root root 6.6K Jul 17 22:46 hd-idle.log
-rw-r--r-- 1 root root 130.3M Jul 17 03:01 xbmc_backup_temp.zip
drwxr-xr-x 5 root root 4.0K Jul 17 03:00 .
drwxr-xr-x 2 root root 4.0K Jul 17 01:08 archive_cache
-rw-r--r-- 1 root root 59.6K Jul 17 01:07 kodi.old.log
<snip>
In kodi.log I see the following applicable messages:
Code: 01:15:17.626 T:140634660787968 ERROR: OnTvStandby - Unexpected [standby_pc_on_tv_standby] setting value
03:00:00.231 T:140633872267008 NOTICE: script.xbmcbackup-1.0.9: Starting
03:00:00.401 T:140633872267008 NOTICE: script.xbmcbackup-1.0.9: Local Dir: /storage/.kodi/
03:00:00.401 T:140633872267008 NOTICE: script.xbmcbackup-1.0.9: Remote Dir: 201707170300/
03:00:00.435 T:140633872267008 NOTICE: script.xbmcbackup-1.0.9: Mode - Backup
03:00:00.525 T:140633872267008 NOTICE: script.xbmcbackup-1.0.9: Creating Files List
03:00:16.692 T:140633872267008 NOTICE: script.xbmcbackup-1.0.9: Writing files to: 201707170300/
03:00:16.693 T:140633872267008 NOTICE: script.xbmcbackup-1.0.9: Source: /storage/.kodi/
03:08:36.331 T:140634065200896 WARNING: CSkinInfo: failed to load skin settings
20:13:10.218 T:140632672667392 WARNING: Previous line repeats 1 times.
20:13:10.240 T:140632672667392 ERROR: GetDirectory - Error getting
20:14:34.707 T:140635261063296 ERROR: Previous line repeats 6 times.
20:14:34.707 T:140635261063296 ERROR: GetDirectory - Error getting zip://%2fstorage%2f.kodi%2ftemp%2fxbmc_backup_temp.zip/
<snip>
22:49:10.162 T:140632535238400 ERROR: GetDirectory - Error getting
The location it is stuck is a symlink. Must be the one starting with Y so YN22JQ3N4NTJB5E5BU7YSQTKRU.
This symlink was added after the last successful backup (a week ago)
I added docker last week, but only today I tried a little with it.
Code: ~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/l # ls -la
total 100
drwx------ 2 root root 4096 Jul 17 19:02 .
drwx------ 26 root root 4096 Jul 17 19:02 ..
lrwxrwxrwx 1 root root 77 Jul 10 21:07 2OEZRP3CLFLYBSBF7QAY3DS6RU -> ../f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f-init/diff
lrwxrwxrwx 1 root root 72 Jul 17 01:08 6OX2XZRE2KFJXICD34T5AAGCE6 -> ../2466a9edcc1010e86e2d80bf3f1a642637d258f393ae3b91de89a5c7bfcf054e/diff
lrwxrwxrwx 1 root root 72 Jul 10 20:07 6Q55UBP2IBPL245NOHF5W4DVZK -> ../d6b09b71af853dec41c51aa04bd31a9a81cdda481ee3a06b9375c98aef1860e5/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:02 6VJICAQU5MPMPSI6ZTMS3B5XFD -> ../0427b0a3d445cf66b26e50e56e90c855dec612b8b71ac44d775e1ad75dae6c17/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:02 7QYCFJZLUPQUGSXPAVGRTT6S5O -> ../83b29f0bc6b3c0776501902e8088847ebd35eb5b305569313efd6a833b76c546/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:02 7ZXZPNDWOBYLNAIC4IT76BGX7H -> ../bfc28e0308c050b80a14c5350984911a8a740143b1078a65f3dfb8569d76c365/diff
lrwxrwxrwx 1 root root 72 Jul 10 20:08 AIGTYX2O3S5ABYBEZYJE6OEKOS -> ../10957c841c25ff0a6180a53909a7eb374ba92d18f2519c6cec7ae0de14ef5c6e/diff
lrwxrwxrwx 1 root root 72 Jul 10 20:08 AYJQDLLORIEYFEFUEWGQ7NVMS5 -> ../fd46657e6bacb9db542a1f7e7332cfac43437743351945537dffb75e6030822f/diff
lrwxrwxrwx 1 root root 72 Jul 10 20:08 BNCL5PB6OT4J6ODUV266BYUW2O -> ../3d37b45967282b93b69ec453a7165c8fcab112e8238234d1e207ff3bbd5ffc45/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:01 CUAOSGVT2YWLDEWFF3B6PAVYTU -> ../434a435bee60bdfebb906234d7d7abc46ccc953cfba0f2f10661d43b68006c19/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:02 ECCAY7W7YC4U4MYJCSDZMA2UOE -> ../a70a5ea3aacadb1786f4216581b95ab139c97a52d8d85a42758e71116897d568/diff
lrwxrwxrwx 1 root root 72 Jul 17 01:07 GVPE7LYNQFQ5NXXBBWST53RXE7 -> ../0be8580060d4d823bdbcd556e5ecba8a171fbdb97e1f545c03ee99fb60290fa7/diff
lrwxrwxrwx 1 root root 77 Jul 17 19:02 KPITRTI33D2M4KKTKSFT7L7CYI -> ../ce949498801c02e282405fd0d39e80e0ecb69d9ef6071245a5c397890181c5a5-init/diff
lrwxrwxrwx 1 root root 72 Jul 10 20:07 LSNJUXFNDCQ6EWDW2JCGC5XO5V -> ../12ce80a8ab1c9e2789755c5a287a566ae553673359cc84e6f899e505072fd78c/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:01 MA6ST64N3YNU5QY26FB7R7ZT5H -> ../6a0c3adcd2ebeeeba204efb63312d4fc5e6319009b8ad23368d7c3c934a43a9a/diff
lrwxrwxrwx 1 root root 72 Jul 10 20:07 N2KD6KPHDWYMR3OQFHMIND5TEA -> ../1f4ab7c56b21b5beeb281825d51ee685f94edede75375dca9673d689fc21cc16/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:02 ONKNUGEZ62VSBB3K6XPNQC2ODA -> ../ce949498801c02e282405fd0d39e80e0ecb69d9ef6071245a5c397890181c5a5/diff
lrwxrwxrwx 1 root root 72 Jul 17 01:07 SUP3UXAEG7POLG6SKVKD7656T3 -> ../cc0188df8dab363e0cefd18e069bc9b2f13c3abe422346bd63073e7a40662423/diff
lrwxrwxrwx 1 root root 72 Jul 17 01:07 UADHVXWHBSVG4YWRPE7Y5EMW2F -> ../da5f164ce943f65bf9e6ba1de51189c5779e3849909c4ce998eea53d2aa169c1/diff
lrwxrwxrwx 1 root root 77 Jul 17 01:08 VR4KWXVMUCVZIXCJEG64KBM3H6 -> ../2466a9edcc1010e86e2d80bf3f1a642637d258f393ae3b91de89a5c7bfcf054e-init/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:02 XZW4XKCZ67IEKLL3L3SCJMQ24U -> ../c9a5c037f34e685a1fe6f3e43bc56039aff28d3aa663c442bd4337f4a4970b57/diff
lrwxrwxrwx 1 root root 72 Jul 10 21:07 YN22JQ3N4NTJB5E5BU7YSQTKRU -> ../f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff
lrwxrwxrwx 1 root root 72 Jul 17 19:02 ZZAOLFTE6BSVPVOJZNSSSR556S -> ../685b2a99c313c4ca3d229ed94c3083d066a61a82490a1f774f1a01a1bfdbb4c1/diff
Don't see a process for backup:
Code: # ps -ef | grep -i ba
37 root 0:00 [writeback]
4602 root 0:00 grep -i ba
Edit (2017-07-21):
Rebooted the system, and started a manual backup.
Also this backup looks to be stuck at the same location userdata/addon_data/service.system.docker/docker/overlay2/l/YN.....
So it is reproducible on my system.
Any logs I can enable to get more details?
The symlink at which it's stuck points to the following:
Code: LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */
app/:
total 8
drwxr-xr-x 2 nobody users 4096 Jul 8 00:16 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
defaults/:
total 8
drwxr-xr-x 2 nobody users 4096 Jul 8 00:16 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
etc/:
total 36
drwxr-xr-x 4 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
drwxr-xr-x 2 root root 4096 Jul 8 00:27 cont-init.d
-rw-r--r-- 1 root root 739 Jul 10 21:07 group
-rw-r--r-- 1 root root 740 Jul 8 00:17 group-
-rw-r--r-- 1 root root 1312 Jul 10 21:07 passwd
-rw-r--r-- 1 root root 1310 Jul 10 21:07 passwd-
drwxr-xr-x 3 root root 4096 Jul 8 00:27 services.d
-rw-r----- 1 root 42 486 Jul 8 00:17 shadow
logs/:
total 8
drwxr-xr-x 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
opt/:
total 12
drwxr-xr-x 3 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
drwxr-xr-x 3 root root 4096 Jul 10 21:07 plexpy
var/:
total 12
drwxr-xr-x 3 root root 4096 Jul 8 00:17 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */*/
etc/cont-init.d/:
total 16
drwxr-xr-x 2 root root 4096 Jul 8 00:27 .
drwxr-xr-x 4 root root 4096 Jul 10 21:07 ..
-rwxr-xr-x 1 root root 658 Jul 8 00:15 10-adduser
-rwxr-xr-x 1 root root 571 Jul 8 00:27 30-install
etc/services.d/:
total 12
drwxr-xr-x 3 root root 4096 Jul 8 00:27 .
drwxr-xr-x 4 root root 4096 Jul 10 21:07 ..
drwxr-xr-x 2 root root 4096 Jul 8 00:27 plexpy
opt/plexpy/:
total 12
drwxr-xr-x 3 root root 4096 Jul 10 21:07 .
drwxr-xr-x 3 root root 4096 Jul 10 21:07 ..
drwxr-xr-x 7 root root 4096 Jul 10 21:07 .git
var/run/:
total 12
drwxr-xr-x 3 root root 4096 Jul 10 21:07 .
drwxr-xr-x 3 root root 4096 Jul 8 00:17 ..
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */*/*/
etc/services.d/plexpy/:
total 12
drwxr-xr-x 2 root root 4096 Jul 8 00:27 .
drwxr-xr-x 3 root root 4096 Jul 8 00:27 ..
-rwxr-xr-x 1 root root 105 Jul 8 00:27 run
var/run/s6/:
total 32
drwxr-xr-x 8 root root 4096 Jul 10 21:07 .
drwxr-xr-x 3 root root 4096 Jul 10 21:07 ..
drwxr-xr-x 2 root root 4096 Jul 10 21:07 container_environment
drwxr-xr-x 2 root root 4096 Jul 10 21:07 env-stage1
drwxr-xr-x 2 root root 4096 Jul 10 21:07 env-stage2
drwxr-xr-x 2 root root 4096 Jul 10 21:07 env-stage3
drwxr-xr-x 2 root root 4096 Jul 10 21:07 etc
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */*/*/*
-rwxr-xr-x 1 root root 105 Jul 8 00:27 etc/services.d/plexpy/run
var/run/s6/container_environment:
total 44
drwxr-xr-x 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
-rw-r--r-- 1 root root 5 Jul 10 21:07 HOME
-rw-r--r-- 1 root root 12 Jul 10 21:07 HOSTNAME
-rw-r--r-- 1 root root 60 Jul 10 21:07 PATH
-rw-r--r-- 1 root root 3 Jul 10 21:07 PGID
-rw-r--r-- 1 root root 30 Jul 10 21:07 PS1
-rw-r--r-- 1 root root 5 Jul 10 21:07 PUID
-rw-r--r-- 1 root root 5 Jul 10 21:07 TERM
-rw-r--r-- 1 root root 16 Jul 10 21:07 TZ
-rw-r--r-- 1 root root 33 Jul 10 21:07 WARNING_MSG
var/run/s6/env-stage1:
total 12
drwxr-xr-x 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
-rw-r--r-- 1 root root 30 Jul 10 21:07 PATH
var/run/s6/env-stage2:
total 8
drwxr-xr-x 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
var/run/s6/env-stage3:
total 8
drwxr-xr-x 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
var/run/s6/etc:
total 8
drwxr-xr-x 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
lrwxrwxrwx 1 root root 18 Jul 10 21:07 cont-finish.d -> /etc/cont-finish.d
lrwxrwxrwx 1 root root 16 Jul 10 21:07 cont-init.d -> /etc/cont-init.d
lrwxrwxrwx 1 root root 16 Jul 10 21:07 fix-attrs.d -> /etc/fix-attrs.d
lrwxrwxrwx 1 root root 15 Jul 10 21:07 services.d -> /etc/services.d
var/run/s6/services:
total 16
drwxr-xr-x 4 root root 4096 Jul 10 21:07 .
drwxr-xr-x 8 root root 4096 Jul 10 21:07 ..
drwxr-xr-x 5 root root 4096 Jul 10 21:07 s6-fdholderd
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */*/*/*/*
-rw-r--r-- 1 root root 5 Jul 10 21:07 var/run/s6/container_environment/HOME
-rw-r--r-- 1 root root 12 Jul 10 21:07 var/run/s6/container_environment/HOSTNAME
-rw-r--r-- 1 root root 60 Jul 10 21:07 var/run/s6/container_environment/PATH
-rw-r--r-- 1 root root 3 Jul 10 21:07 var/run/s6/container_environment/PGID
-rw-r--r-- 1 root root 30 Jul 10 21:07 var/run/s6/container_environment/PS1
-rw-r--r-- 1 root root 5 Jul 10 21:07 var/run/s6/container_environment/PUID
-rw-r--r-- 1 root root 5 Jul 10 21:07 var/run/s6/container_environment/TERM
-rw-r--r-- 1 root root 16 Jul 10 21:07 var/run/s6/container_environment/TZ
-rw-r--r-- 1 root root 33 Jul 10 21:07 var/run/s6/container_environment/WARNING_MSG
-rw-r--r-- 1 root root 30 Jul 10 21:07 var/run/s6/env-stage1/PATH
var/run/s6/services/s6-fdholderd:
total 32
drwxr-xr-x 5 root root 4096 Jul 10 21:07 .
drwxr-xr-x 4 root root 4096 Jul 10 21:07 ..
-rw-r--r-- 1 root root 1 Jul 10 21:07 down
drwx-ws--T 2 root root 4096 Jul 10 21:07 event
-rw-r--r-- 1 root root 1 Jul 10 21:07 notification-fd
drwxr-xr-x 3 root root 4096 Jul 10 21:07 rules
-rwxr-xr-x 1 root root 121 Jul 10 21:07 run
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */*/*/*/*/*
-rw-r--r-- 1 root root 1 Jul 10 21:07 var/run/s6/services/s6-fdholderd/down
-rw-r--r-- 1 root root 1 Jul 10 21:07 var/run/s6/services/s6-fdholderd/notification-fd
-rwxr-xr-x 1 root root 121 Jul 10 21:07 var/run/s6/services/s6-fdholderd/run
var/run/s6/services/s6-fdholderd/event:
total 8
drwx-ws--T 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 5 root root 4096 Jul 10 21:07 ..
var/run/s6/services/s6-fdholderd/rules:
total 12
drwxr-xr-x 3 root root 4096 Jul 10 21:07 .
drwxr-xr-x 5 root root 4096 Jul 10 21:07 ..
drwxr-xr-x 4 root root 4096 Jul 10 21:07 uid
var/run/s6/services/s6-fdholderd/supervise:
total 12
drwx------ 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 5 root root 4096 Jul 10 21:07 ..
prw------- 1 root root 0 Jul 10 21:07 control
-rw-r--r-- 1 root root 0 Jul 10 21:07 lock
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */*/*/*/*/*/*
prw------- 1 root root 0 Jul 10 21:07 var/run/s6/services/s6-fdholderd/supervise/control
-rw-r--r-- 1 root root 0 Jul 10 21:07 var/run/s6/services/s6-fdholderd/supervise/lock
-rw-r--r-- 1 root root 35 Jul 10 21:07 var/run/s6/services/s6-fdholderd/supervise/status
var/run/s6/services/s6-fdholderd/rules/uid:
total 16
drwxr-xr-x 4 root root 4096 Jul 10 21:07 .
drwxr-xr-x 3 root root 4096 Jul 10 21:07 ..
drwxr-xr-x 3 root root 4096 Jul 10 21:07 0
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */*/*/*/*/*/*/*
var/run/s6/services/s6-fdholderd/rules/uid/0:
total 12
drwxr-xr-x 3 root root 4096 Jul 10 21:07 .
drwxr-xr-x 4 root root 4096 Jul 10 21:07 ..
-rw-r--r-- 1 root root 0 Jul 10 21:07 allow
drwxr-xr-x 2 root root 4096 Jul 10 21:07 env
var/run/s6/services/s6-fdholderd/rules/uid/default:
total 12
drwxr-xr-x 3 root root 4096 Jul 10 21:07 .
drwxr-xr-x 4 root root 4096 Jul 10 21:07 ..
-rw-r--r-- 1 root root 0 Jul 10 21:07 allow
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff # ls -la */*/*/*/*/*/*/*/*
-rw-r--r-- 1 root root 0 Jul 10 21:07 var/run/s6/services/s6-fdholderd/rules/uid/0/allow
-rw-r--r-- 1 root root 0 Jul 10 21:07 var/run/s6/services/s6-fdholderd/rules/uid/default/allow
var/run/s6/services/s6-fdholderd/rules/uid/0/env:
total 28
drwxr-xr-x 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 3 root root 4096 Jul 10 21:07 ..
-rw-r--r-- 1 root root 1 Jul 10 21:07 S6_FDHOLDER_GETDUMP
-rw-r--r-- 1 root root 1 Jul 10 21:07 S6_FDHOLDER_LIST
-rw-r--r-- 1 root root 1 Jul 10 21:07 S6_FDHOLDER_RETRIEVE_REGEX
-rw-r--r-- 1 root root 1 Jul 10 21:07 S6_FDHOLDER_SETDUMP
-rw-r--r-- 1 root root 1 Jul 10 21:07 S6_FDHOLDER_STORE_REGEX
var/run/s6/services/s6-fdholderd/rules/uid/default/env:
total 12
drwxr-xr-x 2 root root 4096 Jul 10 21:07 .
drwxr-xr-x 3 root root 4096 Jul 10 21:07 ..
-rw-r--r-- 1 root root 1 Jul 10 21:07 S6_FDHOLDER_LIST
LibreELEC:~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/f84d1f3581a0e62faab9223ec879eb763ebb552bd8ec4ad862d6629f80b1f53f/diff #
Edit (2017-07-23):
Started removing Docker related packages, and removing plexpy solved the Backup getting stuck.
Re-installing plexpy (requires LinuxServer.io's Docker add-on) causing Backup to get stuck again.
It now get stuck at ~/.kodi/userdata/addon_data/service.system.docker/docker/overlay2/l/FOSE5AN34PNXABUTBTODLJYLAA
(which is indeed related to plexpy)
A note for removing plexpy, you also need to remove the container via e.g. via Portainer <ip_address>:9000/#/containers/ and remove the plexpy container.
RE: [Release] Backup (formerly XBMC Backup) - saptadip - 2017-08-06
I am using the Backup addon to store the backup file to my google drive. But my backup is failing with the below exception:
Code: 23:05:19.159 T:1740612592 NOTICE: script.xbmcbackup-1.0.9: Writing files to: /Kodi Backup/
23:05:19.162 T:1740612592 NOTICE: script.xbmcbackup-1.0.9: Source: /home/osmc/.kodi/temp/
23:05:19.357 T:1740612592 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <class 'httplib.BadStatusLine'>
Error Contents: ''
Traceback (most recent call last):
File "/home/osmc/.kodi/addons/script.xbmcbackup/scheduler.py", line 156, in <module>
BackupScheduler().start()
File "/home/osmc/.kodi/addons/script.xbmcbackup/scheduler.py", line 57, in start
backup.run(XbmcBackup.Backup,True)
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/backup.py", line 278, in run
fileCopied = self.backupFiles(fileManager.getFiles(),self.xbmc_vfs, self.remote_vfs)
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/backup.py", line 482, in backupFiles
wroteFile = dest.put(aFile,dest.root_path + aFile[len(source.root_path):])
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/vfs.py", line 390, in put
parentFolder = self._getGoogleFile(pathList[0])
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/vfs.py", line 464, in _getGoogleFile
file_list = self.drive.ListFile({'q':"title='" + pathList[1] + "' and 'root' in parents and trashed=false"}).GetList()
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/pydrive/apiattr.py", line 155, in GetList
for x in self:
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/pydrive/apiattr.py", line 139, in next
result = self._GetList()
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/pydrive/auth.py", line 54, in _decorated
return decoratee(self, *args, **kwargs)
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/pydrive/files.py", line 56, in _GetList
self.metadata = self.auth.service.files().list(**dict(self)).execute()
File "/home/osmc/.kodi/addons/script.module.oauth2client/lib/oauth2client/util.py", line 137, in positional_wrapper
return wrapped(*args, **kwargs)
File "/home/osmc/.kodi/addons/script.module.googleapi/lib/apiclient/http.py", line 722, in execute
body=self.body, headers=self.headers)
File "/home/osmc/.kodi/addons/script.module.oauth2client/lib/oauth2client/util.py", line 137, in positional_wrapper
return wrapped(*args, **kwargs)
File "/home/osmc/.kodi/addons/script.module.oauth2client/lib/oauth2client/client.py", line 556, in new_request
redirections, connection_type)
File "/home/osmc/.kodi/addons/script.module.httplib2/lib/httplib2/__init__.py", line 1570, in request
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/home/osmc/.kodi/addons/script.module.httplib2/lib/httplib2/__init__.py", line 1317, in _request
(response, content) = self._conn_request(conn, request_uri, method, body, headers)
File "/home/osmc/.kodi/addons/script.module.httplib2/lib/httplib2/__init__.py", line 1286, in _conn_request
response = conn.getresponse()
File "/usr/lib/python2.7/httplib.py", line 1111, in getresponse
response.begin()
File "/usr/lib/python2.7/httplib.py", line 444, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.7/httplib.py", line 408, in _read_status
raise BadStatusLine(line)
BadStatusLine: ''
-->End of Python script error report<--
The backup zip file is also created on the system:
Code: -rw-r--r-- 1 osmc osmc 518940108 Aug 5 23:05 /home/osmc/.kodi/temp/201708052300.zip
osmc@osmc:~/.kodi/temp$ file /home/osmc/.kodi/temp/201708052300.zip
/home/osmc/.kodi/temp/201708052300.zip: Zip archive data, at least v2.0 to extract
I have already stored the google client id and secret in the addon, so I don't think it's the drive accessibility issue. Also I can see an empty "Kodi Backup" folder is created in my GDrive each time the backup runs. When I checked in google, I found that httplib.BadStatusLine is reported when the http response code returned from the server(GDrive) is not recognized by the application(Backup Add-on)
Did anyone face this problem? How this can be resolved?
RE: [Release] Backup (formerly XBMC Backup) - sarahmic - 2017-08-09
Hi friends
I'm having Backup problems.
I've got Backup program addon but when i set the Backup trail to send addons to a pendrive, they basically all give me something like 'storage/0000-0000/9508' and other variations of this.
Backup starts on it's own but nothing goes to the pendrive and i don't actually know where they are going!
this is my Android box - Review: H96 PRO PLUS S912 3GB RAM 4K Android TV Box -
Tried 2 different pendrives with the same problems
My box has 32GB Memory and i still have 23GB empty so it has more than enough Storage.
I have 3 boxes, 2 of them have 16.1 and i tried the same pendrive on these 2 boxes and with the same Backup Program Addon to backup - everything was backed up ok!!
It's the box with the 17.1 which is giving me the problems.
On the other 2 boxes when i set the path it comes fine like: usb/sda1/kodi folder, and backup of addons are all there!
On the 17.1 when i set the path it shows as usb/9805.2333/but doesn't backup on the pendrive.
Now i've been reading this thread and in post number 1470 it's said that the Backup is going to Internal Storage and then i 'manually' have to grab it from there and install in the stick/pendrive.
How do i do this please? Where do i find the backup in the Internal Storage? Can someone explain to a 'noob' please?
Thanks lots.
RE: [Release] Backup (formerly XBMC Backup) - sarahmic - 2017-08-10
Can no one answer my query please?
Thanks
RE: [Release] Backup (formerly XBMC Backup) - msnow - 2017-08-11
(2017-08-09, 18:27)sarahmic Wrote: Hi friends
I'm having Backup problems.
I've got Backup program addon but when i set the Backup trail to send addons to a pendrive, they basically all give me something like 'storage/0000-0000/9508' and other variations of this.
Backup starts on it's own but nothing goes to the pendrive and i don't actually know where they are going!
this is my Android box - Review: H96 PRO PLUS S912 3GB RAM 4K Android TV Box -
Tried 2 different pendrives with the same problems
My box has 32GB Memory and i still have 23GB empty so it has more than enough Storage.
I have 3 boxes, 2 of them have 16.1 and i tried the same pendrive on these 2 boxes and with the same Backup Program Addon to backup - everything was backed up ok!!
It's the box with the 17.1 which is giving me the problems.
On the other 2 boxes when i set the path it comes fine like: usb/sda1/kodi folder, and backup of addons are all there!
On the 17.1 when i set the path it shows as usb/9805.2333/but doesn't backup on the pendrive.
Now i've been reading this thread and in post number 1470 it's said that the Backup is going to Internal Storage and then i 'manually' have to grab it from there and install in the stick/pendrive.
How do i do this please? Where do i find the backup in the Internal Storage? Can someone explain to a 'noob' please?
Thanks lots.
Try it by setting your backup path to /storage/emulated/0/backups. In other words back up to the internal location instead of a USB drive.
RE: [Release] Backup (formerly XBMC Backup) - sarahmic - 2017-08-11
[/quote]
Try it by setting your backup path to /storage/emulated/0/backups. In other words back up to the internal location instead of a USB drive.
[/quote]
Thank you for your answer. Much appreciated.
RE: [Release] Backup (formerly XBMC Backup) - saptadip - 2017-08-13
(2017-08-06, 13:52)saptadip Wrote: I am using the Backup addon to store the backup file to my google drive. But my backup is failing with the below exception:
Code: 23:05:19.159 T:1740612592 NOTICE: script.xbmcbackup-1.0.9: Writing files to: /Kodi Backup/
23:05:19.162 T:1740612592 NOTICE: script.xbmcbackup-1.0.9: Source: /home/osmc/.kodi/temp/
23:05:19.357 T:1740612592 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <class 'httplib.BadStatusLine'>
Error Contents: ''
Traceback (most recent call last):
File "/home/osmc/.kodi/addons/script.xbmcbackup/scheduler.py", line 156, in <module>
BackupScheduler().start()
File "/home/osmc/.kodi/addons/script.xbmcbackup/scheduler.py", line 57, in start
backup.run(XbmcBackup.Backup,True)
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/backup.py", line 278, in run
fileCopied = self.backupFiles(fileManager.getFiles(),self.xbmc_vfs, self.remote_vfs)
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/backup.py", line 482, in backupFiles
wroteFile = dest.put(aFile,dest.root_path + aFile[len(source.root_path):])
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/vfs.py", line 390, in put
parentFolder = self._getGoogleFile(pathList[0])
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/vfs.py", line 464, in _getGoogleFile
file_list = self.drive.ListFile({'q':"title='" + pathList[1] + "' and 'root' in parents and trashed=false"}).GetList()
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/pydrive/apiattr.py", line 155, in GetList
for x in self:
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/pydrive/apiattr.py", line 139, in next
result = self._GetList()
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/pydrive/auth.py", line 54, in _decorated
return decoratee(self, *args, **kwargs)
File "/home/osmc/.kodi/addons/script.xbmcbackup/resources/lib/pydrive/files.py", line 56, in _GetList
self.metadata = self.auth.service.files().list(**dict(self)).execute()
File "/home/osmc/.kodi/addons/script.module.oauth2client/lib/oauth2client/util.py", line 137, in positional_wrapper
return wrapped(*args, **kwargs)
File "/home/osmc/.kodi/addons/script.module.googleapi/lib/apiclient/http.py", line 722, in execute
body=self.body, headers=self.headers)
File "/home/osmc/.kodi/addons/script.module.oauth2client/lib/oauth2client/util.py", line 137, in positional_wrapper
return wrapped(*args, **kwargs)
File "/home/osmc/.kodi/addons/script.module.oauth2client/lib/oauth2client/client.py", line 556, in new_request
redirections, connection_type)
File "/home/osmc/.kodi/addons/script.module.httplib2/lib/httplib2/__init__.py", line 1570, in request
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/home/osmc/.kodi/addons/script.module.httplib2/lib/httplib2/__init__.py", line 1317, in _request
(response, content) = self._conn_request(conn, request_uri, method, body, headers)
File "/home/osmc/.kodi/addons/script.module.httplib2/lib/httplib2/__init__.py", line 1286, in _conn_request
response = conn.getresponse()
File "/usr/lib/python2.7/httplib.py", line 1111, in getresponse
response.begin()
File "/usr/lib/python2.7/httplib.py", line 444, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.7/httplib.py", line 408, in _read_status
raise BadStatusLine(line)
BadStatusLine: ''
-->End of Python script error report<--
The backup zip file is also created on the system:
Code: -rw-r--r-- 1 osmc osmc 518940108 Aug 5 23:05 /home/osmc/.kodi/temp/201708052300.zip
osmc@osmc:~/.kodi/temp$ file /home/osmc/.kodi/temp/201708052300.zip
/home/osmc/.kodi/temp/201708052300.zip: Zip archive data, at least v2.0 to extract
I have already stored the google client id and secret in the addon, so I don't think it's the drive accessibility issue. Also I can see an empty "Kodi Backup" folder is created in my GDrive each time the backup runs. When I checked in google, I found that httplib.BadStatusLine is reported when the http response code returned from the server(GDrive) is not recognized by the application(Backup Add-on)
Did anyone face this problem? How this can be resolved?
Can someone please help?
RE: [Release] Backup (formerly XBMC Backup) - sim099 - 2017-08-19
(2017-02-06, 17:37)robweber Wrote: (2017-02-06, 15:35)sim099 Wrote: I'm having the same issue, but it seems to go away when I uncheck the "Config Files" option.
Posted a debug log here: http://pastebin.com/QWcKvCpC
From the log, it looks like the script is attempting to create the root of my hard drive; "E:\"...
I think you're right. The error you're seeing is related to the "XFILE::CDirectory::Create - Error creating E:\" message. This gets a bit into the code here but the explanation is as follows:
When the addon tries to write a file it passes the file write command to a filesystem handler and gives it the source file and destination on where to copy it. This handler returns a boolean true/false value on if this operation was successful. If False is sent back for any operation in the life of the backup, you see the "some files didn't copy error". Now, for everything except cloud storage destinations this handler is just an alias for the xbmcvfs python library. Basically it's asking Kodi's underlying filesystem code to do the work. That XFILE error is actually originating from Kodi's C++ class.
If you stuck with me this far you're probably thinking - "well then how do you fix it?". I don't have a good answer there. Since Kodi is throwing the error and just passing the boolean value back the Backup Addon is just trusting that the error is valid. In this case it isn't, the file still gets written right? I'll have to investigate and post some questions to Kodi Devs on the issue. I'll reference your log file. Please let me know ASAP if I'm in correct and the files are NOT being written.
Apologies, I'd totally forgotten about my original post and only just came back to the forums to look into something else. I have noticed your PM too, but for some reason the forum won't let me respond directly.
You were asking if I could try replacing backup.py with one that you provided. No problem, I just wanted to confirm where it should be placed and verify that it's still worthwhile doing so. I'm not sure what's changed in the time I've been unresponsive... I've taken a quick look and thin it would go under "%appdata%\Kodi\addons\script.xbmcbackup\resources\lib", right?
Also, it's worth me pointing out that the machine that had the original issue is a running Windows 7, so I can't upgrade Kodi and would be testing on v16.1
EDIT:
I taken a look at the file you were asking me to use and a quick comparison revealed that it was just applying a fix (well adding missing brackets) and adding an extra log line. I applied those changes and attempted another backup. The file that it has trouble with is %appdata%\Kodi\userdata\RssFeeds.xml
The log line:
12:17:50 T:2312 DEBUG: script.xbmcbackup-1.0.9: Error writing: %appdata%\Kodi\userdata\RssFeeds.xml
(I've replaced the actual path with %appdata% to avoid including my username)
RE: [Release] Backup (formerly XBMC Backup) - K--Richard - 2017-08-29
Moving this from another thread,
I keep getting errors when I attempt to backup. Can someone take a look at my log file and help me out?
https://pastebin.com/REAmzZ2N
I followed the PC instructions from reddit: https://www.reddit.com/r/kodi/comments/5...gle_drive/
Maybe this is outdated now that we are on 17.4??
Thanks all.
RE: [Release] Backup (formerly XBMC Backup) - gibxxi - 2017-09-14
(2017-04-04, 22:44)yellow1144 Wrote: Hi Everybody.. Thought I'd try again.. Backup still isn't working for me here. It was then stopped. Any thoughts?
(2017-03-06, 20:05)yellow1144 Wrote: I discovered that backups have been failing for me for over a month. Don't really know why. Does this give anyone any ideas?
It had been working fine. I did recently upgrade to 17.0 but the backups were failing before that.
Running on Win7/64 - 24GB RAM no shortage of hard drive space.
Quote:11:45:49.568 T:16388 DEBUG: script.xbmcbackup-1.0.9: Writing file: -C:\Users\otherUser\AppData\Roaming\Kodi\addons/resource.images.weathericons.hd.animated
11:45:49.569 T:16388 DEBUG: script.xbmcbackup-1.0.9: Writing file: -C:\Users\otherUser\AppData\Roaming\Kodi\addons/resource.images.weathericons.hd.animated/resources
11:45:49.569 T:16388 DEBUG: script.xbmcbackup-1.0.9: Writing file: C:\Users\otherUser\AppData\Roaming\Kodi\addons/resource.images.weathericons.hd.animated/resources/Textures.xbt
11:46:01.264 T:16388 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.MemoryError'>
Traceback (most recent call last):
File "C:\Users\otherUser\AppData\Roaming\Kodi\addons\script.xbmcbackup\default.py", line 73, in <module>
backup.run(mode)
File "C:\Users\otherUser\AppData\Roaming\Kodi\addons\script.xbmcbackup\resources\lib\backup.py", line 256, in run
filesCopied = self.backupFiles(fileGroup['files'],self.xbmc_vfs,self.remote_vfs)
File "C:\Users\otherUser\AppData\Roaming\Kodi\addons\script.xbmcbackup\resources\lib\backup.py", line 482, in backupFiles
wroteFile = dest.put(aFile,dest.root_path + aFile[len(source.root_path):])
File "C:\Users\otherUser\AppData\Roaming\Kodi\addons\script.xbmcbackup\resources\lib\vfs.py", line 97, in put
self.zip.writestr(utils.encode(dest),aFile.read())
File "C:\Program Files (x86)\XBMC\system\python\Lib\zipfile.py", line 1240, in writestr
bytes = co.compress(bytes) + co.flush()
MemoryError
-->End of Python script error report<--
11:46:01.279 T:16796 DEBUG: ------ Window Init (DialogNotification.xml) ------
11:46:01.383 T:16388 INFO: Python script stopped
11:46:01.383 T:16388 DEBUG: Thread LanguageInvoker 16388 terminating
11:46:01.652 T:16796 DEBUG: ------ Window Deinit (DialogExtendedProgressBar.xml) -----
Also, when backup fails the notices at the top of my screen showing which files are being backed up just stays there. The backup has crashed but the notice is there. It is stuck showing that it is adding - Addons/Resource.images.weathericons.HD.Animated/REsources.
That folder contains a 169MB Textures file. This was only added in the last week, long after the backups were failing.
I'm getting the same issue as yellow1144, but for a different file (or files). For me it's crashing on adding the downloaded add-on packages, the largest of which is: 'resource.images.weatherfanart.multi-0.0.6.zip' at 80MB (82,013KB as reported by Windows Explorer). There are several other large-ish packages in the folder (depending on your perspective), ranging between 20-40MB on average.
Disabling compression results in a successful (albeit slower) backup. However, as yellow1144 himself pointed out, it's taking up a considerable amount more space, than the zip file. And being stored on a network share, the small file transfers bog down over network access making the backup operation longer.
Here's the log snippet from the latest test (With the packages folder untouched):
Code: 06:46:55.457 T:17428 NOTICE: script.xbmcbackup-1.0.9: Starting
06:47:11.418 T:10808 NOTICE: Previous line repeats 1 times.
06:47:11.418 T:10808 NOTICE: script.xbmcbackup-1.0.9: Local Dir: D:/Kodi Media Center/portable_data/
06:47:11.418 T:10808 NOTICE: script.xbmcbackup-1.0.9: Remote Dir: 201709140647/
06:47:11.424 T:10808 NOTICE: script.xbmcbackup-1.0.9: Mode - Backup
06:47:11.427 T:10808 NOTICE: script.xbmcbackup-1.0.9: Creating Files List
06:47:13.129 T:10808 NOTICE: script.xbmcbackup-1.0.9: Writing files to: 201709140647/
06:47:13.129 T:10808 NOTICE: script.xbmcbackup-1.0.9: Source: D:/Kodi Media Center/portable_data/
06:47:19.359 T:10808 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'exceptions.MemoryError'>
Traceback (most recent call last):
File "D:\Kodi Media Center\portable_data\addons\script.xbmcbackup\default.py", line 73, in <module>
backup.run(mode)
File "D:\Kodi Media Center\portable_data\addons\script.xbmcbackup\resources\lib\backup.py", line 256, in run
filesCopied = self.backupFiles(fileGroup['files'],self.xbmc_vfs,self.remote_vfs)
File "D:\Kodi Media Center\portable_data\addons\script.xbmcbackup\resources\lib\backup.py", line 482, in backupFiles
wroteFile = dest.put(aFile,dest.root_path + aFile[len(source.root_path):])
File "D:\Kodi Media Center\portable_data\addons\script.xbmcbackup\resources\lib\vfs.py", line 97, in put
self.zip.writestr(utils.encode(dest),aFile.read())
File "D:\Kodi Media Center\system\python\Lib\zipfile.py", line 1243, in writestr
bytes = co.compress(bytes) + co.flush()
MemoryError
-->End of Python script error report<--
FWIW: I did another test by clearing out the packages folder, and that also worked fine (with compression enabled). However, as soon as the culprit package gets updated, it's highly likely that the issue will return.
Regards,
Dan/Gib.
RE: [Release] Backup (formerly XBMC Backup) - Jayphen - 2017-10-09
I am trying to back up to Dropbox on Raspbian Stretch, but getting an error regarding SSL certificate verificaiton failing:
https://pastebin.com/kXGtf5WG
RE: [Release] Backup (formerly XBMC Backup) - Rich2222 - 2017-10-10
I am trying to get Kodi Backup to work with Google Drive. I have gDrive installed in Kodi and from the gDrive addon I can see the contents of my Google Drive. I have the Client ID & Client Secret information populated in the Backup configuration.
I have a Google OAUTH2 Code but when I use this code in the Backup Addon (“Input the Validation code after authorizing this app”) I get a Backup Error.
The URL authorisation part of the log (https://paste.ubuntu.com/25713281/) says
<< Google Drive Authorize URL: https://accounts.google.com/o/oauth2/auth?scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdrive.file&redirect_uri=urn%3Aietf%3Awg%3Aoauth%3A2.0%3Aoob&response_type=code&client_id=570214593233-0b0617hn6fo47nj95bj0sj192gaofd.apps.googleusercontent.com&access_type=offline >>
Authentication error is << AuthenticationError: OAuth2 code exchange failed: invalid_requestMissing required parameter: code >>
I must be missing something obvious here and have been going at this for a couple of days now……………
Advice please!!!!
|