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 | 20212023-1001-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.
...
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.
...
- Chaeck that the 'ric's are correctly configured ... See Kohn London - Component configuration again
Then restart the A1 Policy Management Service and try again.