Page History

...

This is generally a different symptom of the same problem as above (flows stuck in PENDING_ADD). If ONOS can’t match the returned flow stats with flow rules in the store, it will remove what it considers to be an extraneous flow and install the flow in the store again. The solution to this problem is to ensure that ONOS can match observed flows with its internal flow store.

Where can I find the ONOS log?

The ONOS log is located on disk at <KARAF_ROOT>/data/log/karaf.log (e.g. this usually means it can be found at /opt/onos/karaf/data/log/karaf.log).

If you run ONOS locally using onos-karaf you can use the tool onos-local-log to follow the log.

If you run ONOS remotely using onos-install, you can use the tool onos-log <instance> (e.g. onos-log $OC1) to follow the log.

How can I tell if ONOS encountered an error at runtime?

Often errors can be found in the log if something goes wrong. You can either find the log file on disk and look in there (see above question) or from the ONOS shell you can view the log using log:display.

log:exception-display will show the last exception in the log.

log:display | grep ERROR will show any errors in the log.