Istanbul - Debug
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.
Log collection
In order to collect logs from each service you can use the following command:
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.
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?
If using A1 controller, SDNC should be used. Specifically, mariadb and sdnc_image must started correctly.
Check MariaDB container
If you can see the following message in the logs for DB container:
sdnc_db_container | 2021-10-28 14:39:34+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
sdnc_db_container | 2021-10-28 14:39:34+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.12+maria~focal started.
sdnc_db_container | 2021-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
You probably are missing vaues for MARIADB_ROOT_PASSWORD, MARIADB_ALLOW_EMPTY_ROOT_PASSWORD and MARIADB_RANDOM_ROOT_PASSWORD. These values must be provided in order for docker compose to work correctly. You can use following values:
To be sure that the container is up and running correctly, following message must be seen in the console:
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:
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:
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?
Volume not mounted properly
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:
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:
[
{
"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:
Check that all container are running in same network?
You can use following command to check:
Check that sdnc_controller is on network nonrtric-docker-net if not use:
- Then restart PMS and try again.