Ich nehms zurück, nach einem Neustart geht nun alles. Vielen lieben Dank für eure Unterstützung.

@andre said in [Synology Docker]Iobroker startet nicht (no database):

iobroker host this

Hab ich getan

root@iobroker-neu:/opt/iobroker# maint on -y                                                                                                                                                        
You are now going to stop ioBroker and activating maintenance mode for this container.                                                                                                              
This command was already confirmed by -y or --yes option.                                                                                                                                           
Activating maintenance mode...                                                                                                                                                                      
Done.                                                                                                                                                                                               
Stopping ioBroker...                                                                                                                                                                                
Done.                                                                                                                                                                                               
root@iobroker-neu:/opt/iobroker# iobroker host this                                                                                                                                                 
Host "iobroker" successfully renamed to "iobroker-neu".                                                                                                                                             
The host for instance "system.adapter.admin.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                   
The host for instance "system.adapter.discovery.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                               
The host for instance "system.adapter.backitup.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                
The host for instance "system.adapter.daswetter.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                               
The host for instance "system.adapter.hm-rpc.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                  
The host for instance "system.adapter.hm-rpc.1" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                  
The host for instance "system.adapter.ical.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                    
The host for instance "system.adapter.icons-mfd-svg.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                           
The host for instance "system.adapter.slideshow.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                               
The host for instance "system.adapter.slideshow.1" was changed from "iobroker-neu" to "iobroker-neu".                                                                                               
The host for instance "system.adapter.slideshow.2" was changed from "iobroker-neu" to "iobroker-neu".                                                                                               
The host for instance "system.adapter.synology.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                
The host for instance "system.adapter.tankerkoenig.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                            
The host for instance "system.adapter.trashschedule.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                           
The host for instance "system.adapter.vis-bars.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                
The host for instance "system.adapter.vis-canvas-gauges.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                       
The host for instance "system.adapter.vis-fancyswitch.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                         
The host for instance "system.adapter.vis-hqwidgets.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                           
The host for instance "system.adapter.vis-inventwo.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                            
The host for instance "system.adapter.vis-jqui-mfd.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                            
The host for instance "system.adapter.vis-justgage.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                            
The host for instance "system.adapter.vis-keyboard.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                            
The host for instance "system.adapter.vis-players.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                             
The host for instance "system.adapter.vis-rgraph.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                              
The host for instance "system.adapter.vis-timeandweather.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                      
The host for instance "system.adapter.vis-weather.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                             
The host for instance "system.adapter.vis.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                     
The host for instance "system.adapter.web.0" was changed from "iobroker-neu" to "iobroker-neu".                                                                                                     
root@iobroker-neu:/opt/iobroker#  

Es hat funktioniert, vielen herzlichen Dank. Die Web Oberfläche ist wieder erreichbar.

Nun noch eine Frage, warum läuft das VIS nicht mehr oder soll ich dazu besser ein neuer Thread eröffnen?

Edit:
Es sind noch weitere Instanzen betroffen (Tankerkönig z.B.) mit dem gleichen Fehler.

Hallo,

Vielen Dank erst ma für euere tolle Unterstützung.
Es tut mir leid, dass ich so spät antworte. Bin leider nicht früher dazu gekommen, das Volume umzustellen. Habe es nun getan aber nach dem Einspielen des Backups geht es weiterhin nicht. Set cap werden laut Log aber richtig gesetzt, das Problem scheint behoben zu sein.

Nun habe ich folgendes Problem

