Firmwsre update is available, but it fails.
EAP670 with omada software cloud(5.12.7)
keep notify me a new firmware is available.
new firmware version: 1.0.12 20230922 rel. 53972
When let it update, it fails.
Am I missing something?
I bought device from Amazon US, (US Device)
I live in South Korea now.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello @everich,
Thanks for reporting this issue to our Business Community!
This issue has been reported to the engineer for further investigation. I'll try to provide an update when there's progress.
You may choose to go to the official website and download the file to upgrade the firmware for EAP670 manually.
- Copy Link
- Report Inappropriate Content
New firmware is only available in Korean webpage.
It is not available in US webpage.
And upgrading from binary(new firmwsre in Korean website) also fails.
Hank21 wrote
Hello @everich,
Thanks for reporting this issue to our Business Community!
This issue has been reported to the engineer for further investigation. I'll try to provide an update when there's progress.
You may choose to go to the official website and download the file to upgrade the firmware for EAP670 manually.
- Copy Link
- Report Inappropriate Content
I had the same issue, but it was resolved by a manual firmware update.
https://community.tp-link.com/en/business/forum/topic/637218?replyId=1273970
- Copy Link
- Report Inappropriate Content
I attached "server.log"
it says " java.lang.OutOfMemoryError: Java heap space"
--- my workaround --
1. Installed a new version of Omada controller for Windows.
2. Forget a device from my old Omada software controller.
3. Adopt from Omada for Windows
4. Upgrade firmware.
5. Forget from Omada for Windows.
6. Adopt from Omada software Controller.
- Copy Link
- Report Inappropriate Content
Hi @everich,
Thanks for your updates!
The support senior engineer is still working on this, and I have sent the feedback to US local team for updating the new firmware information timely. Thanks for your valuable feedback.
- Copy Link
- Report Inappropriate Content
Hi @everich,
After confirming with the R&D department, it is suspected that the current issue may be caused by the heap memory overflow problem, please confirm whether the JRE version of your Omada Controller running environment is 32-Bit?
You can enter "java -version" in the command line, if it is 64-Bit, there will be a -64 bit mark as below image.
If you are running the 32-Bit, please update it to 64-Bit version and try upgrading the EAP's firmware version again.
- Copy Link
- Report Inappropriate Content
Hello, @Hank21
My environment is like following...
ubuntu@omada:/etc$ uname -a
Linux omada 5.15.0-1047-oracle #53-Ubuntu SMP Wed Oct 18 09:56:06 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@omada:/etc$ cat lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
ubuntu@omada:/etc$ java -version
openjdk version "1.8.0_382"
OpenJDK Runtime Environment (build 1.8.0_382-8u382-ga-1~22.04.1-b05)
OpenJDK 64-Bit Server VM (build 25.382-b05, mixed mode)
ubuntu@omada:/etc$ vmstat
procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
r b swpd free buff cache si so bi bo in cs us sy id wa st
1 0 328236 88816 1028 121888 11 12 252 27 136 244 1 1 97 0 1
I assume changing "JAVA_OPTS" in control.sh could help.
ubuntu@omada:/opt/tplink/EAPController/bin$ cat control.sh
#!/bin/bash
#
# startup script for TP-Link's EAP Controller.
#
### BEGIN INIT INFO
# Provides: omada
# Required-Start: $local_fs $remote_fs $network $syslog
# Required-Stop: $local_fs $remote_fs $network $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Omada Controller
# Description: TP-Link's Omada Controller.
### END INIT INFO
NAME="omada"
DESC="Omada Controller"
OMADA_HOME=$(dirname $(dirname $(readlink -f $0)))
LOG_DIR="${OMADA_HOME}/logs"
WORK_DIR="${OMADA_HOME}/work"
DATA_DIR="${OMADA_HOME}/data"
PROPERTY_DIR="${OMADA_HOME}/properties"
AUTOBACKUP_DIR="${DATA_DIR}/autobackup"
JRE_HOME="$( readlink -f "$( which java )" | sed "s:bin/.*$::" )"
JAVA_TOOL="${JRE_HOME}/bin/java"
JAVA_OPTS="-server -XX:MaxHeapFreeRatio=60 -XX:MinHeapFreeRatio=30 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=${LOG_DIR}/java_heapdump.hprof -Djava.awt.headless=true"
- Copy Link
- Report Inappropriate Content
Hi @everich,
Thanks for such detailed info, I've escalated these logs to the support engineers for further investigation, will update soon.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 2
Views: 781
Replies: 8