Business Community > Controllers > JAVA Error - Happened Suddenly
< Controllers

JAVA Error - Happened Suddenly

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

JAVA Error - Happened Suddenly

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
JAVA Error - Happened Suddenly
JAVA Error - Happened Suddenly
2023-09-01 04:45:11
Model: Omada Software Controller (Linux)  
Hardware Version: V5
Firmware Version:

Hi There,

 

I was trying to login to the web UI today, and it wasn't responsive.  So I went to restart the linux server to clear out any issue.


Still not able to login.

 

I then used tpeap stop, and got an error that it failed and will try killing.

 

When I start, I get an JAVA error.

 

I removed omada and java8 and re-installed both.  I still get an error, although it seems to change slightly. 

 

I have tried multiple versions as well.

 

Attached the most recent one here.  Any ideas?

 

root@omada:~# gdebi Omada_SDN_Controller_v5.8.4_Linux_x64.deb 
Reading package lists... Done
Building dependency tree        
Reading state information... Done
Reading state information... Done

Omada Controller
 TP-Link's Omada Controller Software is management software for TP-Link EAP devices. It allows users to easily manage hundreds of TP-Link EAPs in
 multiple sites with the controller in a single location. The ability to control, adjust, and visualize the entire network from any connected PC makes
 centralized business Wi-Fi management more efficient and cost-effective than ever before. The Omada Controller Software integrates seamlessly with
 TP-Link's EAP series devices to create cost-effective business Wi-Fi solutions that offer ultimate performance.
 For how to install Omada Controller on the Linux operation system, please refer to the faq: https://www.tp-link.com/en/support/faq/3272/
 If you are using the old controller and planning to upgrade to this version, please follow the Omada Controller Upgrade Guide.
 Upgrade Guide: https://www.tp-link.com/en/omada-sdn/controller-upgrade
Do you want to install the software package? [y/N]:y
Selecting previously unselected package omadac.
(Reading database ... 19196 files and directories currently installed.)
Preparing to unpack Omada_SDN_Controller_v5.8.4_Linux_x64.deb ...
Unpacking omadac (5.8.4) ...
Setting up omadac (5.8.4) ...
Install Omada Controller succeeded!
==========================
current data is empty
Omada Controller will start up with system boot. You can also control it by [/usr/bin/tpeap]. 
check omada

Starting Omada Controller. Please wait...............................................................................................................................................................................................................................................................................................................
Start failed.
========================
Processing triggers for systemd (237-3ubuntu10.57) ...
Processing triggers for ureadahead (0.100.0-21) ...

 

 

 

--startup.log--

java version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
commons daemon version "1.0.15-dev"
commons daemon process (id: 491, parent: 489)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f22bcd2a2ab, pid=491, tid=0x00007f22cf221740
#
# JRE version: OpenJDK Runtime Environment (8.0_362-b09) (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.362-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J 1879 C2 java.lang.String.getChars(II[CI)V (62 bytes) @ 0x00007f22bcd2a2ab [0x00007f22bcd2a220+0x8b]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting
 Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid491.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
java version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
commons daemon version "1.0.15-dev"
commons daemon process (id: 789, parent: 489)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f22bc972a43, pid=789, tid=0x00007f229baed700
#
# JRE version: OpenJDK Runtime Environment (8.0_362-b09) (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.362-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J 400 C1 java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class; (122 bytes) @ 0x00007f22bc972a43 [0x00007f22
bc9710c0+0x1983]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting
 Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid789.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp

java version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
commons daemon version "1.0.15-dev"
commons daemon process (id: 1077, parent: 489)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f22bc964303, pid=1077, tid=0x00007f229bab4700
#
# JRE version: OpenJDK Runtime Environment (8.0_362-b09) (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.362-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J 411 C1 java.lang.ClassLoader.loadClass(Ljava/lang/String;Z)Ljava/lang/Class; (122 bytes) @ 0x00007f22bc964303 [0x00007f22
bc962980+0x1983]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting
 Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1077.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
java version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
commons daemon version "1.0.15-dev"
commons daemon process (id: 1382, parent: 489)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f22bca16e3b, pid=1382, tid=0x00007f22cf221740
#
# JRE version: OpenJDK Runtime Environment (8.0_362-b09) (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.362-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J 689 C1 java.security.CodeSource.hashCode()I (17 bytes) @ 0x00007f22bca16e3b [0x00007f22bca16aa0+0x39b]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting
 Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1382.log

