Neue Java 11.0.26 #3012

radioo-007 · 2025-02-02T09:07:42Z

radioo-007
Feb 2, 2025

Hallo
Kann jemand bestätigen, ob es Probleme mit der neuen Java-Version zulu11.78.15-ca-jre11.0.26 in Neue Nightly Build Snapshots gibt?
System Rpi5 mit RaspberryMatic-3.79.6.20250131-1df261-rpi5 oder RaspberryMatic-3.79.6.20250201-2cd268-rpi5 oder RaspberryMatic-3.79.6.20250202-d72341-rpi5.

Logs nach dem Neustart des HMIPServers:

2025-02-02 09:21:04,710 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker ERROR [vert.x-worker-thread-4] Can not handle request com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0] 
de.eq3.cbcs.legacy.communication.rpc.RpcSerializationException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:232) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:79) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:30) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[HMIPServer.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
	at java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:701) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2235) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2141) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1203) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseMethodCall(XmlRpcParser.java:97) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:230) ~[HMIPServer.jar:?]
	... 10 more
2025-02-02 09:21:04,738 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker ERROR [vert.x-worker-thread-3] Can not handle request com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0] 
de.eq3.cbcs.legacy.communication.rpc.RpcSerializationException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:232) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:79) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:30) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[HMIPServer.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
	at java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:701) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2235) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2141) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1203) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseMethodCall(XmlRpcParser.java:97) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:230) ~[HMIPServer.jar:?]
	... 10 more
2025-02-02 09:21:09,631 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker ERROR [vert.x-worker-thread-4] Can not handle request com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0] 
de.eq3.cbcs.legacy.communication.rpc.RpcSerializationException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:232) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:79) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:30) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[HMIPServer.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
	at java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:701) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2235) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2141) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1203) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseMethodCall(XmlRpcParser.java:97) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:230) ~[HMIPServer.jar:?]
	... 10 more
2025-02-02 09:21:09,637 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker ERROR [vert.x-worker-thread-3] Can not handle request com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0] 
de.eq3.cbcs.legacy.communication.rpc.RpcSerializationException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:232) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:79) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:30) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[HMIPServer.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
	at java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:701) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2235) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2141) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1203) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseMethodCall(XmlRpcParser.java:97) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:230) ~[HMIPServer.jar:?]
	... 10 more
2025-02-02 09:21:27,502 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker ERROR [vert.x-worker-thread-4] Can not handle request com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0] 
de.eq3.cbcs.legacy.communication.rpc.RpcSerializationException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:232) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:79) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:30) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[HMIPServer.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
	at java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:701) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2235) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2141) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1203) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseMethodCall(XmlRpcParser.java:97) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:230) ~[HMIPServer.jar:?]
	... 10 more
2025-02-02 09:21:27,507 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker ERROR [vert.x-worker-thread-1] Can not handle request com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0] 
de.eq3.cbcs.legacy.communication.rpc.RpcSerializationException: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:232) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:79) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.bidcos.rpc.internal.AbstractLegacyAPIWorker.handle(AbstractLegacyAPIWorker.java:30) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104) ~[HMIPServer.jar:?]
	at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[HMIPServer.jar:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ~[?:?]
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[HMIPServer.jar:?]
	at java.lang.Thread.run(Unknown Source) ~[?:?]
Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
 at [row,col {unknown-source}]: [1,0]
	at com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:701) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2235) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2141) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1180) ~[HMIPServer.jar:?]
	at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1203) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRpcParser.parseMethodCall(XmlRpcParser.java:97) ~[HMIPServer.jar:?]
	at de.eq3.cbcs.legacy.communication.rpc.internal.format.xml.XmlRequestResponseProcessor.parseRequest(XmlRequestResponseProcessor.java:230) ~[HMIPServer.jar:?]
	... 10 more

Answered by jens-maus

Feb 2, 2025

Das wird daran liegen:

006e71e

Bitte also ein entsprechendes Ticket/Issue dazu aufmachen.

View full answer

Baxxy13 · 2025-02-02T09:17:09Z

Baxxy13
Feb 2, 2025

