What is COMMAND
ROGNOSIS used for and what is the default password? I can't find doc on this like I can find with IDs PQLrognosis and PQLostgres. I was unable to log onto the webui in our lab getting error "Database Error Connection not established" and after some service restarts and other attemps I noticed my password config was missing the commandrognosis entry. I restored a backup instance of this config which had the commandrognosis entry and now I can get into the WebUI so I'm guessing this is needed for web access.
Accepted Solutions
Hello Matthew,
The Commandrognosis password entry in the PASSWORDS configuration is used for background processes like the rollup jobs and database summaries. The password value should be blank, anything else causes issues.
Note: the Commandrognosis password entry in the PASSWORDS configuration of the Windows Client will show "******" even if the password entry is blank. An IRFAX will show no hash for this entry if the entry is correct.
The most likely cause of the Web UI login failure (corrected by using an old PASSWORDS configuration) is that the PostgreSQL password entry was also missing from the PASSWORDS configuration. This issue has been seen in some environments after an upgrade.
The underlying cause of the Web UI login failure issue is that Prognosis stores some Role Based Security items in the PostgreSQL database and Prognosis must access PostgreSQL to determine the Security Role for the user. If Prognosis can't access the PostgreSQL database, then the "Database Error Connection not established" message is shown and no Web UI logins will work.
Restoring an old copy of the PASSWORDS configuration or manually adding all the required default password entries is the recommended fix.
Thank you,
Scott Baldwin
Hello Matthew,
The Commandrognosis password entry in the PASSWORDS configuration is used for background processes like the rollup jobs and database summaries. The password value should be blank, anything else causes issues.
Note: the Commandrognosis password entry in the PASSWORDS configuration of the Windows Client will show "******" even if the password entry is blank. An IRFAX will show no hash for this entry if the entry is correct.
The most likely cause of the Web UI login failure (corrected by using an old PASSWORDS configuration) is that the PostgreSQL password entry was also missing from the PASSWORDS configuration. This issue has been seen in some environments after an upgrade.
The underlying cause of the Web UI login failure issue is that Prognosis stores some Role Based Security items in the PostgreSQL database and Prognosis must access PostgreSQL to determine the Security Role for the user. If Prognosis can't access the PostgreSQL database, then the "Database Error Connection not established" message is shown and no Web UI logins will work.
Restoring an old copy of the PASSWORDS configuration or manually adding all the required default password entries is the recommended fix.
Thank you,
Scott Baldwin
