UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?

[amg_666]

@simatec Nein, Config neu speichern reicht nicht aus:

host.iobroker
	2022-03-29 16:54:50.438	info	Restart adapter system.adapter.backitup.0 because enabled
host.iobroker
	2022-03-29 16:54:50.438	error	instance system.adapter.backitup.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker
	2022-03-29 16:54:50.438	error	Caught by controller[0]: at processImmediate (internal/timers.js:466:21)
host.iobroker
	2022-03-29 16:54:50.438	error	Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.backitup/main.js:1342:13)
host.iobroker
	2022-03-29 16:54:50.438	error	Caught by controller[0]: at detectLatestBackupFile (/opt/iobroker/node_modules/iobroker.backitup/main.js:1093:31)
host.iobroker
	2022-03-29 16:54:50.436	error	Caught by controller[0]: at Array.map (<anonymous>)
host.iobroker
	2022-03-29 16:54:50.436	error	Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.backitup/main.js:1093:46
host.iobroker
	2022-03-29 16:54:50.436	error	Caught by controller[0]: at new Promise (<anonymous>)
host.iobroker
	2022-03-29 16:54:50.436	error	Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.backitup/main.js:1095:17
host.iobroker
	2022-03-29 16:54:50.435	error	Caught by controller[0]: at module.exports (/opt/iobroker/node_modules/iobroker.backitup/lib/list.js:76:36)
host.iobroker
	2022-03-29 16:54:50.435	error	Caught by controller[0]: at Object.list (/opt/iobroker/node_modules/iobroker.backitup/lib/list/dropbox.js:15:156)
host.iobroker
	2022-03-29 16:54:50.435	error	Caught by controller[0]: TypeError: Cannot read property 'dropboxAccessJson' of undefined
host.iobroker
	2022-03-29 16:54:50.435	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
backitup.0
	2022-03-29 16:54:49.886	debug	FTP: connected.
backitup.0
	2022-03-29 16:54:49.816	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
backitup.0
	2022-03-29 16:54:49.815	debug	Plugin sentry destroyed
backitup.0
	2022-03-29 16:54:49.814	info	terminating
backitup.0
	2022-03-29 16:54:49.813	info	cleaned everything up...
backitup.0
	2022-03-29 16:54:49.798	error	Cannot read property 'dropboxAccessJson' of undefined
backitup.0
	2022-03-29 16:54:49.798	error	TypeError: Cannot read property 'dropboxAccessJson' of undefined at Object.list (/opt/iobroker/node_modules/iobroker.backitup/lib/list/dropbox.js:15:156) at module.exports (/opt/iobroker/node_modules/iobroker.backitup/lib/list.js:76:36) at /opt/iobroker/node_modules/iobroker.backitup/main.js:1095:17 at new Promise (<anonymous>) at /opt/iobroker/node_modules/iobroker.backitup/main.js:1093:46 at Array.map (<anonymous>) at detectLatestBackupFile (/opt/iobroker/node_modules/iobroker.backitup/main.js:1093:31) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.backitup/main.js:1342:13) at processImmediate (internal/timers.js:466:21)
backitup.0
	2022-03-29 16:54:49.792	error	unhandled promise rejection: Cannot read property 'dropboxAccessJson' of undefined
backitup.0
	2022-03-29 16:54:49.791	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
backitup.0
	2022-03-29 16:54:49.450	info	[ccu] backup was activated at 01:30 every 3 day(s)
backitup.0
	2022-03-29 16:54:49.398	info	[iobroker] backup was activated at 02:00 every 1 day(s)
backitup.0
	2022-03-29 16:54:49.295	debug	Backitup has recognized a linux system
backitup.0
	2022-03-29 16:54:49.259	info	starting. Version 2.4.1 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 4.0.21
backitup.0
	2022-03-29 16:54:48.593	debug	Plugin sentry Initialize Plugin (enabled=true)
host.iobroker
	2022-03-29 16:54:46.824	info	instance system.adapter.backitup.0 started with pid 8627
javascript.0
	2022-03-29 16:54:26.949	info	script.js.Devicemanagement.Triangulation: 0
host.iobroker
	2022-03-29 16:54:16.624	info	Restart adapter system.adapter.backitup.0 because enabled
