Benachrichtigungen
Alles löschen

Server hängt sich regelmäßig auf

Seite 2 / 2

New Member
Beigetreten: Vor 8 Jahren
Beiträge: 1
 

Bei mir schmiert auch alles ab ☹️ 11.0.15


   
AntwortZitat
Active Member
Beigetreten: Vor 6 Jahren
Beiträge: 3
 

Hallo, bei mir auch mit der Version 11.0.15 auf Raspberry 4....2 Mal "tot" pro Tag.

@ Xsolution....bitte um rascheste Behebung.....


   
AntwortZitat
Eminent Member
Beigetreten: Vor 11 Jahren
Beiträge: 19
 

Ich habe gestern, nachdem der Server gegen Mittag wieder weg war, nach dem Reboot die Xsolution-Cloud Schnittstelle deaktiviert. Da ich primär Siri anstelle von Alexa benutze, auch wenn man sich bei diesem blöden Ding dazu zwingen muss und es manchmal Nerven kostet, ist das jetzt zum Test bei mir nicht so schlimm.

Seitdem noch keinen weiteren Ausfall. Ob das aber Zufall ist oder zusammenhängt - keine Ahnung.

Thomas


   
AntwortZitat
 Jens
Eminent Member
Beigetreten: Vor 11 Jahren
Beiträge: 31
 

Hallo Rainer,

auch bei mir ist der Server wieder mal nicht erreichbar. Gestern war der Status der Cloud schon auf Fehler gestanden.

So werde mal ein Reboot machen und dann die Cloud rausschmeißen. Nutze Sie ja nicht.

 

Wäre trotzem schon, wenn der Server erreichbar wäre auch wenn eine Schnittstelle nicht erreichbar ist.

war ja davor auch so.

Vielen Dank

VG Jens

 

Xhome Evo 1.0.67 auf Qnap TS251+


   
AntwortZitat
Eminent Member
Beigetreten: Vor 6 Jahren
Beiträge: 32
 

Hallo zusammen,

Nachdem ich auch ständig das Problem hatte, dass der xhome nicht mehr erreichbar war, habe ich einen Downgrad auf 13 Version durchgeführt.

Brachte jetzt im Endeffekt auch keine Besserung.

Server hängt sich weiter ständig auf, Apple HomeKit sowie Alexa ohne Funktion.

Linux neu installiert, openjdk sowie xhome neu….

Schnittstellen wieder verfügbar, bis jetzt keinen Neustart mit Version 15 gehabt.

so vermute ich, dass über das Update bei xHome irgendwas in openjdk zerschossen wird

grüsse 

 

 


   
AntwortZitat
Eminent Member
Beigetreten: Vor 4 Jahren
Beiträge: 33
 

Hallo Rainer,

ich hab ein ähnliches Problem. Mein Server, Version 11.0.15 und Java 11.0.13, auf einem Intel Nuc mit Win 10. Der Server stürzt recht unmotiviert ab. Hier ist ein Auszug des Server Logs. So wie es aussieht liegt es am Timer2? Ich hatte gerade in der Visu ein Element der Nuki Bridge bearbeitet, als plötzlich die Seite nicht mehr reagiert hat.

VG Max

 

