homematic binding lost Gateway_extras after restart openhab container

Hello,

every friday my debian server make a backup of all my docker peristance folders. For this backup a script stop docker with systemctl stop docker and after a copy, restart docker with systemctl start docker.

my homematic binding:

UID: homematic:bridge:dcf0c3faae
label: Homematic Bridge
thingTypeUID: homematic:bridge
configuration:
binCallbackPort: 9126
xmlCallbackPort: 9125
cuxdPort: 8701
socketMaxAlive: 1200
installModeDuration: 60
userName: *******
callbackRegTimeout: 1200
hmIpPort: 2010
timeout: 600
factoryResetOnDeletion: false
discoveryTimeToLive: 600
password: *******
wiredPort: 2000
gatewayType: auto
callbackHost: 192.168.1.40
useAuthentication: true
groupPort: 9292
gatewayAddress: 192.168.1.5
unpairOnDeletion: false
rfPort: 2001
bufferSize: 4096
channels:

my openhab log with trace:

2025-03-15 19:47:10.518 [WARN ] [core.thing.internal.ThingManagerImpl] - Could not normalize configuration for 'homematic:GATEWAY-EXTRAS-DCF0C3FAAE:dcf0c3faae:GWE00000000' because the thing type was not found in registry.
2025-03-15 19:48:26.270 [DEBUG] [ternal.communicator.client.RpcClient] - Submitting setInstallMode(on=true, time=60, mode=1)
2025-03-15 19:48:26.270 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcRequest:
setInstallMode()
true
60
1
2025-03-15 19:48:26.270 [TRACE] [al.communicator.client.SocketHandler] - Creating new socket for port 8701
2025-03-15 19:48:26.273 [DEBUG] [nal.communicator.client.BinRpcClient] - BinRpcMessage socket failure, sending message again 1/3
2025-03-15 19:48:26.274 [TRACE] [al.communicator.client.SocketHandler] - Closing Socket on port 8701
2025-03-15 19:48:26.274 [TRACE] [al.communicator.client.SocketHandler] - Creating new socket for port 8701
2025-03-15 19:48:26.278 [DEBUG] [nal.communicator.client.BinRpcClient] - BinRpcMessage socket failure, sending message again 2/3
2025-03-15 19:48:26.279 [TRACE] [al.communicator.client.SocketHandler] - Closing Socket on port 8701
2025-03-15 19:48:26.279 [TRACE] [al.communicator.client.SocketHandler] - Creating new socket for port 8701
2025-03-15 19:48:26.285 [DEBUG] [nal.communicator.client.BinRpcClient] - BinRpcMessage socket failure, sending message again 3/3
2025-03-15 19:48:26.285 [TRACE] [al.communicator.client.SocketHandler] - Closing Socket on port 8701
2025-03-15 19:48:26.286 [TRACE] [al.communicator.client.SocketHandler] - Creating new socket for port 8701
2025-03-15 19:48:26.290 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcResponse:
{
faultCode=-1
faultString=setInstallMode: unknown.method name
}

2025-03-15 19:48:26.290 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcResponse:
{
faultCode=-1
faultString=setInstallMode: unknown.method name
}

2025-03-15 19:48:26.291 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcResponse:
{
faultCode=-1
faultString=setInstallMode: unknown.method name
}

2025-03-15 19:48:26.291 [TRACE] [nal.communicator.client.BinRpcClient] - Client BinRpcResponse:
{
faultCode=-1
faultString=setInstallMode: unknown.method name
}

2025-03-15 19:48:26.292 [WARN ] [very.HomematicDeviceDiscoveryService] - Failed to set Homematic controller in install mode
java.io.IOException: -1 setInstallMode: unknown.method name (sending setInstallMode()
true
60
1
)
at org.openhab.binding.homematic.internal.communicator.parser.RpcResponseParser.parse(RpcResponseParser.java:50) ~[?:?]
at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:83) ~[?:?]
at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:95) ~[?:?]
at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:95) ~[?:?]
at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:95) ~[?:?]
at org.openhab.binding.homematic.internal.communicator.client.BinRpcClient.sendMessage(BinRpcClient.java:71) ~[?:?]
at org.openhab.binding.homematic.internal.communicator.client.RpcClient.setInstallMode(RpcClient.java:439) ~[?:?]
at org.openhab.binding.homematic.internal.communicator.AbstractHomematicGateway.setInstallMode(AbstractHomematicGateway.java:602) ~[?:?]
at org.openhab.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.enableInstallMode(HomematicDeviceDiscoveryService.java:82) ~[?:?]
at org.openhab.binding.homematic.internal.discovery.HomematicDeviceDiscoveryService.startScan(HomematicDeviceDiscoveryService.java:67) ~[?:?]
at org.openhab.core.config.discovery.AbstractDiscoveryService.startScanInternal(AbstractDiscoveryService.java:253) ~[?:?]
at org.openhab.core.config.discovery.AbstractDiscoveryService.startScan(AbstractDiscoveryService.java:216) ~[?:?]
at org.openhab.binding.homematic.internal.handler.HomematicBridgeHandler.initializeInternal(HomematicBridgeHandler.java:123) ~[?:?]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:840) [?:?]

And my homematic log of my ccu2:

2025-03-15	00:19:19	warning	192.168.1.36	daemon	cuxd	192.168.1.40 called unknown request method 'setInstallMode' 
2025-03-15	00:19:19	warning	192.168.1.36	daemon	cuxd	192.168.1.40 called unknown request method 'setInstallMode' 
2025-03-15	00:19:19	warning	192.168.1.36	daemon	cuxd	192.168.1.40 called unknown request method 'setInstallMode' 
2025-03-15	00:19:19	warning	192.168.1.36	daemon	cuxd	192.168.1.40 called unknown request method 'setInstallMode' 
2025-03-15	00:19:09	info	192.168.1.36	daemon	cuxd	INIT 'binary://192.168.1.40:9126' 'fc47a68f-dd23-4fce-b88f-fb2207f527fe' 
2025-03-15	00:19:08	warning	192.168.1.36	daemon	cuxd	process_rpc_request(192.168.1.40) - illegal XMLRPC(init) request 
2025-03-15	00:19:08	info	192.168.1.36	daemon	cuxd	INIT 'binary://192.168.1.40:9126' '(null)' 
2025-03-15	00:09:30	info	192.168.1.36	daemon	cuxd	INIT 'binary://192.168.1.40:9126' 'cbb5b10d-d272-4241-b7ca-b9264c55d37e' 
2025-03-15	00:09:29	warning	192.168.1.36	daemon	cuxd	process_rpc_request(192.168.1.40) - illegal XMLRPC(init) request 
2025-03-15	00:09:17	info	192.168.1.36	daemon	cuxd	INIT 'binary://192.168.1.40:9126' '(null)' 
2025-03-14	23:59:25	info	192.168.1.36	daemon	cuxd	INIT 'binary://192.168.1.40:9126' 'c942437b-da83-4d84-ac28-afc67d66df95' 
2025-03-14	23:59:24	warning	192.168.1.36	daemon	cuxd	process_rpc_request(192.168.1.40) - illegal XMLRPC(init) request 
2025-03-14	23:58:15	info	192.168.1.36	daemon	cuxd	INIT 'binary://192.168.1.40:9126' '(null)'

After the next backup session on Friday morning, the gateway_extras was still offline with a config_error. After I disabled and enabled the Homematic binding, the gateway_extras was online again. Unfortunately, the crucial log entries were overwritten by the log rotation. I will monitor it next Friday.