host.iobroker
	2022-03-29 16:54:16.623	error	instance system.adapter.backitup.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
host.iobroker
	2022-03-29 16:54:16.623	error	Caught by controller[0]: at processImmediate (internal/timers.js:466:21)
host.iobroker
	2022-03-29 16:54:16.623	error	Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.backitup/main.js:1342:13)
host.iobroker
	2022-03-29 16:54:16.623	error	Caught by controller[0]: at detectLatestBackupFile (/opt/iobroker/node_modules/iobroker.backitup/main.js:1093:31)
host.iobroker
	2022-03-29 16:54:16.623	error	Caught by controller[0]: at Array.map (<anonymous>)
host.iobroker
	2022-03-29 16:54:16.623	error	Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.backitup/main.js:1093:46
host.iobroker
	2022-03-29 16:54:16.622	error	Caught by controller[0]: at new Promise (<anonymous>)
host.iobroker
	2022-03-29 16:54:16.622	error	Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.backitup/main.js:1095:17
host.iobroker
	2022-03-29 16:54:16.622	error	Caught by controller[0]: at module.exports (/opt/iobroker/node_modules/iobroker.backitup/lib/list.js:76:36)
host.iobroker
	2022-03-29 16:54:16.622	error	Caught by controller[0]: at Object.list (/opt/iobroker/node_modules/iobroker.backitup/lib/list/dropbox.js:15:156)
host.iobroker
	2022-03-29 16:54:16.622	error	Caught by controller[0]: TypeError: Cannot read property 'dropboxAccessJson' of undefined
host.iobroker
	2022-03-29 16:54:16.621	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
backitup.0
	2022-03-29 16:54:16.067	debug	FTP: connected.
backitup.0
	2022-03-29 16:54:15.990	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason
backitup.0
	2022-03-29 16:54:15.990	debug	Plugin sentry destroyed
backitup.0
	2022-03-29 16:54:15.989	info	terminating
backitup.0
	2022-03-29 16:54:15.988	info	cleaned everything up...
backitup.0
	2022-03-29 16:54:15.973	error	Cannot read property 'dropboxAccessJson' of undefined
backitup.0
	2022-03-29 16:54:15.972	error	TypeError: Cannot read property 'dropboxAccessJson' of undefined at Object.list (/opt/iobroker/node_modules/iobroker.backitup/lib/list/dropbox.js:15:156) at module.exports (/opt/iobroker/node_modules/iobroker.backitup/lib/list.js:76:36) at /opt/iobroker/node_modules/iobroker.backitup/main.js:1095:17 at new Promise (<anonymous>) at /opt/iobroker/node_modules/iobroker.backitup/main.js:1093:46 at Array.map (<anonymous>) at detectLatestBackupFile (/opt/iobroker/node_modules/iobroker.backitup/main.js:1093:31) at Immediate.<anonymous> (/opt/iobroker/node_modules/iobroker.backitup/main.js:1342:13) at processImmediate (internal/timers.js:466:21)
backitup.0
	2022-03-29 16:54:15.966	error	unhandled promise rejection: Cannot read property 'dropboxAccessJson' of undefined
backitup.0
	2022-03-29 16:54:15.966	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

[sigi234]

@amg_666 sagte in Test Adapter Backitup v2.4.x:

Nein, Config neu speichern reicht nicht aus:

Dito, habe den Adapter mal gestoppt.

[Matt77CHE]

Habe erstmal auch eine Instanz geupdated - Habe dann gemerkt, dass diese Instanz vom Host gestoppt wurde wegen on/off (error-meldungen).
bin wieder auf die 2.3.5 zurück; läuft wieder sauber...

[simatec]

Ab sofort steht auf Github und in kürze auch im latest die Version 2.4.2 zur Verfügung.

Changelog

2.4.2 (2022-03-29)

• (simatec) Bugfixes Dropbox

[amg_666]

@simatec und die sieht gut aus :-) Bei mir keine Auffälligkeiten mehr im Log und Adapter ist grün,

Hier noch das Log zur Info

