When running the instructions from our Run wiki page, still errors can happen. This page will try to address some common issues we have seen that could help to successfully run all components.
Table of Contents |
---|
Log collection
In order to collect logs from a docker container you can use the following command:
...
Warnings can be also checked, using WARN
instead or ERR
in the command above.
Did SDNC (A1 Controller) start correctly?
If using A1 Controller (SDNC & A1 Adapter), SDNC should be started. Specifically, mariadb
and sdnc_image
must have started correctly.
Check MariaDB container
If you can see the following message in the logs for DB container:
Code Block | ||||
---|---|---|---|---|
| ||||
sdnc_db_container | 2021202x-10-28 14:39:34+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql' sdnc_db_container | 2021202x-10-28 14:39:34+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.12+maria~focal started. sdnc_db_container | 2021202x-10-28 14:39:35+00:00 [ERROR] [Entrypoint]: Database is uninitialized and password option is not specified sdnc_db_container | You need to specify one of MARIADB_ROOT_PASSWORD, MARIADB_ALLOW_EMPTY_ROOT_PASSWORD and MARIADB_RANDOM_ROOT_PASSWORD sdnc_db_container exited with code 1 |
...
Code Block | ||||
---|---|---|---|---|
| ||||
sdnc_db_container | 2023202x-01-28 14:43:56 0 [Note] mysqld: ready for connections. |
Check SDNC container
Make sure the following message has appear in the console of the docker-compose before continue the rest of the wiki page:
Code Block | ||||
---|---|---|---|---|
| ||||
sdnc_controller | Apache Karaf starting up. Press Enter to open the shell now... 100% [========================================================================] sdnc_controller | sdnc_controller | Karaf started in 0s. Bundle stats: 19 active, 19 total sdnc_controller | Certificate installation in progress. Elapsed time - 10 secs. Waiting for 10 secs before checking the status.. sdnc_controller | Certificate installation in progress. Elapsed time - 20 secs. Waiting for 10 secs before checking the status.. sdnc_controller | Certificate installation in progress. Elapsed time - 30 secs. Waiting for 10 secs before checking the status.. sdnc_controller | Start cert provisioning. Log file: /opt/opendaylight/current/data/log/installCerts.log sdnc_controller | Certificate installation script completed execution sdnc_controller | Everything OK in Certificate Installation |
Check SDNC logs
Logs from sdnc_controller
container can be found in /opt/opendaylight/data/log/karaf.log
directory from the sdnc_controller
container. To collect the logs, the following command can be used:
...
If there is any error in SDNC you can contact CCSDK/SDNC team for help.
Did A1 Policy Management Service start correctly?
Volume not mounted properly
The A1 Policy Management Service is unlikely to operate as expected if its configuration files (volumes) are not loaded/mounted correctly.
For example:
2021202x-10-29 07:23:04.878 DEBUG 1 --- [ parallel-2] o.o.c.o.a.dmaap.DmaapMessageConsumer : InfiniteFlux.onRequest 1
2021202x-10-29 07:23:04.879 DEBUG 1 --- [ parallel-2] o.o.c.o.a.dmaap.DmaapMessageConsumer : fetchFromDmaap, no action DMAAP not configured
...
where the source should specify the absolute path of the file, which should be recognizable for your environment.
Cannot establish connection with RIC/Simulator
If when running A1 Policy Management Service you see log warning like those below, this indicates that the configured 'ric's cannot be contacted.
Code Block | ||||
---|---|---|---|---|
| ||||
2021202x-10-29 07:33:06.134 WARN 1 --- [or-http-epoll-1] o.o.c.o.a.clients.A1ClientFactory : Could not get protocol version from Near-RT RIC: ric3 2021202x-10-29 07:33:06.139 WARN 1 --- [or-http-epoll-1] o.o.c.o.a.tasks.RefreshConfigTask : Failed to synchronize types in new RIC: ric3, reason: Protocol negotiation failed for ric3 2021202x-10-29 07:33:06.154 WARN 1 --- [or-http-epoll-1] o.o.c.o.a.clients.A1ClientFactory : Could not get protocol version from Near-RT RIC: ric4 2021202x-10-29 07:33:06.154 WARN 1 --- [or-http-epoll-1] o.o.c.o.a.tasks.RefreshConfigTask : Failed to synchronize types in new RIC: ric4, reason: Protocol negotiation failed for ric4 reactor.core.Exceptions$ErrorCallbackNotImplemented: org.onap.ccsdk.oran.a1policymanagementservice.exceptions.ServiceException: Protocol negotiation failed for ric1 Caused by: org.onap.ccsdk.oran.a1policymanagementservice.exceptions.ServiceException: Protocol negotiation failed for ric1 |
...
- Chaeck that the 'ric's are correctly configured ... See London Montreal - Component configuration again
...