Revolving around the core of technology
Hey Guys,
Just got the issue where the Syncrify server has stopped running after someone reset the box it was running on.
Have the following in the log
2019-08-13 14:56:44,576 INFO sradef.BootLoader - -------------------- New Instance started --------------.
2019-08-13 14:56:44,576 INFO db.a - Reinitializing database...
2019-08-13 14:56:45,215 ERROR db.a - Unable to connect to Database. DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041, SQLERRMC: Failed to create database 'syncrifyDB', see the next exception for details.::SQLSTATE: XBM02Startup failed due to missing functionality for org.apache.derby.iapi.store.access.AccessFactory. Please ensure your classpath includes the correct Derby software.
java.sql.SQLException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041, SQLERRMC: Failed to create database 'syncrifyDB', see the next exception for details.::SQLSTATE: XBM02Startup failed due to missing functionality for org.apache.derby.iapi.store.access.AccessFactory. Please ensure your classpath includes the correct Derby software.
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(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at com.synametrics.commons.util.d.a.g(Unknown Source)
at com.synametrics.commons.util.d.a.(Unknown Source)
at com.synametrics.commons.util.d.a.a(Unknown Source)
at com.synametrics.sradef.db.a.(Unknown Source)
at com.synametrics.sradef.db.a.a(Unknown Source)
at com.synametrics.sradef.BootLoader.main(Unknown Source)
at com.synametrics.syncrify.server.ServerService.main(Unknown Source)
at com.synametrics.syncrify.server.ServerService.start(Unknown Source)
Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041, SQLERRMC: Failed to create database 'syncrifyDB', see the next exception for details.::SQLSTATE: XBM02Startup failed due to missing functionality for org.apache.derby.iapi.store.access.AccessFactory. Please ensure your classpath includes the correct Derby software.
at org.apache.derby.client.am.Connection.completeSqlca(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseRdbAccessFailed(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(Unknown Source)
at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(Unknown Source)
at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source)
at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
at org.apache.derby.client.net.NetConnection.(Unknown Source)
at org.apache.derby.client.net.NetConnection40.(Unknown Source)
at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(Unknown Source)
... 11 more
2019-08-13 14:56:45,215 INFO sradef.BootLoader - Working directory: C:\Syncrify
2019-08-13 14:56:45,246 INFO syncrify.Ignition - Starting up. Build number: 833, instance #: 21
2019-08-13 14:56:45,293 INFO d.c - Status server is now ready to accept connections...
Restarting the service or rebooting the machine further didn't help.
Try the following steps:
Once Syncrify comes up, some of your reports will get messed up but it should work as far as backup goes
Thanking you muchly, seems to have done the trick.
Any ideas what happened so we can try to avoid it in the future? Or the db just had a bad day
Syncrify contains an embedded SQL server that is used for reporting purposes. If the process is shut down abruptly, this embedded DB could get corrupted, causing this problem. Removing the $INSTALL_DIR\db folder removes the database forcing Syncrify to recreate it on next restart.
Having a similar issue again, although no errors in the log.
Just have the following
[2019-12-13 08:39:00] [info] Commons Daemon procrun (1.0.10.0 64-bit) started
[2019-12-13 08:39:00] [info] Running 'Syncrify' Service...
[2019-12-13 08:39:00] [info] Starting service...
[2019-12-13 08:39:01] [info] Service started in 1201 ms.
[2019-12-13 08:48:44] [info] Stopping service...
[2019-12-13 08:50:49] [info] Commons Daemon procrun (1.0.10.0 64-bit) started
[2019-12-13 08:50:49] [info] Running 'Syncrify' Service...
[2019-12-13 08:50:49] [info] Starting service...
[2019-12-13 08:50:50] [info] Service started in 1123 ms.
Server doesn't appear to be listening on port 5800