Re: Deadlock monitor error

Maros Marsalek -X (mmarsale - PANTHEON TECHNOLOGIES@Cisco)

Hi Sagar,


This part of the log is interesting:

2016-03-09 00:14:32,405 | ERROR | ult-dispatcher-4 | OneForOneStrategy                | 123 - com.typesafe.akka.slf4j - 2.3.14 | IO error: /honeycomb/v3po/karaf/target/assembly/journal/MANIFEST-000001: Invalid argument exception during creation


Caused by: org.fusesource.leveldbjni.internal.NativeDB$DBException: IO error: /honeycomb/v3po/karaf/target/assembly/journal/MANIFEST-000001: Invalid argument

     at org.fusesource.leveldbjni.internal.NativeDB.checkStatus([126:org.fusesource.leveldbjni.leveldbjni-all:1.8.0]


Suggesting there’s a problem with some data in journal folder stored by clustered data store.


So what you can do is: clean the distribution and run again. And to clean it, just perform a delete in the distro folder:


rm –rf journal data snapshots instances etc/opendaylight


And the distro will be good as new.

Btw. This error occurred with the first run of honeycomb ? Or on one of the subsequent runs ?





From: honeycomb-dev-bounces@... [mailto:honeycomb-dev-bounces@...] On Behalf Of SAGAR SRIVASTAV
Sent: Wednesday, March 09, 2016 9:41 AM
To: honeycomb-dev@...
Subject: [honeycomb-dev] Deadlock monitor error




I am Sagar, a final year undergrad engineering student. I am trying to bring up the honeycomb agent demo. for that i did a vagrant up in the vagrant-demo directory. however, when i run karaf i get a bunch of exceptions and deadlock monitor errors like the one below.



2016-03-08 21:38:32,015 | WARN  | saction-86-88'}} | DeadlockMonitor                  | 86 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | ModuleIdentifier{factoryName='netconf-mdsal-monitoring-mapper', instanceName='netconf-mdsal-monitoring-mapper'} did not finish after 171098 ms



i get the same issue in both v3po and vbd


I have attached the karaf log with the email. is this a known issue? 




Join to automatically receive all group messages.