2022-09-25T11:42:22,447 [qtp14605597-97] INFO (Web_Socket_Handler.java:76) - New connection: 192.168.178.35 55249
2022-09-25T11:42:22,448 [qtp14605597-97] INFO (Web_Socket_Server.java:485) - addClient 2
2022-09-25T11:42:22,450 [qtp14605597-97] INFO (Web_Socket_Handler.java:66) - Error: Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Session) with args: [org.eclipse.jetty.websocket.common.WebSocketSession]
2022-09-25T11:42:22,451 [qtp14605597-97] INFO (Web_Socket_Handler.java:49) - Close: statusCode=1011, reason=Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Sess
2022-09-25T11:42:22,452 [qtp14605597-97] INFO (Web_Socket_Server.java:491) - removeClient 1
2022-09-25T11:42:24,076 [qtp14605597-104] INFO (Web_Socket_Handler.java:76) - New connection: 192.168.178.35 55250
2022-09-25T11:42:24,077 [qtp14605597-104] INFO (Web_Socket_Server.java:485) - addClient 2
2022-09-25T11:42:24,079 [qtp14605597-104] INFO (Web_Socket_Handler.java:66) - Error: Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Session) with args: [org.eclipse.jetty.websocket.common.WebSocketSession]
2022-09-25T11:42:24,080 [qtp14605597-104] INFO (Web_Socket_Handler.java:49) - Close: statusCode=1011, reason=Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Sess
2022-09-25T11:42:24,080 [qtp14605597-104] INFO (Web_Socket_Server.java:491) - removeClient 1
2022-09-25T11:42:25,018 [qtp14605597-97] INFO (Web_Socket_Handler.java:76) - New connection: 192.168.178.35 55251
2022-09-25T11:42:25,019 [qtp14605597-97] INFO (Web_Socket_Server.java:485) - addClient 2
2022-09-25T11:42:25,021 [qtp14605597-97] INFO (Web_Socket_Handler.java:66) - Error: Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Session) with args: [org.eclipse.jetty.websocket.common.WebSocketSession]
2022-09-25T11:42:25,022 [qtp14605597-97] INFO (Web_Socket_Handler.java:49) - Close: statusCode=1011, reason=Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Sess
2022-09-25T11:42:25,022 [qtp14605597-97] INFO (Web_Socket_Server.java:491) - removeClient 1
2022-09-25T11:42:25,546 [qtp14605597-104] INFO (Web_Socket_Handler.java:76) - New connection: 192.168.178.35 55252
2022-09-25T11:42:25,546 [qtp14605597-104] INFO (Web_Socket_Server.java:485) - addClient 2
2022-09-25T11:42:25,549 [qtp14605597-104] INFO (Web_Socket_Handler.java:66) - Error: Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Session) with args: [org.eclipse.jetty.websocket.common.WebSocketSession]
2022-09-25T11:42:25,550 [qtp14605597-104] INFO (Web_Socket_Handler.java:49) - Close: statusCode=1011, reason=Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Sess
2022-09-25T11:42:25,550 [qtp14605597-104] INFO (Web_Socket_Server.java:491) - removeClient 1
2022-09-25T11:42:26,700 [qtp14605597-104] INFO (Web_Socket_Handler.java:76) - New connection: 192.168.178.35 55253
2022-09-25T11:42:26,700 [qtp14605597-104] INFO (Web_Socket_Server.java:485) - addClient 2
2022-09-25T11:42:26,703 [qtp14605597-104] INFO (Web_Socket_Handler.java:66) - Error: Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Session) with args: [org.eclipse.jetty.websocket.common.WebSocketSession]
2022-09-25T11:42:26,703 [qtp14605597-104] INFO (Web_Socket_Handler.java:49) - Close: statusCode=1011, reason=Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Sess
2022-09-25T11:42:26,704 [qtp14605597-104] INFO (Web_Socket_Server.java:491) - removeClient 1
2022-09-25T11:42:40,815 [qtp14605597-97] INFO (Web_Socket_Handler.java:49) - Close: statusCode=1001, reason=null
2022-09-25T11:42:40,816 [qtp14605597-97] INFO (Web_Socket_Server.java:491) - removeClient 0
2022-09-25T11:42:41,123 [qtp14605597-104] INFO (Web_Socket_Handler.java:76) - New connection: 192.168.178.35 55269
2022-09-25T11:42:41,123 [qtp14605597-104] INFO (Web_Socket_Server.java:485) - addClient 12022-09-25T11:42:49,311 [qtp14605597-104] INFO (Web_Socket_Handler.java:76) - New connection: 192.168.178.35 55281
2022-09-25T11:42:49,312 [qtp14605597-104] INFO (Web_Socket_Server.java:485) - addClient 2
2022-09-25T11:42:49,314 [qtp14605597-104] INFO (Web_Socket_Handler.java:66) - Error: Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Session) with args: [org.eclipse.jetty.websocket.common.WebSocketSession]
2022-09-25T11:42:49,316 [qtp14605597-104] INFO (Web_Socket_Handler.java:49) - Close: statusCode=1011, reason=Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Sess
2022-09-25T11:42:49,316 [qtp14605597-104] INFO (Web_Socket_Server.java:491) - removeClient 1
2022-09-25T11:42:52,704 [qtp14605597-97] INFO (Web_Socket_Handler.java:76) - New connection: 192.168.178.35 55286
2022-09-25T11:42:52,705 [qtp14605597-97] INFO (Web_Socket_Server.java:485) - addClient 2
2022-09-25T11:42:52,707 [qtp14605597-97] INFO (Web_Socket_Handler.java:66) - Error: Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Session) with args: [org.eclipse.jetty.websocket.common.WebSocketSession]
2022-09-25T11:42:52,708 [qtp14605597-97] INFO (Web_Socket_Handler.java:49) - Close: statusCode=1011, reason=Cannot call method public void de.xsolution.communication.Web_Socket_Handler#onConnect(org.eclipse.jetty.websocket.api.Sess
2022-09-25T11:42:52,708 [qtp14605597-97] INFO (Web_Socket_Server.java:491) - removeClient 1
2022-09-25T11:42:56,004 [Timer-2] INFO (Cloud_Client.java:170) - Fehler, Verbindung wird neu initialisiert
2022-09-25T11:42:56,007 [Timer-2] ERROR (Cloud_Client.java:125) - java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
2022-09-25T11:43:18,480 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Connection_Json.java:88) - {"siteCurrentPowerFlow":{"updateRefreshRate":3,"unit":"kW","connections":[{"from":"LOAD","to":"Grid"},{"from":"PV","to":"Load"},{"from":"PV","to":"Storage"}],"GRID":{"status":"Active","currentPower":0.4},"LOAD":{"status":"Active","currentPower":0.29},"PV":{"status":"Active","currentPower":1.66},"STORAGE":{"status":"Charging","currentPower":0.97,"chargeLevel":31,"critical":false}}}
2022-09-25T11:43:18,481 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Connection_Json.java:89) - {"overview":{"lastUpdateTime":"2022-09-25 11:43:15","lifeTimeData":{"energy":3.77269E7,"revenue":7781.407},"lastYearData":{"energy":6482438.0},"lastMonthData":{"energy":534332.0},"lastDayData":{"energy":1369.0},"currentPower":{"power":588.0},"measuredBy":"INVERTER"}}
2022-09-25T11:43:18,482 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Gateway_Solaredge.java:178) - get Solaredge aktuelle Leistung (Monitoring) aktpverzeugungkw
2022-09-25T11:43:18,483 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Gateway_Solaredge.java:198) - Solaredge Value Received :aktuelle Leistung (Monitoring) = 1.6599999999999999200639422269887290894985198974609375
2022-09-25T11:43:56,010 [Timer-2] INFO (Cloud_Client.java:170) - Fehler, Verbindung wird neu initialisiert
2022-09-25T11:43:56,013 [Timer-2] ERROR (Cloud_Client.java:125) - java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
2022-09-25T11:44:19,041 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Connection_Json.java:88) - {"siteCurrentPowerFlow":{"updateRefreshRate":3,"unit":"kW","connections":[{"from":"LOAD","to":"Grid"},{"from":"PV","to":"Load"},{"from":"PV","to":"Storage"}],"GRID":{"status":"Active","currentPower":0.41},"LOAD":{"status":"Active","currentPower":0.31},"PV":{"status":"Active","currentPower":1.68},"STORAGE":{"status":"Charging","currentPower":0.96,"chargeLevel":31,"critical":false}}}
2022-09-25T11:44:19,043 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Connection_Json.java:89) - {"overview":{"lastUpdateTime":"2022-09-25 11:44:20","lifeTimeData":{"energy":3.77269E7,"revenue":7781.407},"lastYearData":{"energy":6482438.0},"lastMonthData":{"energy":534332.0},"lastDayData":{"energy":1369.0},"currentPower":{"power":588.0},"measuredBy":"INVERTER"}}
2022-09-25T11:44:19,044 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Gateway_Solaredge.java:178) - get Solaredge aktuelle Leistung (Monitoring) aktpverzeugungkw
2022-09-25T11:44:19,046 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Gateway_Solaredge.java:198) - Solaredge Value Received :aktuelle Leistung (Monitoring) = 1.6799999999999999378275106209912337362766265869140625
2022-09-25T11:44:56,049 [Timer-2] INFO (Cloud_Client.java:170) - Fehler, Verbindung wird neu initialisiert
2022-09-25T11:44:56,064 [Timer-2] ERROR (Cloud_Client.java:125) - java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached
2022-09-25T11:45:19,940 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Connection_Json.java:88) - {"siteCurrentPowerFlow":{"updateRefreshRate":3,"unit":"kW","connections":[{"from":"LOAD","to":"Grid"},{"from":"PV","to":"Load"},{"from":"PV","to":"Storage"}],"GRID":{"status":"Active","currentPower":0.44},"LOAD":{"status":"Active","currentPower":0.3},"PV":{"status":"Active","currentPower":1.71},"STORAGE":{"status":"Charging","currentPower":0.97,"chargeLevel":32,"critical":false}}}
2022-09-25T11:45:19,940 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Connection_Json.java:89) - {"overview":{"lastUpdateTime":"2022-09-25 11:45:20","lifeTimeData":{"energy":3.7726956E7,"revenue":7781.418},"lastYearData":{"energy":6482493.0},"lastMonthData":{"energy":534387.0},"lastDayData":{"energy":1424.0},"currentPower":{"power":727.0},"measuredBy":"INVERTER"}}
2022-09-25T11:45:19,941 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Gateway_Solaredge.java:178) - get Solaredge aktuelle Leistung (Monitoring) aktpverzeugungkw
2022-09-25T11:45:19,943 [[de.xsolution.gateways.gateway_solaredge.Gateway_Solaredge::UpdateQueue_11] pool-38-thread-1] INFO (Gateway_Solaredge.java:198) - Solaredge Value Received :aktuelle Leistung (Monitoring) = 1.70999999999999996447286321199499070644378662109375

   
AntwortZitat
Eminent Member
Beigetreten: Vor 6 Jahren
Beiträge: 32
 

