troubleshooting
Differences
This shows you the differences between two versions of the page.
Previous revisionLast revision | |||
— | troubleshooting [2016/09/14 11:43] – jtello | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | |||
+ | ==failed devices: MOODD == | ||
+ | **Possible reason:** One of the centrald is in a HARD OFF state. This can happen if the rts2 system is stopped and restarted. | ||
+ | **Solution: | ||
+ | |||
+ | ==Loss of tracking== | ||
+ | Many underlying reasons can cause a mount to stop tracking, in some cases it can be fixed by simply reenabling it. | ||
+ | **Diagnostic: | ||
+ | **Solution: | ||
+ | |||
+ | |||
+ | ==Cannot connect to databse== | ||
+ | An error of the type: | ||
+ | #### | ||
+ | May occur either because the postgresql service needs to be restarted (sudo service postgresql restart) or because the user requesting access to the database is not part of the database yet and must be added (createuser user) | ||
+ | | ||
troubleshooting.txt · Last modified: 2016/09/14 00:00 (external edit)