EM collector log filling up with postgres error

[David Richards]

Hi - running APM 9.5.2 - Introscope only.

 

Our EM logs are filling up with this error - I can't see anything in KB or online for this. Any ideas what we need to do to fix ?

 

 

 

20160522 095412 BST [INFO] [Manager.com.timestock.tess.util.DbUtils] Retrying defect partition creation for 2016-05-21

20160522 095412 BST [ERROR] [Manager.com.timestock.tess.util.DbUtils] Unable to create defect partition for 2016-05-21

org.postgresql.util.PSQLException: ERROR: relation "ts_defects_20160521" already exists

        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)

        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)

        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)

        at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)

        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:353)

        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:299)

        at com.mchange.v2.c3p0.impl.NewProxyStatement.executeUpdate(NewProxyStatement.java:64)

        at com.timestock.tess.util.DbUtils.executeDDL(DbUtils.java:5490)

        at com.timestock.tess.util.DbUtils.createDefectPartitionsPostgres(DbUtils.java:6116)

        at com.timestock.tess.util.DbUtils.createDefectPartitions(DbUtils.java:6069)

        at com.timestock.tess.util.DbUtils$DefectPartitionCreator.createPartitions(DbUtils.java:6041)

        at com.timestock.tess.util.DbUtils.createMissingPartitions(DbUtils.java:5979)

        at com.timestock.tess.util.DbUtils.createMissingDefectPartitions(DbUtils.java:6055)

        at com.timestock.tess.services.scheduler.CreateDefectPartitionsTask.run(CreateDefectPartitionsTask.java:41)

        at com.timestock.tess.util.ScheduledRunnable.run(ScheduledRunnable.java:54)

        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)

        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)

        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

        at java.lang.Thread.run(Unknown Source)

[Michael Cook]

Hi Dave,

 

As discussed, the problem is as a result of each collector in the cluster trying to run the CEM processes and create the partitions. This is because the installations were cloned rather than individually installed. If you clone the installation you need to delete the file EMHOME/config/internalserver/tess.internal.properties before starting teh collector (or cloning) as this contains the unique identifier which the APM database holds against the system responsible fro running the various service. On startup the file will be regenerated if not present and so that way each collector will be truly unique and the processing will only be run on one collector in the cluster and so this clash should not take place.

 

cheers

Mike

[Hallett German]

Hi Dave:

It looks like Mike has answered your question. May we mark this thread as closed? Or are there followup questions?

 

Thanks

Hal German

[David Richards]

No you can close this, thank you.

 

 

Dave Richards

PaaS APM Team

03301535505

 

http://middlewarewiki.barclays.co.uk/doku.php?id=components:wily

 

http://teams.barclays.intranet/sites/apaas/SitePages/Wily%20Cartridge.aspx