backitup.0
	2022-03-29 17:23:12.031	debug	detect last backup file: iobroker_2022_03_29-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.028	debug	detect backup file 80 from ftp: iobroker_2022_03_29-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.028	debug	detect backup file 79 from ftp: iobroker_2022_03_28-20_08_55_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.027	debug	detect backup file 78 from ftp: iobroker_2022_03_28-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.027	debug	detect backup file 77 from ftp: iobroker_2022_03_27-03_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.027	debug	detect backup file 76 from ftp: iobroker_2022_03_26-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.026	debug	detect backup file 75 from ftp: iobroker_2022_03_25-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.026	debug	detect backup file 74 from ftp: iobroker_2022_03_24-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.026	debug	detect backup file 73 from ftp: iobroker_2022_03_23-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.026	debug	detect backup file 72 from ftp: iobroker_2022_03_22-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.025	debug	detect backup file 71 from ftp: iobroker_2022_03_21-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.024	debug	detect backup file 70 from ftp: iobroker_2022_03_20-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.024	debug	detect backup file 69 from ftp: iobroker_2022_03_19-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.024	debug	detect backup file 68 from ftp: iobroker_2022_03_18-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.023	debug	detect backup file 67 from ftp: iobroker_2022_03_17-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.023	debug	detect backup file 66 from ftp: iobroker_2022_03_13-11_01_19_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.023	debug	detect backup file 65 from ftp: iobroker_2022_03_01-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.023	debug	detect backup file 64 from ftp: iobroker_2022_02_28-21_02_32_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.022	debug	detect backup file 63 from ftp: iobroker_2022_02_28-20_35_11_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.022	debug	detect backup file 62 from ftp: iobroker_2022_02_26-16_29_43_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.021	debug	detect backup file 61 from ftp: iobroker_2022_02_23-10_24_30_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.021	debug	detect backup file 60 from ftp: iobroker_2022_02_21-08_58_53_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.021	debug	detect backup file 59 from ftp: iobroker_2022_02_13-20_03_52_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.021	debug	detect backup file 58 from ftp: iobroker_2022_02_12-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.020	debug	detect backup file 57 from ftp: iobroker_2022_02_11-14_48_38_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.019	debug	detect backup file 56 from ftp: iobroker_2022_02_11-14_42_27_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.019	debug	detect backup file 55 from ftp: iobroker_2022_02_02-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.019	debug	detect backup file 54 from ftp: iobroker_2022_02_01-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.019	debug	detect backup file 53 from ftp: iobroker_2022_01_31-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.018	debug	detect backup file 52 from ftp: iobroker_2022_01_18-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.018	debug	detect backup file 51 from ftp: iobroker_2022_01_13-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.018	debug	detect backup file 50 from ftp: iobroker_2022_01_12-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.017	debug	detect backup file 49 from ftp: iobroker_2022_01_11-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.017	debug	detect backup file 48 from ftp: iobroker_2022_01_10-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.017	debug	detect backup file 47 from ftp: iobroker_2021_12_27-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.017	debug	detect backup file 46 from ftp: iobroker_2021_12_23-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.016	debug	detect backup file 45 from ftp: iobroker_2021_12_21-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.016	debug	detect backup file 44 from ftp: iobroker_2021_12_15-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.015	debug	detect backup file 43 from ftp: iobroker_2021_11_30-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.015	debug	detect backup file 42 from ftp: iobroker_2021_11_29-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.014	debug	detect backup file 41 from ftp: iobroker_2021_11_25-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.014	debug	detect backup file 40 from ftp: iobroker_2021_11_19-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.014	debug	detect backup file 39 from ftp: iobroker_2021_11_18-21_44_52_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.014	debug	detect backup file 38 from ftp: iobroker_2021_11_16-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.013	debug	detect backup file 37 from ftp: iobroker_2021_11_15-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.013	debug	detect backup file 36 from ftp: iobroker_2021_11_12-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.013	debug	detect backup file 35 from ftp: iobroker_2021_11_04-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.013	debug	detect backup file 34 from ftp: iobroker_2021_10_29-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.011	debug	detect backup file 33 from ftp: iobroker_2021_10_28-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.011	debug	detect backup file 32 from ftp: iobroker_2021_10_25-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.011	debug	detect backup file 31 from ftp: iobroker_2021_10_24-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.010	debug	detect backup file 30 from ftp: iobroker_2021_10_23-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.010	debug	detect backup file 29 from ftp: iobroker_2021_10_22-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.010	debug	detect backup file 28 from ftp: iobroker_2021_10_21-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.010	debug	detect backup file 27 from ftp: iobroker_2021_10_20-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.009	debug	detect backup file 26 from ftp: iobroker_2021_10_14-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.009	debug	detect backup file 25 from ftp: iobroker_2021_10_10-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.009	debug	detect backup file 24 from ftp: iobroker_2021_10_09-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.008	debug	detect backup file 23 from ftp: iobroker_2021_10_08-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.008	debug	detect backup file 22 from ftp: iobroker_2021_10_07-11_22_48_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.008	debug	detect backup file 21 from ftp: iobroker_2021_10_07-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.008	debug	detect backup file 20 from ftp: iobroker_2021_10_06-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.007	debug	detect backup file 19 from ftp: iobroker_2021_10_02-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.007	debug	detect backup file 18 from ftp: iobroker_2021_09_30-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.007	debug	detect backup file 17 from ftp: iobroker_2021_09_29-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.006	debug	detect backup file 16 from ftp: iobroker_2021_09_17-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.006	debug	detect backup file 15 from ftp: iobroker_2021_09_13-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.006	debug	detect backup file 14 from ftp: iobroker_2021_09_12-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.006	debug	detect backup file 13 from ftp: iobroker_2021_09_10-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.005	debug	detect backup file 12 from ftp: iobroker_2021_09_01-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.005	debug	detect backup file 11 from ftp: iobroker_2021_08_26-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.005	debug	detect backup file 10 from ftp: iobroker_2021_08_20-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.004	debug	detect backup file 9 from ftp: iobroker_2021_08_16-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.004	debug	detect backup file 8 from ftp: iobroker_2021_08_15-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.004	debug	detect backup file 7 from ftp: iobroker_2021_08_14-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.003	debug	detect backup file 6 from ftp: iobroker_2021_08_13-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.003	debug	detect backup file 5 from ftp: iobroker_2021_08_12-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.003	debug	detect backup file 4 from ftp: iobroker_2021_08_11-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.002	debug	detect backup file 3 from ftp: iobroker_2021_08_10-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.002	debug	detect backup file 2 from ftp: iobroker_2021_08_09-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:12.001	debug	detect backup file 1 from ftp: iobroker_2021_08_08-02_00_10_backupiobroker.tar.gz
