"Big Monitoring Without the Complexity and Cost"  
Home Products Pricing Support Downloads News and Events Contact Us  
 
 
Support
Release Information
FAQ
Quick Setup
Support Request
 
 






Red Hat and the Shadow Man logo are registered trademarks of Red Hat, Inc. in the United States and other Countries, used with permission.
 
 
FAQ/Troubleshooting
The following list of frequently asked questions has been assembled in order to help with troubleshooting your installation. If this does not solve an issue that you are having, please contact Technical Support.
 
SiteMaestro Agent TM

The agent fails to start - "Bind Failure" in sm.trc
The HTTP port is already in use by another service. Choose another port and restart the agent.

The agent fails to start - "Trial License Expired" in sm.trc
The trial license has expired. If you have alread purchased a license, then copy your license file (sm.lic) from another server. If you need to purchase a license or extend your trial period, contact our Sales Department.

Why do the Ping, Network, and TCP Scanners not run?
On most versions of Unix, device /dev/ip is restricted to super-user access only. To correct the problem, make sure that the agent is running with super-user privileges.

The S80smd init.d scripts will not install
The user does not have permissions to write to the startup script directories (Solaris: /etc/init.d, Linux: /etc/rc.d). Restart the installation as a user with super-user privileges.

The agent does see my configuration settings
The configuration file must be named sm.conf and be located in the main installation directory of the agent. In addition, changes are only picked up during startup and at each polling interval. See the "Poll" property of the [Configuration] section of the configuration file.

Why are some sections of the configuration skipped?
When syntax errors are detected in a configuration section, the entire section is skipped. Check the trace log for errors in the configuration and correct them.

The agent core dumps under Solaris 2.5.1
Sun introduced a nasty bug in the thread library under patch level 33. We recommend that you install patch level 34 or higher.

The Filesystem scanner does not run under Windows 2000
Agent versions prior to 1.5.2 rely on the logical disk performance counters to be active. To correct this upgrade to v1.5.2 or activate them using the "diskperf" command.

Disk statistics are all zeros under Windows 2000/2003/XP
The disk statistics are obtained from the physical disk performance counters. To start getting data, activate them using the "diskperf" command.

I cannot access the Configuration web pages
If you have the User Authentication option enabled, then a user must be in the "admin" access group in order to access the Configration web pages. To make someone a member of this group, add "admin" to their access group list in the "sm.passwd" file. For more information see "Configuring User Authentication" in the Reference Manual.

How do I add a new plugin?
In order to activate plugins, the plugin file needs to be copied to the "plugins" sub-directory of the installation directory. Then, the agent configuration needs to be updated to load it:

  1. Add the plugin filename in CONFIGURATION->GENERAL
  2. Apply and Save
  3. Restart the agent
  4. Added a new scanner instance in CONFIGURATION->SCANNERS by clicking on "Add New" under the "Plugin Scanners" section. Select your plugin name and configure
  5. Apply and Save

I changed the IP address or Port number of the Agent, it did not seem to work
The IP address and port number of the agent or console requires a service restart to take effect.

 
SiteMaestro Console TM

The Console does not seem to start - I cannot contact it after installation
The console may not be enabled or set to start on the specified machine. On Windows, the console service is set for MANUAL startup by default. On Unix, the console is only started by the init.d scripts when "enabled=true" is set in the [Console] section of the configuration. In addition, check the port number and license situation by looking in the console trace log "smc.trc".

 
Home  | Contact Us  | Privacy  | Copyright © 2002-2008 T3 Software Builders, Inc. |  All Rights Reserved