TrueSight.log shows: ERROR 11/20 14:14:35.673 [DevMOMsg_1] c.b.t.a.qmgr.TSQueue BMC_TS-CA000023E Error processing task <FQDN> Exception while processing task in QManager org.hibernate.TransactionException: rollback failed at org.hibernate.engine.transaction.spi.AbstractTransactionImpl.rollback(AbstractTransactionImpl.java:217) at com.bmc.truesight.api.extended.device.DevicesDao.updateDevice(DevicesDao.java:2038) at com.bmc.truesight.platform.etl.device.task.TSIMDeviceCRUDTask.processDeltaChanges(TSIMDeviceCRUDTask.java:312) at com.bmc.truesight.platform.etl.device.task.TSIMDeviceCRUDTask.process(TSIMDeviceCRUDTask.java:120) at com.bmc.truesight.api.qmgr.TSQueue.run(TSQueue.java:85) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: org.hibernate.TransactionException: unable to rollback against JDBC connection at org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doRollback(JdbcTransaction.java:167) at org.hibernate.engine.transaction.spi.AbstractTransactionImpl.rollback(AbstractTransactionImpl.java:211) |
From the error in the TrueSight.log, there is was a DB replication problem between the two TSPS servers. (In this case, the Secondary node was OK, but the Primary node was not OK. So the solution is to manually 'sync' the working DB from the Secondary to the Primary) Stop both TSPS nodes (tssh server stop) On Primary: Rename /opt/bmc/TrueSightPServer/truesightpserver/data/ On Secondary: Copy /opt/bmc/TrueSightPServer/truesightpserver/data/ to Primary. Ensure that ownership & permissions are OK on Primary Start Primary (tssh server start) If this is successful, review the environment to investigate what caused the problem with the DB replication (e.g. network problems) |