Alexa funktioniert doch nicht!
ich habs bereits erwähnt, die Logfile wird permanent voll geschrieben. Seit der Neuinstallation von heute Morgen 8:30 bis 12.00 Uhr wurden wieder bereits 16Mb geschrieben:

2022-09-25T12:40:16,836 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 75
2022-09-25T12:40:16,836 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 76
2022-09-25T12:40:16,836 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 74
2022-09-25T12:40:16,836 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 73
2022-09-25T12:40:16,836 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 72
2022-09-25T12:40:16,837 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 71
2022-09-25T12:40:16,837 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 70
2022-09-25T12:40:16,837 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 69
2022-09-25T12:40:16,837 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 67
2022-09-25T12:40:16,837 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 68
2022-09-25T12:40:17,144 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 79
2022-09-25T12:40:17,144 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 77
2022-09-25T12:40:17,144 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 75
2022-09-25T12:40:17,145 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 76
2022-09-25T12:40:17,145 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 74
2022-09-25T12:40:17,145 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 73
2022-09-25T12:40:17,145 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 72
2022-09-25T12:40:17,145 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 71
2022-09-25T12:40:17,145 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 70
2022-09-25T12:40:17,146 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 69
2022-09-25T12:40:17,146 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 67
2022-09-25T12:40:17,146 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 68
2022-09-25T12:40:19,031 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 79
2022-09-25T12:40:19,031 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 77
2022-09-25T12:40:19,031 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 75
2022-09-25T12:40:19,032 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 76
2022-09-25T12:40:19,032 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 74
2022-09-25T12:40:19,032 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 73
2022-09-25T12:40:19,032 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 72
2022-09-25T12:40:19,032 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 71
2022-09-25T12:40:19,032 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 70
2022-09-25T12:40:19,033 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 69
2022-09-25T12:40:19,033 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 67
2022-09-25T12:40:19,033 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 68
2022-09-25T12:40:19,147 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 79
2022-09-25T12:40:19,147 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 77
2022-09-25T12:40:19,147 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 75
2022-09-25T12:40:19,147 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 76
2022-09-25T12:40:19,148 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 74
2022-09-25T12:40:19,148 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 73
2022-09-25T12:40:19,148 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 72
2022-09-25T12:40:19,148 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 71
2022-09-25T12:40:19,148 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 70
2022-09-25T12:40:19,148 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 69
2022-09-25T12:40:19,149 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 67
2022-09-25T12:40:19,149 [[de.xsolution.gateways.gateway_knx.Gateway_Knx::knxUpdateReceiveExecutor1] pool-49-thread-1] INFO (SubscriptionManager.java:129) - Publishing change for 68
2022-09-25T12:40:25,582 [Timer-3] INFO (Cloud_Client.java:170) - Fehler, Verbindung wird neu initialisiert


   
AntwortZitat
Mitglied Admin
Beigetreten: Vor 12 Jahren
Beiträge: 91
 