Ja, sehe ich hier auch auf diversen Testsystemen die mit den letzten Nightly's laufen.
Ich geh mal auf das letzte Release zurück um das gegenzuchecken.

1 reply

Baxxy13 Feb 2, 2025

Ich hab noch einen Pi4B gefunden der mit Nightly vom 25.01. läuft.
Der zeigt die Meldungen nicht, also liegt es wahrscheinlich am Java Update.

jens-maus · 2025-02-02T09:44:46Z

jens-maus
Feb 2, 2025
Maintainer

Das wird daran liegen:

006e71e

Bitte also ein entsprechendes Ticket/Issue dazu aufmachen.

7 replies

radioo-007 Feb 3, 2025
Author

Mit der offiziellen Releaseversion 3.79.6.20250118 ist alles OK, gestern habe ich bei dieser Version keine Fehler bemerkt

Baxxy13 Feb 3, 2025

Vielleicht sind die allerersten Meldungen (direkt nach Reboot) relevant:

2025-02-03 12:38:30,539 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Thread-1] BidCosCache could not be initialized 
2025-02-03 12:38:30,548 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Thread-1] java.net.ConnectException: Connection refused (Connection refused) 
2025-02-03 12:38:31,362 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register BidCos-RF_java 
2025-02-03 12:38:36,362 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register BidCos-RF_java 
2025-02-03 12:38:41,356 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register BidCos-RF_java 
2025-02-03 12:38:46,357 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register BidCos-RF_java 
2025-02-03 12:38:51,362 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register BidCos-RF_java 
2025-02-03 12:38:56,358 de.eq3.ccu.bidcos.dispatcher.BidCosRpcDispatcher ERROR [Timer-4] Could not register BidCos-RF_java 
2025-02-03 12:38:58,600 de.eq3.cbcs.legacy.bidcos.rpc.internal.LegacyAPIWorker ERROR [vert.x-worker-thread-3] Can not handle request com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog

Ich hab noch nen Pi3B+ gefunden der mit 30.01. ohne diese Fehler läuft.

jens-maus Feb 3, 2025
Maintainer

Vielleicht löst die ReGa 249 diese Fehlermeldung aus? Kannst du mal bitte schauen/probieren ob neuere ReGa da irgendwas mit zu tun haben? in nem OVA sehe ich diese prolog Fehler auch im aktuellsten nightly.

Baxxy13 Feb 3, 2025

Ne Kommando zurück mit meinen Logmeldungen, der rfd war nicht gestartet.
ReGa kann ich testen.

Baxxy13 Feb 3, 2025

ReGa 245 bringt keine Veränderung.

Baxxy13 · 2025-02-03T14:58:19Z

Baxxy13
Feb 3, 2025

Also ich kann es nun eingrenzen.
Nightly's vom 30.01. zeigen das Problem nicht.
Gemeldet hat @radioo-007 das Problem mit Nightly vom 31.01. und folgenden.
Die commits dazwischen waren überschaubar und ich kann mir aktuell nicht erklären woran das liegt.

1 reply

jens-maus Feb 3, 2025
Maintainer

Ok, dann sind/waren es die Änderungen an der /etc/monitrc. Siehe:

bf25dd8#diff-7206f55f26b0fd20c2b19337ae5d13e07e6e61e1524164e50876bc7b9e718bc3

D.h. ich werd die mal für den nächsten Nightly zurücknehmen und dann hören diese prolog Meldungen hoffentlich auf.

radioo-007 · 2025-02-03T16:42:03Z

radioo-007
Feb 3, 2025
Author

dies dient nur zur Information, wie die Monit für Lighttpd für die Version RaspberryMatic-3.79.6.20250203-bba7b7-rpi5 bei mir aussieht

2 replies

jens-maus Feb 3, 2025
Maintainer

danke. All das sieht man aber auch via monit status lighttpd kommandozeilenaufruf. Dafür braucht es kein Webinterface ;-)

Und in der Tat ist das problem das da bei Port 2010 bzw. 42010 jeweils protocol HTTP stand. Mit dem morgigen nightly (wo auch wieder die aktuellste Javaversion dabei ist) sollte das wieder behoben sein. Ergo: Das hab nie was mit der Javaversion zu tun gehabt...

