Ask Your Question
0

Runtime logs don't show up

asked 2014-11-14 04:28:29 -0700

skywalker gravatar image

updated 2014-11-14 16:00:30 -0700

I am using helium - integration, I tried both the master and the stable branch. I think that the runtime log is not working due to the messages that I see during the start of odl:

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [bundleresource://287.fwk148765233:1/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://287.fwk148765233:2/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [bundleresource://287.fwk148765233:3/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.JDK14LoggerFactory]

Just to clarify, I call runtime logs the messages that were showing up in hydrogen. The ones set in: LoggerFactory.getLogger(<class>).(info|debug|warn|trace)("msg")

These are the features that I have installed.

$ feature:install odl-restconf
$ feature:install odl-l2switch-switch
$ feature:install odl-mdsal-apidocs

$ feature:install odl-adsal-all
$ feature:install odl-adsal-northbound

$ feature:install odl-dlux-core

In logback.xml I set <logger name="org.opendaylight" level="DEBUG"/>

Do you have any suggestions?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
1

answered 2014-11-15 07:30:38 -0700

skywalker gravatar image

The following command does what I was expecting.

log:tail        Continuously display log entries. Use ctrl-c to quit this command

It is a better and a cleaner way. You can use one separate window/tab for logging messages.

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2014-11-14 04:28:29 -0700

Seen: 249 times

Last updated: Nov 15 '14