2022-07-24 07:53:34.161  - info: host.iobroker-neu iobroker.js-controller version 4.0.23 js-controller starting
2022-07-24 07:53:34.176  - info: host.iobroker-neu Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-07-24 07:53:34.178  - info: host.iobroker-neu hostname: iobroker-neu, node: v14.20.0
2022-07-24 07:53:34.180  - info: host.iobroker-neu ip addresses: 172.17.0.2
2022-07-24 07:53:34.794  - info: host.iobroker-neu connected to Objects and States
2022-07-24 07:53:34.842  - info: host.iobroker-neu Node.js version has changed from unknown to 14.20.0
2022-07-24 07:53:34.974  - info: host.iobroker-neu added notifications configuration of host
2022-07-24 07:53:35.089  - info: host.iobroker-neu Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
2022-07-24 07:53:35.545  - info: host.iobroker-neu 3 instances found
2022-07-24 07:53:35.566  - info: host.iobroker-neu starting 3 instances
2022-07-24 07:53:35.659  - info: host.iobroker-neu instance system.adapter.admin.0 started with pid 1090
2022-07-24 07:53:36.001  - info: host.iobroker-neu Created UUID: af6d0dcd-989c-495f-b9e9-a9de5cee9b2f
2022-07-24 07:53:39.026  - info: admin.0 (1090) starting. Version 5.3.8 in /opt/iobroker/node_modules/iobroker.admin, node: v14.20.0, js-controller: 4.0.23
2022-07-24 07:53:39.114  - info: admin.0 (1090) requesting all states
2022-07-24 07:53:39.115  - info: admin.0 (1090) requesting all objects
2022-07-24 07:53:39.294  - info: admin.0 (1090) received all objects
2022-07-24 07:53:39.349  - info: admin.0 (1090) Request actual repository...
2022-07-24 07:53:39.371  - info: host.iobroker-neu Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
2022-07-24 07:53:39.536  - info: admin.0 (1090) http server listening on port 8081
2022-07-24 07:53:39.537  - info: admin.0 (1090) Use link "http://localhost:8081" to configure.
2022-07-24 07:53:39.727  - info: host.iobroker-neu instance system.adapter.discovery.0 started with pid 1117
2022-07-24 07:53:39.754  - warn: admin.0 (1090) Repository cannot be read: Active repo - stable
2022-07-24 07:53:39.773  - warn: admin.0 (1090) Active repository "stable cannot be read
2022-07-24 07:53:43.240  - info: admin.0 (1090) Repository received successfully.
2022-07-24 07:53:43.630  - info: host.iobroker-neu instance system.adapter.backitup.0 started with pid 1128
2022-07-24 07:53:43.934  - info: discovery.0 (1117) starting. Version 3.0.3 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.20.0, js-controller: 4.0.23
2022-07-24 07:53:46.842  - info: backitup.0 (1128) starting. Version 2.4.6 in /opt/iobroker/node_modules/iobroker.backitup, node: v14.20.0, js-controller: 4.0.23
2022-07-24 07:53:46.974  - info: backitup.0 (1128) [iobroker] backup was activated at 02:40 every 1 day(s)
2022-07-24 07:58:23.217  - info: backitup.0 (1128) cleaned everything up...
2022-07-24 07:58:23.216  - info: host.iobroker-neu received SIGTERM
2022-07-24 07:58:23.226  - info: admin.0 (1090) terminating http server on port 8081
2022-07-24 07:58:23.236  - info: host.iobroker-neu stopInstance system.adapter.admin.0 (force=false, process=true)
2022-07-24 07:58:23.239  - info: host.iobroker-neu stopInstance system.adapter.discovery.0 (force=false, process=true)
2022-07-24 07:58:23.240  - info: host.iobroker-neu stopInstance system.adapter.backitup.0 (force=false, process=true)
2022-07-24 07:58:23.273  - info: admin.0 (1090) Got terminate signal TERMINATE_YOURSELF
2022-07-24 07:58:23.275  - info: discovery.0 (1117) Got terminate signal TERMINATE_YOURSELF
2022-07-24 07:58:23.278  - info: backitup.0 (1128) Got terminate signal TERMINATE_YOURSELF
2022-07-24 07:58:23.284  - info: discovery.0 (1117) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-07-24 07:58:23.286  - info: admin.0 (1090) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-07-24 07:58:23.289  - info: host.iobroker-neu stopInstance system.adapter.admin.0 send kill signal
2022-07-24 07:58:23.295  - info: host.iobroker-neu stopInstance system.adapter.discovery.0 send kill signal
2022-07-24 07:58:23.296  - info: host.iobroker-neu stopInstance system.adapter.backitup.0 send kill signal
2022-07-24 07:58:23.330  - info: backitup.0 (1128) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2022-07-24 07:58:23.903  - info: host.iobroker-neu instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-07-24 07:58:23.947  - info: host.iobroker-neu instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-07-24 07:58:23.974  - info: host.iobroker-neu instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2022-07-24 07:58:23.976  - info: host.iobroker-neu All instances are stopped.
2022-07-24 07:58:24.096  - info: host.iobroker-neu terminated
2022-07-24 08:02:37.840  - info: host.iobroker iobroker.js-controller version 4.0.23 js-controller starting
2022-07-24 08:02:37.856  - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-07-24 08:02:37.858  - info: host.iobroker hostname: iobroker, node: v14.20.0
2022-07-24 08:02:37.859  - info: host.iobroker ip addresses: 172.17.0.2
2022-07-24 08:02:39.837  - info: host.iobroker connected to Objects and States
2022-07-24 08:02:39.928  - info: host.iobroker Node.js version has changed from unknown to 14.20.0
2022-07-24 08:02:39.969  - info: host.iobroker added notifications configuration of host
2022-07-24 08:02:40.803  - info: host.iobroker Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
2022-07-24 08:02:40.915  - info: host.iobroker Delete host system.host.iobroker-neu
2022-07-24 08:02:41.020  - info: host.iobroker 28 instances found
2022-07-24 08:02:41.049  - warn: host.iobroker does not start any instances on this host
2022-07-24 08:03:57.749  - info: host.iobroker iobroker.js-controller version 4.0.23 js-controller starting
2022-07-24 08:03:57.763  - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-07-24 08:03:57.764  - info: host.iobroker hostname: iobroker, node: v14.20.0
2022-07-24 08:03:57.766  - info: host.iobroker ip addresses: 172.17.0.2
2022-07-24 08:03:59.705  - info: host.iobroker connected to Objects and States
2022-07-24 08:03:59.756  - info: host.iobroker added notifications configuration of host
2022-07-24 08:03:59.768  - info: host.iobroker Node.js version has changed from unknown to 14.20.0
2022-07-24 08:03:59.883  - info: host.iobroker Successfully updated capabilities "cap_net_admin, cap_net_bind_service, cap_net_raw" for /usr/bin/node
2022-07-24 08:04:00.474  - info: host.iobroker Delete host system.host.iobroker-neu
2022-07-24 08:04:00.580  - info: host.iobroker 28 instances found
2022-07-24 08:04:00.615  - warn: host.iobroker does not start any instances on this host