radioo-007 Feb 3, 2025
Author

genau so wie du schreibst :-)

monit von RaspberryMatic-3.79.6.20250118-rpi5:

radioo-007 · 2025-02-04T05:07:25Z

radioo-007
Feb 4, 2025
Author

Ich bestätige, dass Version RaspberryMatic-3.79.6.20250204-07d3ef-rpi5 nun fehlerfrei ist

Monit 5.34.2 uptime: 10m

Process 'lighttpd'
  status                       OK
  monitoring status            Monitored
  monitoring mode              active
  on reboot                    start
  pid                          1709
  parent pid                   1
  uid                          0
  effective uid                0
  gid                          0
  uptime                       10m
  threads                      1
  children                     1
  cpu                          0.0%
  cpu total                    0.0%
  memory                       0.0% [512 kB]
  memory total                 0.2% [8 MB]
  security attribute           unconfined
  filedescriptors              3 [0.3% of 1024 limit]
  total filedescriptors        40
  read bytes                   0 B/s [2.0 kB total]
  disk read bytes              0 B/s [12 kB total]
  disk read operations         0.0 reads/s [6 reads total]
  write bytes                  0 B/s [5 B total]
  disk write bytes             0 B/s [0 B total]
  disk write operations        0.0 writes/s [1 writes total]
  port response time           0.520 ms to localhost:49292 type TCP/IP protocol DEFAULT
  port response time           11.044 ms to localhost:48181 type TCP/IP using TLS (certificate valid for 3343 days) protocol HTTP
  port response time           0.150 ms to localhost:42010 type TCP/IP protocol DEFAULT
  port response time           0.083 ms to localhost:42001 type TCP/IP protocol DEFAULT
  port response time           0.073 ms to localhost:42000 type TCP/IP protocol DEFAULT
  port response time           0.071 ms to localhost:41999 type TCP/IP protocol DEFAULT
  port response time           0.072 ms to localhost:9292 type TCP/IP protocol DEFAULT
  port response time           0.598 ms to localhost:8181 type TCP/IP protocol HTTP
  port response time           0.100 ms to localhost:2010 type TCP/IP protocol DEFAULT
  port response time           0.080 ms to localhost:2001 type TCP/IP protocol DEFAULT
  port response time           0.073 ms to localhost:2000 type TCP/IP protocol DEFAULT
  port response time           0.071 ms to localhost:1999 type TCP/IP protocol DEFAULT
  port response time           0.554 ms to localhost:80 type TCP/IP protocol HTTP
  port response time           10.368 ms to localhost:443 type TCP/IP using TLS (certificate valid for 3343 days) protocol HTTP
  data collected               Tue, 04 Feb 2025 06:14:58

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Neue Java 11.0.26 #3012

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 5 comments 11 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Neue Java 11.0.26 #3012

radioo-007 Feb 2, 2025

Replies: 5 comments · 11 replies

Baxxy13 Feb 2, 2025

Baxxy13 Feb 2, 2025

jens-maus Feb 2, 2025 Maintainer

radioo-007 Feb 3, 2025 Author

Baxxy13 Feb 3, 2025

jens-maus Feb 3, 2025 Maintainer

Baxxy13 Feb 3, 2025

Baxxy13 Feb 3, 2025

Baxxy13 Feb 3, 2025

jens-maus Feb 3, 2025 Maintainer

radioo-007 Feb 3, 2025 Author

jens-maus Feb 3, 2025 Maintainer

radioo-007 Feb 3, 2025 Author

radioo-007 Feb 4, 2025 Author

radioo-007
Feb 2, 2025

Replies: 5 comments 11 replies

Baxxy13
Feb 2, 2025

jens-maus
Feb 2, 2025
Maintainer

radioo-007 Feb 3, 2025
Author

jens-maus Feb 3, 2025
Maintainer

Baxxy13
Feb 3, 2025

jens-maus Feb 3, 2025
Maintainer

radioo-007
Feb 3, 2025
Author

jens-maus Feb 3, 2025
Maintainer

radioo-007 Feb 3, 2025
Author

radioo-007
Feb 4, 2025
Author