backitup.0
	2022-03-29 17:23:09.692	debug	FTP: connected.
backitup.0
	2022-03-29 17:23:09.168	info	[ccu] backup was activated at 01:30 every 3 day(s)
backitup.0
	2022-03-29 17:23:09.112	info	[iobroker] backup was activated at 02:00 every 1 day(s)
backitup.0
	2022-03-29 17:23:09.018	debug	Backitup has recognized a linux system
backitup.0
	2022-03-29 17:23:08.975	info	starting. Version 2.4.2 (non-npm: simatec/ioBroker.backitup) in /opt/iobroker/node_modules/iobroker.backitup, node: v14.19.0, js-controller: 4.0.21

[sigi234]

@simatec sagte in Test Adapter Backitup v2.4.x:

Ab sofort steht auf Github und in kürze auch im latest die Version 2.4.2 zur Verfügung.

Changelog

2.4.2 (2022-03-29)

• (simatec) Bugfixes Dropbox

Läuft wieder ohne Fehler. :+1:

[simatec]

Ab sofort steht auf Github und in kürze auch im latest die Version 2.4.3 zur Verfügung.

Changelog

2.4.3 (2022-03-29)

• (simatec) Bugfixes Dropbox
• (simatec) try/catch options added
• (simatec) code verifier check for Dropbox oAuth

[JB_Sullivan]

Muss das mit sentry so?

backitup.0
11204	2022-03-30 08:03:04.496	info	[iobroker] backup was activated at 02:00 every 1 day(s)

backitup.0
11204	2022-03-30 08:03:04.237	debug	Backitup has recognized a win32 system

