This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
Remedy Single Sign On
Remedy Single Sign On
Remedy Single Sign On with Postgres DB
After checking an issue in the RSSO Server we changed the permissions in "TruesightRSSO" folder to "chmod 777 -R TruesightRSSO"
24 Apr 2019 11:36:39.574 INFO Thread_18 com.bmc.rsso.dao.util.GenericDaoCreator.createRelayStateDao(): Creating POSTGRES RelayStateDao
24 Apr 2019 11:36:39.575 INFO Thread_18 com.bmc.rsso.dao.BaseDatabaseDao.init(): Initializing DAO class com.bmc.rsso.dao.SqlRelayStateDao
24 Apr 2019 11:36:39.575 INFO Thread_18 com.bmc.rsso.dao.util.DatabaseInitializer.init(): Initializing datasource jdbc/rsso
24 Apr 2019 11:36:39.578 SEVERE Thread_18 com.bmc.rsso.dao.util.DatabaseInitializer.init(): Error initializing datasource jdbc/rsso
ERROR: Connection to localhost:5438 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
After checking the postmaster is not configure to accept requests from port 5432.
The permissions in rsso/data/pgsql (DB Folder) are wrong FATAL: data directory "/opt/bmc/TrueSightRSSO/rsso/data/pgsql" has group or world access DETAIL: Permissions should be u=rwx (0700).
Checking the "database.stdout.log" file we found:
LOG: database system is shut down
FATAL: data directory "/opt/bmc/TrueSightRSSO/rsso/data/pgsql" has group or world access
DETAIL: Permissions should be u=rwx (0700).
This means that Postgres is not capable to process the requests as the permissions should be "o=rwx (700)", then after changing the permissions to "/opt/bmc/TrueSightRSSO/rsso/data/pgsql" - chmod 777 -R pgsql , the RSSO service start running fine again:
INFO Thread_24 com.bmc.rsso.data.SpDataManager.checkOrUpdateConfig(): Configuration reloading is finished
In case of Windows environment, it is more likely that its not a permissions issue. This error was seen in RSSO install logs while upgrading embedded RSSO to 1902
"Connection to localhost:5438 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections."
No permissions were modified to resolve the issue, but had to run the installer three times. It appears that timestamp is important in this case. When installing / upgrading embedded RSSO, just before the stage of 'configuring database', installer stops the Tomcat service and then restarts. It was noticed that Tomcat was not started in time, hence the connection to Postgres db was also not available. Upon running the installer on multiple attempts, the installation was finally successful.