When running the instructions from our Run wiki page, still errors can happened. 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 each service you can use the following command:
| Code Block | ||||
|---|---|---|---|---|
| ||||
docker exec <container_name> cat <log_path> |
Below there is a list with the container names follow by the log path, to replace the values in the command above. The container names correspond to the names used in the example Run page, to double check that the you are using the same names in your environment, you could use docker ps.
sdnc_container="/opt/opendaylight/data/log/karaf.log"
policy-agent-container="/var/log/policy-agent/application.log"
nonrtric-control-panel="/logs/nonrtric-controlpanel.log"
nonrtric-gateway="/var/log/nonrtric-gateway/application.log"
The below command can be used to check if there is any error in the logs, in this case for me policy-agent-container, but it could be check for every other container.
| Code Block | ||||
|---|---|---|---|---|
| ||||
docker exec policy-agent-container grep ERR /var/log/policy-agent/application.log |
Warning can be also checked, using WARN instead or ERR in the command above.
Did SDNC started correctly?
...
| 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 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:
| Code Block | ||||
|---|---|---|---|---|
| ||||
docker exec -t sdnc_controller cat /opt/opendaylight/data/log/karaf.log > karaf_log.log |
Log will be store in current directory with the name karaf_log.log. Once we get the logs, we can verify if there is any error.
If there is any error in SDNC you can contact CCSDK/SDNC team for help.
Did PSM started correctly?
...
2021-10-29 07:23:04.878 DEBUG 1 --- [ parallel-2] o.o.c.o.a.dmaap.DmaapMessageConsumer : InfiniteFlux.onRequest 1
2021-10-29 07:23:04.879 DEBUG 1 --- [ parallel-2] o.o.c.o.a.dmaap.DmaapMessageConsumer : fetchFromDmaap, no action DMAAP not configured
To be sure that the configuration file was mount properly execute the follow command:
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ docker inspect -f '{{ json .Mounts }}' policy-agent-container | jq |
The output below shows when the file was not properly mounted:
[
{
"Type": "volume",
"Name": "f85d0d2c9c11dc9cd9cb20e6658711442fbd326ac8805ba2e5aa77d1c80af785",
"Source": "/var/lib/docker/volumes/f85d0d2c9c11dc9cd9cb20e6658711442fbd326ac8805ba2e5aa77d1c80af785/_data",
"Destination": ":/opt/app/policy-agent/data/application_configuration.json",
"Driver": "local",
"Mode": "",
"RW": true,
"Propagation": ""
}
]
When the file is mount correctly the output must look like this:
| Code Block | ||||
|---|---|---|---|---|
| ||||
$ docker inspect -f '{{ json .Mounts }}' policy-agent-container | jq |
[
{
"Type": "bind",
"Source": "/home/ychacon/repo/onap/ccsdk/oran/a1-policy-management/config/application_configuration.json",
"Destination": "/opt/app/policy-agent/data/application_configuration.json",
"Mode": "",
"RW": true,
"Propagation": "rprivate"
}
]
where the source should specify the absolute path of the file.
Cannot establish connection with RIC
If when running PMS, output below is shown, there are some things that you can try:
| Code Block | ||||
|---|---|---|---|---|
| ||||
2021-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 2021-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 2021-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 2021-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 |
...