On 9/20/18 5:40 AM, Tom Pantelis wrote:
On Thu, Sep 20, 2018 at 1:45 AM Jamo Luhrsen <jluhr...@gmail.com
<mailto:jluhr...@gmail.com>> wrote:
> No - not with the default INFO logging. In order to dig deeper we need
to enable targeted debug, in this
> case org.opendaylight.controller.cluster.datastore.entityownership.
I don't think it worked. Here is what the logger config lines looked
like:
22:38:53
log4j2.logger.org_opendaylight_org_opendaylight_controller_cluster_datastore_entityownership.name
<http://log4j2.logger.org_opendaylight_org_opendaylight_controller_cluster_datastore_entityownership.name>
=
org.opendaylight.org
<http://org.opendaylight.org>.opendaylight.controller.cluster.datastore.entityownership
22:38:53
log4j2.logger.org_opendaylight_org_opendaylight_controller_cluster_datastore_entityownership.level
= DEBUG
The package name is wrong - has an extra "org.opendaylight" - should be
"org.opendaylight.controller.cluster.datastore.entityownership"
Thanks for catching this.
I finally have it reproduced for you:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/builder-copy-sandbox-logs/445/jamo-controller-csit-3node-clustering-ask-all-oxygen/1/robot-plugin/log.html.gz#s1-s14-t9-k2-k1-k1-k4
Here's a JIRA for us to track this better:
https://jira.opendaylight.org/browse/CONTROLLER-1865
The suite takes aprox 90 from start to finish and it's just a matter of
adding a single string to the parameters when we start the build. This
failure has happened 2 of the 3 jobs we ran. That's easiest for now,
and splitting up the karaf logs after the fact shouldn't be too bad.
OK - can you do the log file splitting then?
no, but it's really not hard. For this specific job, you can pull the
karaf logs locally and run this single command to extract just the
logs from the suite that failed. you can tweak it even further if you
want to narrow it more.
sed -n "/16.59.*ROBOT MESSAGE: Starting
suite/,/restart_odl_with_tell_based_false/p" odl1_karaf.log > 1.log
the key piece is that '16.59' string which is part of a timestamp that
I had to dig up from the robot logs to make sure it was getting the
right piece.
Thanks,
JamO
Thanks,
JamO
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
