Troubleshooting¶
How to access the instance database¶
The data is stored at SA-K8S-MSSQL.office.sbs\\MSSQL2017 database. Look for the database for your instance, which will look like saas-instanceName. The database contains the Multitenancy tables, Security Database tables and Logging tables.
How to read the logs¶
The logs are stored alongside the Security tables, in the same database. They can be found at dbo.Logs table. See How to access the instance database.
How to read the logs which are outside Logging¶
In general, logs are stored in the Logging table dbo.Logs which can be found in the same database as the instance Security. But there are logs that are important and they are not stored in that table (Authentication has some important errors logged outside Logging).
These logs can be retrieved using the GET /api/instance/{instanceName} endpoint with the parameter includeLogs set to true. With the response, it have included the more recent logs for each container running for the instance. The object podLogs in the response is a dictionary/map where the key is the name of the pod (which will look like instanceName-api-dn1283jd-fd828a42) and the value the logs. Logs are sorted by time ascending, so the last line is the more recent log.
Authentication errors
There are some errors related to Authentication like invalid_client or invalid_redirect_uri which the reason of failure can be found in these logs. It is recommended to grab those logs quickly and inspect them properly, because they usually appear between other kind of logs.
How to see the health checks¶
The easiest way is to go to the API, send a request to GET /api/instance/{instanceName} with the parameters includeHealthChecks set to true and it will return them in the response. You may also issue the health check request directly to the Security services manually.
Something in Security is not working properly¶
First check the logs to see if there is something wrong. Also check out the health checks to see if there is something not working properly.
Currently, the only thing that may not work and can be fixed by users is the RabbitMQ connection.
For other kind of errors that you cannot fix, please contact Supporting Apps.
FQDN domains
It is recommended to use FQDN in the RabbitMQ URL to avoid any kind type of connection error.
I'm getting invalid_client or invalid_redirect_uri¶
Check out the Authentication logs using the method described in How to read the logs which are outside Logging. The cause of the error is usually on this logs.
A deployment is failing¶
If you are using a custom configuration, check that is valid.
For any other cases, please contact Supporting Apps.