#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1382.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
java version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
commons daemon version "1.0.15-dev"
commons daemon process (id: 1677, parent: 489)
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f22bc8db64a, pid=1677, tid=0x00007f22cf221740
#
# JRE version: OpenJDK Runtime Environment (8.0_362-b09) (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.362-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J 202 C2 java.lang.String.hashCode()I (55 bytes) @ 0x00007f22bc8db64a [0x00007f22bc8db520+0x12a]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting
 Java again
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1677.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
java version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
commons daemon version "1.0.15-dev"
commons daemon process (id: 1905, parent: 489)

  0      
 
  0      
 
#1
Options
5 Reply
Re:JAVA Error - Happened Suddenly
2023-09-01 05:24:56 - last edited 2023-09-01 05:28:28

Note: I get the exact same error with 5.9.31.  Here is a copy of my java -version.


What is interesting is the error messages are all different in startup.log

 

root@omada:~# dpkg -i Omada_SDN_Controller_v5.9.31_Linux_x64.deb 
Selecting previously unselected package omadac.
(Reading database ... 19498 files and directories currently installed.)
Preparing to unpack Omada_SDN_Controller_v5.9.31_Linux_x64.deb ...
Unpacking omadac (5.9.31) ...
Setting up omadac (5.9.31) ...
Install Omada Controller succeeded!
==========================
current data is empty
Omada Controller will start up with system boot. You can also control it by [/usr/bin/tpeap]. 
check omada
Starting Omada Controller. Please wait...............................................................................................................................................................................................................................................................................................................
Start failed.
========================
Processing triggers for systemd (237-3ubuntu10.57) ...
Processing triggers for ureadahead (0.100.0-21) ...
root@omada:~# java -version
openjdk version "1.8.0_362"
OpenJDK Runtime Environment (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
OpenJDK 64-Bit Server VM (build 25.362-b09, mixed mode)
root@omada:~# 

  0  
  0  
#2
Options
Re:JAVA Error - Happened Suddenly
2023-09-05 02:25:56

  @MannyF 

 

"# An error report file with more information is saved as:
# /tmp/hs_err_pid1382.log "

 

Here is a little weird, did you look through it?

Just striving to develop myself while helping others.
  0  
  0  
#3
Options
Re:JAVA Error - Happened Suddenly
2023-09-05 09:05:21

Hello @MannyF,

 

Thank you so much for taking the time to post the issue on TP-Link community!

 

To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID230907416, please check your email box and ensure the support email is well received. Thanks!

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

 

Many thanks for your great cooperation and patience!

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#4
Options
Re:JAVA Error - Happened Suddenly
2023-09-10 21:17:20

  @Virgo Yes - didn't notice anything odd. I can't paste the full contents here as it says invalid URL and for some reason I can't upload the file.  Here is a short version


 

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f049df97a90, pid=748, tid=0x00007f04b08de740
#
# JRE version: OpenJDK Runtime Environment (8.0_362-b09) (build 1.8.0_362-8u372-ga~us1-0ubuntu1~18.04-b09)
# Java VM: OpenJDK 64-Bit Server VM (25.362-b09 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J 212 C2 java.lang.String.equals(Ljava/lang/Object;)Z (81 bytes) @ 0x00007f049df97a90 [0x00007f049df97a20+0x70]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   ***
#

---------------  T H R E A D  ---------------

Current thread (0x00005601eacd6800):  JavaThread "main" [_thread_in_Java, id=748, stack(0x00007ffca5e56000,0x00007ffca5f56000)]

siginfo: si_signo: 11 (SIGSEGV), si_code: 0 (SI_USER)

Registers:
RAX=0x0000000000000001, RBX=0x0000000000000004, RCX=0x0000000000000003, RDX=0x0000000000000002
RSP=0x00007ffca5f53088, RBP=0x0000000672c3d790, RSI=0x0000000000000004, RDI=0x00000000ffffffff
R8 =0x0000000000000004, R9 =0x0000000672c36d60, R10=0x0000000000000065, R11=0x0000000000000000
R12=0x0000000000000000, R13=0x00000005cc4b4688, R14=0x00000000b98968d1, R15=0x00005601eacd6800
RIP=0x00007f049df97a90, EFLAGS=0x0000000000010202, CSGSFS=0x002b000000000033, ERR=0x0000000000000004
  TRAPNO=0x000000000000000e

Top of Stack: (sp=0x00007ffca5f53088)
0x00007ffca5f53088:   00007f049df5c53c 00000007c009d9f8
0x00007ffca5f53098:   00000005cc4b4590 0000000500000001
0x00007ffca5f530a8:   00000005cc4b45d0 002ff57c00000039
0x00007ffca5f530b8:   00000007c00016d0 0000000000000000
0x00007ffca5f530c8:   0000000672c36a30 00000005cc4b4670
0x00007ffca5f530d8:   00005601b98968ce 00000000b98968bd
0x00007ffca5f530e8:   0000000000000000 0000007900000000
0x00007ffca5f530f8:   0000003900000039 0000000500000000
0x00007ffca5f53108:   00000005cc4b4670 0000000000000007
0x00007ffca5f53118:   1a14ae766ee2dd00 0000000000000001
0x00007ffca5f53128:   00000007c0011838 00007ffca5f535d0
0x00007ffca5f53138:   00007f049e5fc92c 000000000000003b
0x00007ffca5f53148:   0000000000000006 00007ffca5f531d0
0x00007ffca5f53158:   00007f04ae62194f 00000005cc4af338
0x00007ffca5f53168:   00000005cc4b4020 000000000000002e
0x00007ffca5f53178:   1a14ae766ee2dd00 00007ffca5f531d0
0x00007ffca5f53188:   00007f049850eee0 00005601eacd6800
0x00007ffca5f53198:   00005601eacd7560 000000000000005b
0x00007ffca5f531a8:   00007f049850eee0 00007ffca5f53220
0x00007ffca5f531b8:   00007f04ae4a279a 0000000000000000
0x00007ffca5f531c8:   00000007c0011838 00007f049850eee0
0x00007ffca5f531d8:   00000005d4909728 00000005cc4b4538
0x00007ffca5f531e8:   00000005cc4b4590 000000070000003a
0x00007ffca5f531f8:   00007ffca5f53250 00000007c002b250
0x00007ffca5f53208:   00007ffca5f53260 00007ffca5f532b0
0x00007ffca5f53218:   00007f04ae80793b 00007ffca5f535d0
0x00007ffca5f53228:   00007f049e250e7c 00007ffca5f532b0
0x00007ffca5f53238:   0000000000000001 00007ffca5f53270
0x00007ffca5f53248:   00007f04aea306f4 00007ffca5f53280
0x00007ffca5f53258:   0000000000800001 00007f0498535c88
0x00007ffca5f53268:   00000000000000b9 00007ffca5f532c0
0x00007ffca5f53278:   00007f04ae8c8c1e 00007f04aef2e108 

Instructions: (pc=0x00007f049df97a90)
0x00007f049df97a70:   43 8b 74 d4 0c 44 8b 72 0c 43 8b 5c f4 0c 3b f3
0x00007f049df97a80:   74 15 33 c0 eb 05 b8 01 00 00 00 48 83 c4 30 5d
0x00007f049df97a90:   85 05 6a 15 95 12 c3 85 f6 0f 84 5f 01 00 00 44
0x00007f049df97aa0:   8b d6 41 ff ca 4c 63 c6 c4 c1 79 7e d9 49 c1 e1 

Register to memory mapping:

RAX=0x0000000000000001 is an unknown value
RBX=0x0000000000000004 is an unknown value
RCX=0x0000000000000003 is an unknown value
RDX=0x0000000000000002 is an unknown value
RSP=0x00007ffca5f53088 is pointing into the stack for thread: 0x00005601eacd6800
RBP=0x0000000672c3d790 is an oop
java.util.Hashtable$Entry 
 - klass: 'java/util/Hashtable$Entry'
RSI=0x0000000000000004 is an unknown value
RDI=0x00000000ffffffff is an unknown value
R8 =0x0000000000000004 is an unknown value
R9 =0x0000000672c36d60 is an oop
[C 
 - klass: {type array char}
 - length: 4
R10=0x0000000000000065 is an unknown value
R11=0x0000000000000000 is an unknown value
R12=0x0000000000000000 is an unknown value
R13=
[error occurred during error reporting (printing register info), id 0xb]

Stack: [0x00007ffca5e56000,0x00007ffca5f56000],  sp=0x00007ffca5f53088,  free space=1012k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
J 212 C2 java.lang.String.equals(Ljava/lang/Object;)Z (81 bytes) @ 0x00007f049df97a90 [0x00007f049df97a20+0x70]
C  0x0000000000000000

 

 

  0  
  0  
#5
Options
Re:JAVA Error - Happened Suddenly
2023-09-11 02:59:58

Hello @MannyF,

 

Our senior engineer has received your feedback on the issue via email, they will continue to follow up with your case. If you have any additional information, please feel free to reply to the support email whose case ID is TKID230907416. Many thanks for your cooperation and patience!

 

Thank you for your valued update on the case.

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#6
Options

Information

Helpful: 0

Views: 725

Replies: 5

Related Articles
omada setup "general error"
875 0
Java Exceptions in Startup log file
515 0
General Error while trying to apply settings for WANs
951 0
Be aware of Omada Controller on Linux with Java 17
248 1
No connection through Powerline. Just happened today!
174 0
MAC Listing Module Error
345 0
About Us
Press
Copyright © TP-LINK CORPORATION PTE. LTD. All rights reserved.