Wieso startet der iobroker keine Instanz?
Ich habe dann erfolgreich den iobroker fix durchlaufen lassen:

curl -sL https://iobroker.net/fix.sh | bash -

Danach erhalte ich dieses Log

2022-07-25 12:02:52.501  - info: host.iobroker iobroker.js-controller version 4.0.23 js-controller starting
2022-07-25 12:02:52.516  - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-07-25 12:02:52.517  - info: host.iobroker hostname: iobroker, node: v14.20.0
2022-07-25 12:02:52.519  - info: host.iobroker ip addresses: 172.17.0.2
2022-07-25 12:02:54.668  - error: host.iobroker-Server Cannot start inMem-objects on port 9001: Failed to lock DB file "/opt/iobroker/iobroker-data/objects.jsonl"!

ich habe den Docker gestoppt, die objects.jsonl.lock Datei gelöscht und erneut gestartet.

root@iobroker-neu:/opt/iobroker# pkill -u iobroker                                                                                                                                                  
root@iobroker-neu:/opt/iobroker# iobroker start                                                                                                                                                     
Starting iobroker controller daemon...                                                                                                                                                              
iobroker controller daemon started. PID: 16915                                                                                                                                                      
root@iobroker-neu:/opt/iobroker# 

2022-07-25 12:08:24.468  - info: host.iobroker received SIGTERM
2022-07-25 12:08:24.572  - info: host.iobroker terminated
2022-07-25 12:08:32.544  - info: host.iobroker iobroker.js-controller version 4.0.23 js-controller starting
2022-07-25 12:08:32.557  - info: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-07-25 12:08:32.559  - info: host.iobroker hostname: iobroker, node: v14.20.0
2022-07-25 12:08:32.560  - info: host.iobroker ip addresses: 172.17.0.2
2022-07-25 12:08:35.027  - info: host.iobroker connected to Objects and States
2022-07-25 12:08:35.089  - info: host.iobroker added notifications configuration of host
2022-07-25 12:08:35.902  - info: host.iobroker 28 instances found
2022-07-25 12:08:35.929  - warn: host.iobroker does not start any instances on this host

Ich habe verschieden Backups versucht, leider bei allen das Problem

@andre said in [Synology Docker]Iobroker startet nicht (no database):

