How to settle db not found issue

2019-12-12 09:48:34,767 INFO  xeams.ServerStarter - Received message to terminate Rules Engine from unknown
2019-12-12 09:48:34,783 INFO  xeams.ServerStarter - Clean routines ran successfully...
2019-12-12 09:48:34,793 INFO  db.ka - Database 'xeamsDB' not found.
2019-12-12 09:48:34,909 INFO  xeams.I - Server terminating...
2019-12-12 09:48:41,200 INFO  xeams.ServerStarter - ---------------------------------------------------
2019-12-12 09:48:41,214 INFO  xeams.ServerStarter - Starting server. Current directory = /opt/Xeams. Time = 12/12/19 9:48 AM. Build number: 6081 on Linux
2019-12-12 09:52:08,058 ERROR db.ka - Could not ping Derby server. DRDA_NoIO.S:Could not connect to Derby Network Server on host localhost, port 7865: Connection refused (Connection refused)
2019-12-12 09:52:08,174 ERROR db.ka - Unable to connect to Database. java.net.ConnectException : Error connecting to server localhost on port 7865 with message Connection refused (Connection refused).
java.sql.SQLNonTransientConnectionException: java.net.ConnectException : Error connecting to server localhost on port 7865 with message Connection refused (Connection refused).
	at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source)
	at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
	at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
	at java.sql.DriverManager.getConnection(DriverManager.java:664)
	at java.sql.DriverManager.getConnection(DriverManager.java:247)
	at com.synametrics.commons.util.c.D.h(ConnectionPool.java:168)
	at com.synametrics.commons.util.c.D.<init>(ConnectionPool.java:158)
	at com.synametrics.commons.util.c.D.h(ConnectionPool.java:106)
	at com.synametrics.xeams.db.ka.h(DBConfigurator.java:56)
	at com.synametrics.xeams.db.ka.<init>(DBConfigurator.java:26)
	at com.synametrics.xeams.db.ka.h(DBConfigurator.java:35)
	at com.synametrics.xeams.ServerStarter.h(ServerStarter.java:399)
	at com.synametrics.xeams.ServerStarter.main(ServerStarter.java:150)
2019-12-12 09:52:08,220 INFO  xeams.rulesengine - Good folder is: /opt/Xeams/GoodEmails
2019-12-12 09:52:08,220 INFO  xeams.rulesengine - Spam folder is: /opt/Xeams/SpamEmails
2019-12-12 09:52:08,220 INFO  xeams.rulesengine - Possible spam folder is: /opt/Xeams/PossibleSpams
2019-12-12 09:52:08,314 WARN  util.t - The profile id read from file is 0, but in memory value = 1
2019-12-12 09:52:08,923 INFO  custom.AntiPhishingUpdate - Fetching AntiPhishing files
2019-12-12 09:52:09,874 INFO  xeams.ServerStarter - Profile 1 initialized.
2019-12-12 09:52:09,924 INFO  util.B - SMTP Queue thread successfully started
2019-12-12 09:52:13,721 WARN  v.h - Unable to fetch current time.
2019-12-12 09:52:47,656 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.
2019-12-12 09:52:47,672 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.
2019-12-12 09:54:05,595 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.
2019-12-12 09:55:01,285 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.
2019-12-12 09:55:54,706 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.
2019-12-12 09:55:54,934 INFO  g.j - SMTP server successfully started on port 25
2019-12-12 09:56:06,001 INFO  g.j - SMTP server is now ready to accept connections...
2019-12-12 09:57:12,089 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.
2019-12-12 09:57:56,595 WARN  users.d - Config file config/UserConfig.xml not found. Cannot continue reading.
2019-12-12 09:58:07,543 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.

Xeams contains an embedded SQL server that is used for reporting purposes. It appears to be corrupted. Try the following steps to fix this error:

• Stop Xeams 
• Delete/Rename /opt/Xeams/db folder 
• Restart Xeams

The folder will be recreated. Xeams will run a bit slow initially until this database is populated again. 

I have tried,but same result.

I have MySQL running on the same server,is it the problem for xeams db not create issue? But seems xeams db connect to 7865.

MySQL is on 3306 port

2019-12-12 10:35:59,284 INFO  xeams.rulesengine - Good folder is: /opt/Xeams/GoodEmails
2019-12-12 10:35:59,284 INFO  xeams.rulesengine - Spam folder is: /opt/Xeams/SpamEmails
2019-12-12 10:35:59,284 INFO  xeams.rulesengine - Possible spam folder is: /opt/Xeams/PossibleSpams
2019-12-12 10:35:59,386 WARN  util.t - The profile id read from file is 0, but in memory value = 1
2019-12-12 10:36:00,930 WARN  users.d - Config file config/UserConfig.xml not found. Cannot continue reading.
2019-12-12 10:36:00,939 INFO  custom.AntiPhishingUpdate - Fetching AntiPhishing files
2019-12-12 10:36:01,853 INFO  xeams.ServerStarter - Profile 1 initialized.
2019-12-12 10:36:01,879 INFO  util.B - SMTP Queue thread successfully started
2019-12-12 10:36:08,365 WARN  v.h - Unable to fetch current time.
2019-12-12 10:39:22,189 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.
2019-12-12 10:41:13,019 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.
2019-12-12 10:49:52,915 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds. 
2019-12-12 10:50:36,870 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds. 
2019-12-12 10:51:38,992 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds. 
2019-12-12 10:52:18,856 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds. 
2019-12-12 11:20:30,627 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds. 
2019-12-12 11:21:18,129 ERROR servlet.FrontController - Unable to get a database connection after waiting for 40 seconds.

What is the hostname of your machine? Are you able to ping the hostname? If the machine is not able to resolve the IP address of its own hostname, you will run into errors starting the embedded DB. If you cannot resolve the IP when pinging the hostname, add an entry in /etc/hosts file.

The presence of MySQL has nothing to do with this problem.

resolved,it is hostname issue.