Commit c97b89d3 authored by Francisco-Javier Ramon Salguero's avatar Francisco-Javier Ramon Salguero
Browse files

Merge branch 'troubleshooting' into 'master' 

Updated 09-troubleshooting: how to know osm version, how to change log level

See merge request !17
parents b4e9a0e7 37d2bd93

09-troubleshooting.md

+35 −5
Original line number Diff line number Diff line
@@ -2,22 +2,29 @@ 


## How to know the version of your current OSM installation



In order to know the version that you have installed you only need to search the `osm-devops` package installed in your system, since `osm-devops` is the package used to drive installations:

Run the following command to know the version of OSM client and OSM NBI:



```bash

osm version

```



In some circumstances, it could be useful to search the `osm-devops` package installed in your system, since `osm-devops` is the package used to drive installations:



```bash

dpkg -l osm-devops



||/ Name                     Version            Architecture          Description

+++-======================-=================-=====================-=====================================

ii  osm-devops             4.0.1-1            all

ii  osm-devops             7.0.0-1            all

```



In case you only installed separate stacks (e.g. `elk_stack`, `pm_stack`, etc.), you could end with a newer version of the `osm-devops` package. Then you can search the `python-osmclient` package as a way to know your current version of OSM:

To know the current verion of the OSM client, you can also search the `python3-osmclient` package as a way to know your current version of OSM:



```text

```bash

dpkg -l python3-osmclient

||/ Name                     Version            Architecture          Description

+++-======================-=================-=====================-=====================================

ii  python-osmclient       4.0.1-1            all

ii  python3-osmclient       7.0.0-1            all

```



## Recommended installation to facilitate troubleshooting
@@ -518,6 +525,29 @@ And the DOCKER_ID can be obtained this way, e.g. for MON 
docker ps -aqf "name=osm_mon" -n 1 --no-trunc

```



### Changing the log level



You can change the log level of any container, by updating the container with the right `LOG_LEVEL` env var.



Log levels are:



- ERROR

- WARNING

- INFO

- DEBUG



For instance, to increase the log level to DEBUG for the NBI in a deployment of OSM over docker swarm:



```bash

docker service update --env-add OSMNBI_LOG_LEVEL=DEBUG osm_nbi

```



For instance, to set the log level to INFO for the MON in a deployment of OSM over K8s:



```bash

kubectl -n osm set env deployment mon OSMMON_GLOBAL_LOGLEVEL=INFO

```



## How to report an issue



**If you have bugs or issues to be reported, please use [Bugzilla](https://osm.etsi.org/bugzilla)**