These errors could affect any Qorus client program that communicates with the Qorus process using the HTTP interface.

Error: Connection Error

Error Message:

ERROR: Qorus server at "http://localhost:8501" is down

Explanation:: The client program could not connect the Qorus HTTP server.

Possible Cause	Action to Take
The system is not running	Check the system status with the `ps` command, if it’s already been shut down, then no further action need be taken
The client URL (hostname and/or port) is incorrect	Verify that the URL is correct and edit the System Options File file as needed.
The system is running but has not yet fully shut down.	If the system has already stopped the HTTP server, but has not yet exited, then this error could appear. Usually the system process will terminate within a few seconds after shutting down the HTTP server. If it does not, it could be because a running service refuses to stop. If the process does not terminate in a reasonable time after the HTTP server has stopped (the amount of time may vary if there are any user services loaded that take an unusually long time to stop), then the only option left is to kill the Qorus process. If the session was not closed, then the next time the Qorus process is launched; the auto-recover option must be set to true.

Error: Authentication Error

When Qorus Role-Based Access Control (RBAC) security is enabled, all network clients must provide a username and password to communicate with the server. All unauthenticated connections will be rejected by the server.

Error Message:

HTTP-CLIENT-RECEIVE-ERROR: HTTP status code 401 received: message: Unauthorized

Explanation:: The Qorus HTTP server rejected the connection because authentication information was missing or invalid and no host or IP overrides exist for the client.

Possible Cause	Action to Take
Authentication information is missing in the HTTP request	Include a username and password in the request URL (i.e. `http://user:pass@host:port`) or, to allow unauthenticated connections from a certain host or IP address range, configure the qorus.rbac-force-user option in the System Options File file and restart the Qorus server to assume a default user for all unauthenticated connections from that host or IP address range.
Password is incorrect	Correct the password in the URL and try again.

Error: Authorization Error

When Qorus Role-Based Access Control (RBAC) security is enabled, only authenticated users can connect, and each user has a set of roles that allow the user to perform certain actions or classes of actions in the server. If the user does not have the required role, an error message is returned.

Error Message:

AUTHORIZATION-ERROR: user “user1" does not have role “WORKFLOW-CONTROL"

Explanation:: Qorus denied the request to perform the action because the authenticated user does not have sufficient privileges to perform the action. One or more roles are needed that the user does not have.

Possible Cause	Action to Take
User does not have the required role	Use another username that has the role or add the role to your user and try again.

Error: Database Connection Error

Error Message: (error message may differ according to the database used):

ERROR: DBI:PGSQL:ERROR: could not connect to server: Connection refused

Explanation:: The database could not be reached or (depending on the error message) the login parameters were invalid.

Possible Cause	Action to Take
The database connection parameters are incorrect	Check the entry in the system datasource (dbparams) File file for the `omq` datasource and try again. Verify connectivity with `sqlplus` (Oracle), `psql` (PostgreSQL), or `mysql` (MySQL)
The database is down	Restart the database and try again

Error: Environment Error

Error Message:

unhandled QORE System exception thrown in TID 1 at ../ocmd:11
PARSE-EXCEPTION: cannot open include file "qorus-client.ql"

Explanation:: The program could not find the include file "qorus-client.ql" and therefore cannot execute.

Possible Cause	Action to Take
The `$QORE_INCLUDE_DIR` environment variable is not configured properly	Check the `$QORE_INCLUDE_DIR` environment variable, it must be set to `$OMQ_DIR/qlib`
The Qorus installation is corrupt; `$OMQ_DIR/qlib` is missing or empty	Check your `$OMQ_DIR` environment variable and the filesystem, reinstall from the original installation package if necessary to restore system files.