The issue occurs due to one or more of the following causes. Check the error message and trouble and fix the issue based on the error message.
Potential cause 1 and solution
Error message
You can see more details in logs/config-center.log
Cause
You turned off the output in the startup.sh
script of the lightweight configuration center to reduce the number of standard output
logs.
nohup $JAVA -Daddress.server.ip=$SERVER_IP -Dderby.system.home=../ -jar -Dderby.stream.error.file=logs/derby.log ../lib/edas-config-center.jar --logging.config=../conf/logback.xml >/dev/null 2>&1 &
startup.bat
.
Solution
Make sure that JDK 1.8 or later is installed and is being used.
Potential cause 2 and solution
Error message
Unable to start embedded Tomcat servlet container
Tomcat connector in failed state
Solution
Check whether port 8080 is being used. If the port is used by another program, stop the program, and run the startup script again.
- Windows
- Open Command Prompt, run the
netstat -aon|findstr "8080"
script, and record the number in the last column of the queried dataPID (Process ID)
, for example, 2720. - Run
tasklist|findstr "2720"
. The program that is related to the current process ID (PID) is displayed, for example, javaw.exe. - Run
taskkill /PID 2720 /T /F
. - Start the lightweight configuration center again.
- Open Command Prompt, run the
- Linux
- Run netstat -antp|grep 8080. Then, the PID and program of the process that uses port 8080 appears, for example 2720.
- Run kill -9 2720.
- Start the lightweight configuration center again.
Potential cause 3 and solution
Error message
Caused by: java.net.UnknownHostException:iZ25ax7xuf5Z
Solution
iZ25ax7xuf5Z indicates the current host name. Check whether the IP address and the name of the current host are specified in /etc/hosts. If not, specify the IP address and the name, for example, 192.168.1.10 iZ25ax7xuf5Z.