Hallo zusammen,

danke für die Rückmeldungen, wir sind an dem Thema dran. 

 

Gruß Xsolkution


   
AntwortZitat
Eminent Member
Beigetreten: Vor 4 Jahren
Beiträge: 33
 

Hallo Rainer,

das wäre echt toll, wenn da zügig eine Abhilfe käme. Ich muss den Server täglich mehrmals neu starten, Rollos gehen nicht mehr hoch oder runter, die PV macht, was sie will, etc.
Da merkt man erstmal, was passiert, wenn man sich auf ein einziges System verlassen hat...

 

VG Max

Diese r Beitrag wurde geändert Vor 2 Monaten von atlantic

   
AntwortZitat
Eminent Member
Beigetreten: Vor 1 Jahr
Beiträge: 18
 

Hallo

Bei mir hängt es auch mit der Xsolution Cloud zusammen, wenn sie nicht erreichbar ist, dann schmiert der Server regelmäßig ab. Jetzt habe ich die Schnittstelle deaktiviert, seit dem läuft der Server.

Grus T. G. 

Diese r Beitrag wurde geändert Vor 2 Monaten von FSXPET

   
AntwortZitat
 Jens
Eminent Member
Beigetreten: Vor 11 Jahren
Beiträge: 31
 

Hallo

