Logs and troubleshooting (Release ONE): Difference between revisions
From OSM Public Wiki
Garciadeblas (talk | contribs) |
|||
Line 17: | Line 17: | ||
===RO logs=== | ===RO logs=== | ||
The server-side RO logs can be obtained on the RO container at: | |||
<pre> /var/log/openmano/openmano.log </pre> | |||
logs output and level (''debug'' by default) are set at file | |||
<pre> /etc/default/openmanod.cfg </pre> | |||
===VCA logs=== | ===VCA logs=== |
Revision as of 16:46, 2 November 2016
Under elaboration
Logs
SO logs
UI logs
The server-side UI logs can be obtained on the SO-ub container at:
/usr/rift/usr/share/rw.ui/skyquake/err.log /usr/rift/usr/share/rw.ui/skyquake/out.log
Client side UI logs can be obtained in the Developer Console in a browser.
RO logs
The server-side RO logs can be obtained on the RO container at:
/var/log/openmano/openmano.log
logs output and level (debug by default) are set at file
/etc/default/openmanod.cfg
VCA logs
Troubleshooting
Checking status
SO status
UI status
- The status of the UI process can be checked by running the following command in the SO-ub container as root:
forever list
- You should see a status similar to following with an uptime:
info: Forever processes running data: uid command script forever pid id logfile uptime data: [0] uivz /usr/bin/nodejs skyquake.js --enable-https --keyfile-path=/usr/rift/etc/ssl/current.key --certfile-path=/usr/rift/etc/ssl/current.cert 21071 21082 /root/.forever/forever.log 0:18:12:3.231
- In case the UI server process has issues, you won't see an uptime but will instead see a status "STOPPED" in that position.
- In case the UI server process never started, you'll see a status saying "No forever processes running".
RO status
VCA status
Restarting services
Restarting SO
Restarting UI
- The UI is restarted when the SO module (launchpad) is restarted.
- However, in case just the UI needs to be restarted, you can run the following command in the SO-ub container as root:
forever restartall