@simka sagte in [Synology Docker]Iobroker startet nicht (no database):

Ich wollte mal iobroker:latest-v7 ausprobieren oder wäre ein Anderes besser bevor ich die Docker Applikation deinstalliere?

Ich würde es bei latest-v6 belassen. Sonst machst du auch noch nen node versionswechsel mit rein. Docker installieren wird meiner Meinung nach nix bringen... Ich teste das Image gerade mal in meinem virtuellen dsm 7...
Wenn du im Discord bist, ich bin aktuell in der Lounge online...

MfG,
André

Habs mit der latest-v7 und latest-v6 tetestet. Bei beiden direkt nach dem Starten der Instanz den getcap Befehl ausgeführt und immer den Fehler bekommen.
Liegt wohl tatsächlich an der Diskstation, am Speicher oder sonst wo

@andre said in [Synology Docker]Iobroker startet nicht (no database):

@SimKa Hast du mehrere Volumes/ Speicherpools auf der DiskStation? Welches Dateisystem verwendest du?

(Das ist jetzt so ein bisschen stochern im Nebel. Bin da leider nicht so der Dateisystem Spezi)

Ich habe nur ein Volume im Raid 1 betrieb.

@andre said in [Synology Docker]Iobroker startet nicht (no database):

Gerade im DSM gesehen, hier mal geschaut? Das sind die capabilities...

[EDIT] Bei mir läuft der Container auch ohne Probleme auf DSM 7...

Hier meine capabilities

@glasfaser said in [Synology Docker]Iobroker startet nicht (no database):

@simka sagte in [Synology Docker]Iobroker startet nicht (no database):
Docker ( Paket ) von Syn deinstallieren und neu installieren .

Damit meine ich das _

Achso, ich dachte das Image von iobroker.
Ich wollte mal iobroker:latest-v7 ausprobieren oder wäre ein Anderes besser bevor ich die Docker Applikation deinstalliere?

@andre said in [Synology Docker]Iobroker startet nicht (no database):

@glasfaser sagte in [Synology Docker]Iobroker startet nicht (no database):

denn .... wenn du iobroker neu installierst ist ja alles OK , nur bei einem Backup einspielen ist es so.

@simka sagte in [Synology Docker]Iobroker startet nicht (no database):

Hmm schade. Wundert mich, dass erst nach dem Update die Probleme auftreten.

Sicher dass es so ist? Bitte mal nen ioBroker Container ohne Restore testen und den getcap Befehl ausführen.

getcap $(eval readlink -f `which node`)

Ich würde nämlich tippen, dass das Problem grundsätzlich da ist. Ohne Restore wird nur eben nix an den capabilities gedreht. Das macht der ioBroker ja nur weil der js-controller nach dem Restore dies erkennt und korrigieren will:

2022-07-05 14:05:40.907  - info: host.iobroker Node.js version has changed from unknown to 14.19.3

MfG,
André

Tatsache, ist von Anfang an defekt. Direkt nach dem Start einer neuen leeren Docker Instanz kommt auch die Fehlermeldung.

root@iobroker-default:/opt/iobroker# getcap $(eval readlink -f `which node`)                                                                                                                        
Failed to get capabilities of file '/usr/bin/node' (Operation not supported)                                                                                                                        
root@iobroker-default:/opt/iobroker#

@glasfaser said in [Synology Docker]Iobroker startet nicht (no database):

@simka sagte in [Synology Docker]Iobroker startet nicht (no database):

Habe eine neue Instanz gestartet

Was heißt das bei dir ...

Eine Instanz ist im ioBroker !?

Mit einer Instanz meine ich eine Docker Instanz. Aus dem Image eine neue leere Docker Instanz starten

@glasfaser said in [Synology Docker]Iobroker startet nicht (no database):

@simka

host.iobroker-default

Bitte nicht immer den gleichen nutzen , auch eine anderen Mount Ordner nutzen !!!

Hast du viele Container laufen , wenn nein dann:

Docker ( Paket ) von Syn deinstallieren und neu installieren .

Ich habe nur einen Docker laufen. Ich mounte immer neue leere Ordner, kopiere dann das Backup *.gz in den backup Ordner (welcher nach dem Starten erstellt wurde) und führe dann das Backup aus.

Ich probiere gleich mal die neue Version bzw. ggfs. mal ne ältere Docker Version aus.