Frequently asked questions for agent troubleshooting

Resolution: Installation of an RSCD agent requires approximately 200 MB of space on Windows platforms and 450 MB of space on Linux and UNIX platforms. When running, an RSCD agent on any platform requires approximately 60 MB of available disk space on 32-bit platforms and 140 MB on 64-bit platforms.
See Minimum-hardware-requirements.

Resolution: Please refer to Knowledge Article ID: 000090421, or to the following pages in the documentation:

• User-accounts
• Considerations-for-automation-principals-and-Windows-user-mapping

When pushing ACLs you might observe that extra roles are added to the users file.  This is because the ACL Push and ACL Preview resolve the permissions for the server object as well as any Component objects linked to the server. Roles that have permission on the associated Component will be resolved in the users file and pushed to the Server. For more information, see Creating-or-modifying-ACL-Push-Jobs.

Resolution: Certain RSCD Agent directories (typically within /opt/bmc/bladelogic/RSCD) have world-writable (777) permissions, with a sticky bit. The following table provides information about why these directories (which all reside within the RSCD Agent installation directory) require world-writable permissions. In general, the directories are world-writable so that when roles are mapped to different local user accounts, these accounts are able to write various data into the following directories:

The application of the umask setting through the RSCD Agent varies, depending on a number of factors:

• In the case of a login process (nexec –i –l . . .), profiles that create the login environment are executed, and these profiles set the umask
• In the case of a non-login process (for example, cp //<rscd-host>/ . . . ), umask is inherited when the agent is started. If the agent is started from the login shell by the root user (/etc/init.d/rscd start or agentctl start/restart from the root user's bash shell command prompt), it inherits the umask that was set by the login shell (or any subshells), if any. Umask can also be set explicitly in /etc/init.d/rscd. This also includes scriptutil executions and "Type 3" NSH Jobs.
• If the RSCD Agent is started during the system start or reboot, /etc/init.d/functions sets the umask.

Resolution: The files below are used by Magnicomp's sysinfo executable, which is used by the Hardware Information CO to gather information about the system. This information is typically included in the Inventory Snapshot Jobs that populate the out-of-the-box inventory reports in BDSSA. If BSA roles that gather this information are mapped to root or if the information is not needed, then the suid bit is not required. If the BSA roles that gather the information are mapped to a non-root account, then the suid bit is required for the executables to run correctly.

• <RSCD installDir>/nativetool/bin/.mcsiwrapper
• <RSCD installDir>/nativetool/bin/mcsysinfo (symlink to .mcsiwrapper)
• <RSCD installDir>/nativetool/bin/sdi (symlink to .mcsiwrapper)
  
• <RSCD installDir>/nativetool/bin/sysinfo (symlink to .mcsiwrapper)
  

The following additional files in the RSCD Agent install directory are also granted the setuid permissions. Similar to the group of files listed above, if the BSA roles that execute these functions are mapped to root, then the suid bit is not required.

• <RSCD installDir>/bin/vsh — a virtual shell that provides keystroke logging
• <RSCD installDir>/bin/lsof — used to set up x-windows forwarding through the NSH>RSCD connection

Resolution: Ensure <user> belongs to the local administrators group (Windows) or you are mapped to root (Unix)

The RSCD Agent listens on port 4750/tcp

A complex password of up to 16 characters, consisting of alphanumeric and special characters. 

Yes. Customers can use chapw -p to create a password of up to 80 characters, after the initial password creation.

On a domain controller, you can also use the agentctl utility to change the password of the BladeLogicRSCDDC user account, as discussed in Changing-the-BladeLogicRSCDDC-account-password-on-domain-controllers.

Yes, chapw -r creates a 16-character-long random password that contains alphanumeric characters.

Resolution: The details are as follows:

• BL version 8.9.02 or later: Microsoft Visual C++ 2015 Redistributable - 14.0.24215
• BL version 8.9.01 or earlier: Microsoft Visual C++ 2005 Redistributable - 8.0.50727.762

Resolution:

• BL version 8.9.02 or later: Microsoft Visual C++ 2015 Redistributable - 14.0.24215
  Yes, the RSCD Agent will work with the latest Microsoft Visual C++ runtime libraries.
• BL version 8.9.01 or earlier: Microsoft Visual C++ 2005 Redistributable - 8.0.50727.762
  No. The RSCD Agent will not work if these runtime library versions are missing.

Resolution: Multiple RSCD Agent installation is supported on UNIX host with an exception of HPUX (using -local option with installer).
On UNIX hosts, you will have to use additional -local option with installer.
For more information, see How to configure two RSCD agents on a single host (user contribution). 

Resolution:The following applications may have an impact on the smooth running of RSCD Agent:

• Applications configured to use the same port as the TrueSight Server Automation RSCD agent listening port (4750): The listening port of the agent can be customized if necessary.
• Anti-virus software which prevents the agent from accessing its own files, or communicating with the application server.

Resolution: By using the rootdir option in the configuration file (exports, users or users.local) we can restrict the access to the directory tree on the RSCD Agent. If the RSCD agent can't change the root directory to the configured value, we would see this warning.
For more information, see Setting-up-configuration-files .

Example:

On HOST2, the /opt/test directory doesn't exist and if the users file contains:

 rootrw,rootdir=/opt/test

Now when we try to access HOST2 from HOST1 like:

 [root@HOST1]$ agentinfo HOST2
Can't access host "HOST2": No authorization to access host
[root@HOST1]$ 

 Whereas in the rscd.log on HOST2 we will see:

 05/15/12 04:24:45.782 WARN rscd - HOST1 25287 0/0 (root): agentinfo: Failed to change the root directory

Resolution: limits.conf only applies to a shell session. These configuration settings do not apply at boot time, because no shell is started at that time.
Thus, if you start the agent at boot time, you will have to define the limits in the agent startup script.
This is standard UNIX practice, nothing to do with TrueSight Server Automation.

For more information, see Ubuntu forums entry

Resolution: You can restart the remote RSCD Agent using following command from NSH:
nexec <HOSTNAME> agentctl -b restart

 Resolution: Please refer to Creating rules to determine the repeater used for target servers

Resolution: Starting with version 8.2.00, we can deploy RSCD agent on Windows vio GPO.

Use the following installers:

•  RSCD82-WIN32.msi
•  RSCD82-WIN64.msi

Resolution: One of the causes for this situation may be that the additional hostname of the RSCD host is not getting resolved to its IP.
Adding the hostname and IP address in the hosts database (for example /etc/hosts) may resolve this issue. 

Resolution: There is no method by which exports file can be edited on the go during the silent install.
Once the installation is complete, it can be edited to have desired entries/user mappings in it. 

Resolution:

1. Verify the system event logs (on Windows)
2. Set the agent log level to debug by one of the following methods:
   • Manually, by editing log4crc.txt, and then restarting the agent.
   • From version 8.2 SP1 and later: Use agentctl toggle, to switch between the debug level and the current level.

Resolution: Use --local flag while installing/upgrading RSCD agent on Solaris 10 sparse root zone.

For example, RSCD82-SOL10-SPARC.sh --local

Resolution: First, upgrade NSH on the server, and then the RSCD Agent. Another way is upgrade both the console and NSH, and then to upgrade the RSCD Agent.

Resolution: The platform default locations are as follows:

• Platform: Solaris/Linux/AIX/HPUX Location: /etc/rsc
• Platform: Windows Location: %WINDIR%\rsc

This information is covered in Administering.

Resolution: nativetool_installer should not be removed. If removed, the package manager will report the files as missing when package is verified. If anyone doesn't care about the package verification they can feel free to delete the folder.