Note: Please see the Troubleshooting Guide for TSSA Application Server Startup issues for more details on troubleshooting these issues. The error message prior to BSA 8.2 is:
|
These errors suggest there is a problem communicating with the TSSA/BSA RSCD agent on the designated File Server. The Application Server validates connectivity with the BladeLogic File Server during startup and will not proceed if this step fails. When this error message is encountered during the Application Server startup, run through the following steps: 1) Verify the designated File Server is as expected by running the following blasadmin commands:
blasadmin show fileserver all
This will return the File Server hostname and directory e.g.
# blasadmin -a show file all blasadmin now running against the following deployments: default, _template [FileServer] location:/opt/bmc/bladelogic/storage/ name:blapp.example.com If this output looks correct, proceed to step 2. If this output looks incorrect (i.e. incorrect hostname or directory) update the settings as follows:
blasadmin -a set fileserver name newfshost blasadmin -a set fileserver location /new/storage/path Restart the application server to pickup the change in the file server location. 2) Once you have verified that the File Server hostname and directory are correct, the next step is to confirm that the File Server RSCD Agent can be reached from the Application server.
The product documentation provides a guide to troubleshoot RSCD agent connectivity issues. Also take not of the special acl requirements noted elsewhere in the product documentation. It can also be helpful to inspect the rscd.log while the appserver service is starting for any errors such as:
04/09/19 17:07:18.478 WARN rscd - ::ffff:123.456.78.90 16766 -1/-1 (Not_available): (Not_available): Host not granted accessWhich indicates my appserver host (123.456.78.90) is not granted access in the exports file. Or: 04/09/19 17:06:59.784 WARN rscd - ::ffff:123.456.78.90 16748 99/99 (System:System): agentinfo: Failed to map user to local userWhich indicates the System:System role:user is not mapped correctly in the users.local file. NOTE: - Make sure there is NO 'nouser' entry in 'users' file in the file server 'rsc' folder. If any, remove the entry. - Make sure there is a mapping entry for 'System:System' in 'users.local' file in the file server 'rsc' folder. If doesn't exist, add a mapping entry to a local admin user. - Make sure the 'BladelogicRSCD' Account is Not Disabled. 3) If the Application Server startup problem persists after running through the above steps, please submit a ticket with BMC Support with the following data: - appserver.log from the appserver that failed to start due to file server validation (log is located under "<appserver install dir>/NSH/br" folder) - rscd.log from file server (located under "<RSCD agent install dir>/RSCD/" or "<RSCD agent install dir>/RSCD/log" folder) - zip all files under 'rsc' folder from file server (located under '/etc/rsc' in case of linux, 'C:\Windows\rsc' in case of Windows) |