backitup.0
11204	2022-03-30 08:03:04.215	info	starting. Version 2.4.2 in C:/iobroker/GLT/node_modules/iobroker.backitup, node: v14.16.0, js-controller: 4.0.21

backitup.0
11204	2022-03-30 08:03:03.857	debug	Plugin sentry destroyed because not initialized correctly

backitup.0
11204	2022-03-30 08:03:03.848	debug	Plugin sentry Do not initialize Plugin (enabled=false)

backitup.0
11204	2022-03-30 08:03:03.429	debug	States connected to redis: 127.0.0.1:9000

backitup.0
11204	2022-03-30 08:03:03.340	debug	States create User PubSub Client

backitup.0
11204	2022-03-30 08:03:03.339	debug	States create System PubSub Client

backitup.0
11204	2022-03-30 08:03:03.310	debug	Redis States: Use Redis connection: 127.0.0.1:9000

backitup.0
11204	2022-03-30 08:03:03.270	debug	Objects connected to redis: 127.0.0.1:9001

backitup.0
11204	2022-03-30 08:03:03.264	debug	Objects client initialize lua scripts

backitup.0
11204	2022-03-30 08:03:03.158	debug	Objects create User PubSub Client

backitup.0
11204	2022-03-30 08:03:03.157	debug	Objects create System PubSub Client

backitup.0
11204	2022-03-30 08:03:03.156	debug	Objects client ready ... initialize now

backitup.0
11204	2022-03-30 08:03:03.110	debug	Redis Objects: Use Redis connection: 127.0.0.1:9001

[simatec]

@jb_sullivan Dann hast du sentry sicher für Backitup deaktiviert

[legro]

Die Erfahrungen, die ich mit den Entwicklungen im ZigBee-Adapter gemacht habe, lassen mich aufschrecken. Ich frage mich, wie kann ich mein System so sichern, dass ich es exakt wiederherstellen kann?

Sehe ich das richtig, dass Backitup den Programmcode gar nicht sichert, sondern nur dessen Wiederherstellung, indem die benötigten Teile aus dem GitHub geladen werden? Jedenfalls erscheinen mir die erzeugten Backups viel zu klein.

Wenn, wie im ZigBee-Adapter geschehen, alte, noch funktionierende Versionen gar nicht mehr verfügbar sind, so sollte Backitup doch wohl beim Wiederherstellen scheitern.

Somit bliebe dann wohl nur, eine Software à la Apple Pi Baker zu verwenden, die ein eins-zu-eins Abbild des Speichermediums (SD, SSD) erstellt.

Schiebe ich unberechtigt Panik oder ist dem wirklich so, wie hier von mir vermutet?

[Thomas Braun]

@legro sagte in Test Adapter Backitup v2.4.x:

Jedenfalls erscheinen mir die erzeugten Backups viel zu klein.

Es wird (mehr oder weniger) der Bauplan gesichert, nicht das komplette Haus.
Das reicht auch eigentlich aus, gibt also keinen Grund irgendeine 'Panik' zu schieben.

[simatec]

@legro Da liegst du falsch ... Im Gegenteil. das von Backitup erstellte Backup stellt dir ein sauberes und fehlerfreies System wieder her ...

[legro]

@thomas-braun, @simatec

Vielen Dank für eure Hinweise. Leider beruhigen sie mich nicht so sehr, wie ich es mir wünschen würde.

Wenn der Code der Adapter nicht im Backup gesichert wird, von wo wird dieser dann wiederhergestellt?

In dem oben verlinkten Beispiel zum ZigBee-Adapter für BITRON Sirenen war die letzte für meine Geräte noch funktionierende Version die 1.6.0. Nicht einmal die Entwickler hatten diese Version noch zur Hand. Woher nimmt BackItUp denn in diesem Fall den Programmcode?

Mittlerweile hat @Asgothian eine Testversion in seinem Fork auf GitHub bereitgestellt, mit der ich mein Alarmsystem aus BITRON Geräten wieder zum Laufen bekomme.

[Thomas Braun]

@legro sagte in Test Adapter Backitup v2.4.x:

Wenn der Code der Adapter nicht im Backup gesichert wird, von wo wird dieser dann wiederhergestellt?

Aus den Repositories.

[simatec]

