Java runtime error on Raspberry Pi 2 with Omada SDN Linux 3.2.10
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have a Raspberry Pi 2B with no use and decided to follow the instruction found on other forum to setup Omada SDN Controller Linux 3.2.10.
Everything work well except failed to retrieve clients information on my EAP245 with statistics.
The "Clients of SSID" on the statistics dashboard only display "Waiting for data"
Further troubleshoot and find some Java runtime error in server.log file.
Java use OpenJDK 8.0.
Appreciated in advance for any help to resolve the error.
2020-08-18 13:48:27 [defaultEventExecutorGroup-4-1] [ERROR]-[SourceFile:21] - java.lang.NullPointerException
java.lang.NullPointerException: null
at com.tp_link.eap.a.b.a(SourceFile:403) ~[eap-infrastructure-3.2.10.jar:?]
at com.tp_link.eap.a.b.b(SourceFile:374) ~[eap-infrastructure-3.2.10.jar:?]
at com.tp_link.eap.a.b.b(SourceFile:190) ~[eap-infrastructure-3.2.10.jar:?]
at com.tp_link.eap.monitor.monitor.b.f.a(SourceFile:171) ~[eap-monitor-3.2.10.jar:?]
at com.tp_link.eap.monitor.monitor.b.f.b(SourceFile:120) ~[eap-monitor-3.2.10.jar:?]
at com.tp_link.eap.device.c.a.a(SourceFile:18) [eap-device-3.2.10.jar:?]
at com.tp_link.eap.device.ActiveDevice.dispatch(SourceFile:27) [eap-device-3.2.10.jar:?]
at com.tp_link.eap.device.AbstractDevice.handle(SourceFile:37) [eap-device-3.2.10.jar:?]
at com.tp_link.eap.device.c.handle(SourceFile:38) [eap-device-3.2.10.jar:?]
at com.tp_link.eap.device.AbstractDevice.knock(SourceFile:31) [eap-device-3.2.10.jar:?]
at com.tp_link.eap.device.DeviceContext.knock(SourceFile:119) [eap-device-3.2.10.jar:?]
at com.tp_link.eap.k.e.c.a(SourceFile:41) [eap-net-3.2.10.jar:?]
at com.tp_link.eap.k.h.d.a.a.a(SourceFile:88) [eap-net-3.2.10.jar:?]
at com.tp_link.eap.k.h.d.a.a.channelRead(SourceFile:52) [eap-net-3.2.10.jar:?]
at io.netty.channel.ChannelHandlerInvokerUtil.invokeChannelReadNow(ChannelHandlerInvokerUtil.java:74) [netty-all-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at io.netty.channel.DefaultChannelHandlerInvoker$6.run(DefaultChannelHandlerInvoker.java:143) [netty-all-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at io.netty.util.concurrent.DefaultEventExecutor.run(DefaultEventExecutor.java:57) [netty-all-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:794) [netty-all-5.0.0.Alpha1.jar:5.0.0.Alpha1]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212]
2020-08-18 13:48:32 [qtp30949313-76] [WARN]-[SourceFile:325] - sessionCSRFToken is null for request /
2020-08-18 13:48:57 [defaultEventExecutorGroup-4-1] [ERROR]-[SourceFile:21] - java.lang.NullPointerException
java.lang.NullPointerException: null
at com.tp_link.eap.a.b.a(SourceFile:403) ~[eap-infrastructure-3.2.10.jar:?]
Hi @helloworld1,
please note that TP-Link does not support the Omada community version.
Do you mean the display doesn't change after a client has connected to the EAP245?
I cannot reproduce this on my Raspi3 using Oracle's JRE8.
»Waiting for data« is shown when no clients are connected:
As soon as a client connects, it changes to a diagram:
This does not look good. Maybe it's caused by OpenJDK.
If you don't mind, install Raspbian's Oracle JRE8 package (jdk-8-oracle-arm32-vfp-hflt) using apt or apt-get. IIRC, both JREs can co-exist and are selected using the update-java-alternatives(8) mechanism (see the manpage).