nachdem ich die xhome cloud Schnittstelle gelöscht habe, ist die Oberfläche von Xhome erreichbar. Läuft seit 2 Tagen ohne Probleme

VG

Jens

Xhome Evo 1.0.67 auf Qnap TS251+


   
AntwortZitat
Mitglied Admin
Beigetreten: Vor 12 Jahren
Beiträge: 91
 

Hallo zusammen,

kurzzeitig mal die Alexa Cloud Schnittstelle löschen. Wir optimieren gerade die Schnittstelle und wechseln den Provider.

Wir versuchen das Problem so schnell wie möglich zu lösen.

 

 

Gruß Xsolution

 


   
AntwortZitat
 BB
Eminent Member
Beigetreten: Vor 4 Jahren
Beiträge: 19
 

Hi Xsolution team,

die neue Version 10.0.17 läuft auf dem Raspberry 4 8GB stabil - hurra endlich braucht man nicht mehr auf Version  10.0.10 downgraden.

Sogar die Charts mit großer Datenbank - bei uns schon 61 000kb - läuft nun schon seid 2 wochen und wächst weiter!

 

Watchdog für das xhome "Servic"e bleibt essentiel!

 

WOLLTE MAL DANKE sagen - die Version 10.0.17 ist die best ever xhome evolution Version für Raspberry Platform!

Weiter so,

BB


   
AntwortZitat
Seite 2 / 2
Teilen:
WordPress Cookie Hinweis von Real Cookie Banner