Hallo nochmal,
Dank udo1toni, ich habe das Logging in der Openhab Console auf DEBUG hochgesetzt.
Man kann leider nur für ALLE Bindings das login hochdrehen.
Wie auch immer, ich habe alle Things disabled, Login hochgesetzt und dann das Thing für die Fritzbox von DISABLED wieder eingeschaltet.
Das habe ich mit der funktionierenden Fritzbox (offizielles FritzOS) und mit der Test-Fritzbox (Laborversion) durchgefürht.
Im Log ist das Problem erkennbar:
So sieht das Log aus, wenn OpenHab zur funktionierenden Fritzbox die Verbindung öffnen will:
Code: Alles auswählen
Queued HttpRequest[GET /status HTTP/1.1]@1a4d26a for HttpDestination[http://192.168.0.214]@1444559,queue=1,pool=DuplexConnectionPool@157503c[c=0/0/2,a=0,i=0,q=1]
write(array) s=OPEN,api=BLOCKING,sc=false,e=null aggregated !flush DirectByteBuffer@d96fac[p=0,l=15,c=32768,r=15]={<<<event: message\n>>>data: {"t...\x00\x00\x00\x00\x00\x00\x00}
Acquiring create=true on DuplexConnectionPool@157503c[c=0/0/2,a=0,i=0,q=1]
write(array HeapByteBuffer@fff003[p=0,l=6,c=6,r=6]={<<<data: >>>})
Try creating connection 0/2 with 0 pending
Try creating(true) connection, pending/demand/supply: 0/2/0, result=true
write(array) s=OPEN,api=BLOCKING,sc=false,e=null aggregated !flush DirectByteBuffer@d96fac[p=0,l=21,c=32768,r=21]={<<<event: message\ndata: >>>{"topic":...\x00\x00\x00\x00\x00\x00\x00}
Creating connection 0/2 at MultiEntry@ff5020{PENDING,usage=0,multiplex=0,pooled=null}
write(array HeapByteBuffer@16268c4[p=0,l=198,c=198,r=198]={<<<{"topic":"openhab/things/..."ThingStatusInfoEvent"}>>>})
Und so sieht es aus, wenn die Verbindung zur Fritzbox mit der Laborversion eröffnet werden soll:
Code: Alles auswählen
Queued HttpRequest[GET /login_sid.lua HTTP/1.1]@1443c57 for HttpDestination[http://192.168.1.1]@ae84c8,queue=1,pool=DuplexConnectionPool@18e3fdb[c=0/0/2,a=0,i=0,q=1]
Acquiring create=true on DuplexConnectionPool@18e3fdb[c=0/0/2,a=0,i=0,q=1]
Selector sun.nio.ch.EPollSelectorImpl@17bbf0a woken with none selected
Selector sun.nio.ch.EPollSelectorImpl@17bbf0a woken up from select, 0/0/5 selected
Try creating connection 0/2 with 0 pending
Selector sun.nio.ch.EPollSelectorImpl@17bbf0a processing 0 keys, 0 updates
updateable 0
updates 0
Selector sun.nio.ch.EPollSelectorImpl@17bbf0a waiting with 5 keys
queue org.eclipse.jetty.io.ManagedSelector$DestroyEndPoint@1240536 startThread=0
flushed 206 SocketChannelEndPoint@32ac3b{l=/192.168.1.202:8080,r=/192.168.0.202:53540,OPEN,fill=-,flush=W,to=1405/30000}{io=0/0,kio=0,kro=1}->HttpConnection@be3e12[p=HttpParser{s=CONTENT,0 of -1},g=HttpGenerator@3da39b{s=COMMITTED}]=>HttpChannelOverHttp@c82042{s=HttpChannelState@19515ce{s=WAITING rs=ASYNC os=COMMITTED is=IDLE awp=false se=false i=false al=2},r=1,c=false/false,a=WAITING,uri=//192.168.1.202:8080/rest/events?topics=openhab/items/*/*,openhab/things/*/*,openhab/channels/*/triggered,openhab/channels/*/descriptionchanged,age=188298024}
Flushed=true written=206 remaining=0 WriteFlusher@34e640{WRITING}->null
generate: DONE for SendCallback@141b01e[PROCESSING][i=null,cb=org.eclipse.jetty.server.HttpChannel$SendCallback@1b8fed0] (null,[p=200,l=200,c=32768,r=0],false)@COMMITTED
onWriteComplete(false,null) s=OPEN,api=BLOCKED,sc=false,e=null->s=OPEN,api=BLOCKING,sc=false,e=null c=null cb=null w=false
write(array HeapByteBuffer@2a186b[p=0,l=1,c=1,r=1]={<<<\n>>>})
Commit failed
org.eclipse.jetty.io.EofException: null
at org.eclipse.jetty.io.ChannelEndPoint.flush(ChannelEndPoint.java:279) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.io.WriteFlusher.flush(WriteFlusher.java:422) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.io.WriteFlusher.write(WriteFlusher.java:277) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.io.AbstractEndPoint.write(AbstractEndPoint.java:381) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.server.HttpConnection$SendCallback.process(HttpConnection.java:831) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.util.IteratingCallback.processing(IteratingCallback.java:241) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.util.IteratingCallback.iterate(IteratingCallback.java:223) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:555) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:1014) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:1086) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.server.HttpOutput.channelWrite(HttpOutput.java:285) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.server.HttpOutput.channelWrite(HttpOutput.java:269) ~[bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.server.HttpOutput.flush(HttpOutput.java:751) ~[bundleFile:9.4.46.v20220331]
at org.openhab.core.io.rest.core.internal.GsonMessageBodyWriter.writeTo(GsonMessageBodyWriter.java:91) ~[?:?]
at org.openhab.core.io.rest.core.internal.MediaTypeExtension.writeTo(MediaTypeExtension.java:84) ~[?:?]
at org.apache.cxf.jaxrs.sse.OutboundSseEventBodyWriter.writePayloadTo(OutboundSseEventBodyWriter.java:133) ~[bundleFile:3.4.5]
at org.apache.cxf.jaxrs.sse.OutboundSseEventBodyWriter.writeTo(OutboundSseEventBodyWriter.java:112) ~[bundleFile:3.4.5]
at org.apache.cxf.jaxrs.sse.OutboundSseEventBodyWriter.writeTo(OutboundSseEventBodyWriter.java:40) ~[bundleFile:3.4.5]
at org.apache.cxf.jaxrs.sse.SseEventSinkImpl.dequeue(SseEventSinkImpl.java:238) ~[bundleFile:3.4.5]
at org.eclipse.jetty.server.handler.ContextHandler.handle(ContextHandler.java:1525) [bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.server.AsyncContextState$1.run(AsyncContextState.java:153) [bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883) [bundleFile:9.4.46.v20220331]
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034) [bundleFile:9.4.46.v20220331]
at java.lang.Thread.run(Thread.java:829) [?:?]
Caused by: java.io.IOException: Broken pipe
at sun.nio.ch.FileDispatcherImpl.writev0(Nat
Das Binding kommt nicht einmal dazu die API aufzurufen, weil der eigentliche Verbindungsaufbau schon auf die Bretter geht.
Hinweis sind für mich 2 meldungen:
1. queue org.eclipse.jetty.io.
ManagedSelector$DestroyEndPoint@1240536 startThread=0
2. onWriteComplete(false,null) s=OPEN,
api=BLOCKED,sc=false,
Da scheint die API auf der Fritzbox in die Knie gegangen zu sein.
Bevor ich jetzt die Fritzbox zurücksetze würde ich nochmal einen Hinweis bei AVM aufgeben, ob ggf. die Updateprozedur ein Fehler machen kann.
Ich melde mich !
