summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/slice-analysis-ms/slice_analysis_ms_troubleshooting.rst
diff options
context:
space:
mode:
authorReshmasree <reshmasree.chamarthi2@wipro.com>2020-11-10 18:00:05 +0530
committerAhila <ahila.pandaram@wipro.com>2020-11-11 19:15:01 +0530
commit2cf33d0d1cecad5a309d428aa44f7740ca48032e (patch)
tree05c515ff22dfc0b3db84dd02b6ebaeecc5786290 /docs/sections/services/slice-analysis-ms/slice_analysis_ms_troubleshooting.rst
parent7634901b6d877a6126978ee11ce489ebfc4e3669 (diff)
Add slice-analysis-ms documents
Application configurations and troubleshooting steps added Removed references to PNDA Issue-ID: DCAEGEN2-2515 Signed-off-by: Reshmasree <reshmasree.chamarthi2@wipro.com> Signed-off-by: Ahila P <ahila.pandaram@wipro.com> Change-Id: I941420b459b60e0e8f4c63463b16d7f6602cbfeb
Diffstat (limited to 'docs/sections/services/slice-analysis-ms/slice_analysis_ms_troubleshooting.rst')
-rw-r--r--docs/sections/services/slice-analysis-ms/slice_analysis_ms_troubleshooting.rst46
1 files changed, 46 insertions, 0 deletions
diff --git a/docs/sections/services/slice-analysis-ms/slice_analysis_ms_troubleshooting.rst b/docs/sections/services/slice-analysis-ms/slice_analysis_ms_troubleshooting.rst
new file mode 100644
index 00000000..66dee8c2
--- /dev/null
+++ b/docs/sections/services/slice-analysis-ms/slice_analysis_ms_troubleshooting.rst
@@ -0,0 +1,46 @@
+Trouble shooting steps
+----------------------
+1. **Microservice stops and restarts during startup**
+
+ Possible reason & Solution: Microservice is not registered with the consul
+ - Check the consul if the microservice is registered with it and the MS is able to fetch the app config from the CBS. Check if CBS and consul are deployed properly and try to redeploy the MS
+ The below logs will be seen if CBS is not reachable by the MS
+
+ 15:14:13.861 [main] WARN org.postgresql.Driver - JDBC URL port: 0 not valid (1:65535)
+ 15:14:13.862 [main] WARN o.s.b.w.s.c.AnnotationConfigServletWebServerApplicationContext -
+ Exception encountered during context initialization - cancelling refresh attempt:
+ org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name
+ 'org.springframework.boot.autoconfigure.orm.jpa.HibernateJpaConfiguration': Unsatisfied
+ dependency expressed through constructor parameter 0; nested exception is
+ org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource'
+ defined in org.onap.dcaegen2.services. sliceanalysisms.Application: Initialization of bean failed;
+ nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name
+ 'org.springframework.boot.autoconfigure.jdbc.DataSourceInitializerInvoker': Invocation of init method failed; nested exception is
+ org.springframework.jdbc.datasource.init.UncategorizedScriptException: Failed to execute database script; nested exception is
+ java.lang.RuntimeException: Driver org.postgresql.Driver claims to not accept jdbcUrl, jdbc:postgresql://null:0/sliceanalysisms
+ 15:14:13.865 [main] INFO o.a.catalina.core.StandardService - Stopping service [Tomcat]
+ 15:14:13.877 [main] INFO o.s.b.a.l.ConditionEvaluationReportLoggingListener - Error starting ApplicationContext.
+ To display the conditions report re-run your application with 'debug' enabled.
+ 15:14:13.880 [main] ERROR o.s.boot.SpringApplication - Application run failed
+
+2. **No PostgreSQL clusters have been deployed on this manager**
+
+ Solution:
+
+ kubectl exec -ti -n onap dev-dcaemod-db-primary-56ff585cf7-dxkkx bash
+ psql
+ ALTER ROLE "postgres" WITH PASSWORD 'onapdemodb';
+ \q
+
+ kubectl exec -ti -n onap dev-dcae-bootstrap-b47854569-dnrqf bash
+ cfy blueprints upload -b pgaas_initdb /blueprints/k8s-pgaas-initdb.yaml
+ cfy deployments create -b pgaas_initdb -i k8s-pgaas-initdb-inputs.yaml pgaas_initdb
+ cfy executions start -d pgaas_initdb install
+
+
+Logging
+-------
+Since the Slice Analysis MS is deployed as a pod in the kubernetes, we can check the logs by
+using the following command:
+
+ $ kubectl logs <pod-name> –namespace onap \ No newline at end of file