@legro Deine Aussage kann ich nicht nachvollziehen.
Alle Versionen liegen auf npm und du kannst diese jederzeit installieren

https://www.npmjs.com/package/iobroker.zigbee

[legro]

@simatec

Irgendwie habe ich das Gefühl, dass wir aneinander vorbei argumentieren.

Das von mir ins Spiel gebrachte Beispiel hätte die Wiederstellung des ZigBee Adapters zurück auf die Version 1.6.0 erfordert. Aber diese ist anscheinend nicht mehr verfügbar zu sein.

Für mich sieht das noch immer so aus, dass man die Wahl zwischen zwei Optionen hat, wobei jede ihre ureigenen Vor- und Nachteile zu haben scheint. Verwende ich etwa Apple Pi Baker, so wird auch der Programmcode eingefroren und bei der Wiederherstellung gehen mir dafür alle zwischenzeitlich angefallenen Daten, Einstellungen und Konfigurationen verloren. Hingegen bleiben mir bei BackItUp alle Daten, Konfigurationen und Einstellungen erhalten, dafür geht jedoch alte Programmcode verloren.

Oder sehe ich bloß noch immer keinen Weg, wie ich die hier von mir befürchteten Nachteile vermeiden kann? Derzeit fahre ich daher zweigleisig: Ich verwende BackItUp und ApplePiBaker.

Um bei meinem Dilemma zu bleiben: Leider habe ich kein Backup mit ZigBee 1.6.0 aufbewahrt )weder von BackItUp noch von ApplePiBaker), sodass ich das hätte ausprobieren können.

[Thomas Braun]

@legro

iobroker upgrade adaptername@versionsnummer

schaufelt dir eine genaue Version auf das System.

[MCU]

@legro Zur Info es gibt immer die Commits zum Projekt, auch von v1.6.0:

Welches man nutzen muss, um die v1.6.0 zurückzusichern, muss man probieren. Sie ist auf jeden Fall da.
Stimmt:

 npm show iobroker.zigbee versions

[
  '0.5.0',  '0.5.2',  '0.5.3',  '0.5.4',  '0.5.5',
  '0.5.6',  '0.5.7',  '0.5.8',  '0.6.0',  '0.7.0',
  '0.7.1',  '0.7.3',  '0.7.5',  '0.7.6',  '0.7.7',
  '0.8.0',  '0.9.0',  '0.9.1',  '0.9.2',  '0.10.0',
  '0.10.1', '0.10.2', '0.10.3', '0.11.0', '0.11.1',
  '0.11.2', '0.11.3', '0.11.5', '1.0.0',  '1.0.1',
  '1.0.2',  '1.0.3',  '1.0.4',  '1.1.0',  '1.1.1',
  '1.2.0',  '1.2.1',  '1.3.0',  '1.3.1',  '1.4.0',
  '1.4.1',  '1.4.2',  '1.4.4',  '1.5.0',  '1.5.1',
  '1.5.2',  '1.5.3',  '1.5.5',  '1.5.6',  '1.6.0',
  '1.6.3',  '1.6.6',  '1.6.8',  '1.6.12', '1.6.14',
  '1.6.15', '1.6.16'

[Kueppert]

@legro ansonsten einfach Proxmox nutzen und die VM/LXC jeden Tag sichern. Ich nutze beides...Backitup und die Sicherung des gesamten Systems

[legro]

@thomas-braun said in Test Adapter Backitup v2.4.x:

iobroker upgrade adaptername@versionsnummer

schaufelt dir eine genaue Version auf das System.

Vielen Dank für deinen Hinweis. Genau dies hatte ich jedoch ohne Erfolg versucht und dachte daher, dass die Version 1.6.0 tatsächlich nicht mehr verfügbar ist - zumal sogar Artec und Asgothian meinten, dass diese Versionen nicht mehr verfügbar seien.:confused:

Das System scheint so seine Tücken zu haben. Die von @Asgothian in seinem Fork auf GitHub zu Verfügung gestellte Beta (1.6.17) ließ sich auch zunächst nicht installieren; erst der dritte Versuch führte zum Erfolg.

Zur Sicherheit habe ich nun meine npm Version von 6.14.15 auf 8.6.0 aktualisiert.