Troubleshooting
How to diagnose
Check the service
Make sure the stcpgemini-api service is running (systemctl status stcpgemini-api) and that the host and port used are the ones in the API config.json.
Note the HTTP status
The status indicates the class of the problem. See Response codes.
Look for the symptom
See the common problems.
Common problems
The connection to the API fails or shows a certificate error
Symptom: the client does not connect or rejects the certificate.
Probable cause: wrong port, TLS disabled (ssl: false or -ns) or a certificate the client does not trust.
Solution: check host, port, ssl, cert and key in the general section of the API config.json and use the matching scheme (http or https).
The token endpoint returns 400 or 401
Symptom: POST /oauth/token does not return the access_token.
Probable cause: body not in the application/x-www-form-urlencoded format, grant_type other than password, or invalid operator credentials.
Solution: send grant_type=password, username and password as a form and check the operator in the Portal.
Calls return 401 after some time
Symptom: calls that worked start returning 401.
Probable cause: the token has expired or was invalidated by a sign-out.
Solution: obtain a new token and repeat the call.
The report returns null data
Symptom: the response is {"data": null, "next": ""}.
Probable cause: there are no records in the period or the filters do not match the data. It is common to send start and end in seconds instead of milliseconds.
Solution: send the dates in milliseconds and check instance, user and the other filters.
The operator cannot access a resource
Symptom: the token is issued, but the call is refused.
Probable cause: the operator has no permission on the resource group (see the token scope field).
Solution: adjust the operator’s permissions in the Riversoft® Console Portal.