Error Messages

If you have recently changed the hostname of your monitoring station and receive the message "Database Not Responding" in the monitoring station web interface, you must make the following...

By: CSS | Date Created: 10-1-2009 | Last Modified: 10-18-2013 | Index: 379

This problem occurs if the format of the license.dat file is not correct. Specifically when the line feed after any '\' character is not in place. In the example license key below the 3rd line is...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-10-2011 | Index: 254

This error is commonly caused by permission problems on the icmp executable that up.time uses to verify the PING status for a monitored element. To resolve this issue review the information below...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 279

The exception below appears when starting the up.time data collector service in the following scenarios 1 - The up.time data collector is already running 2 - Another service is using the up.time...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 286

This error is generally seen when using perl-based plug-in monitors and may refer to any path listed in the perl script. This issue can usually be resolved by ensuring that perl exists where it...

By: CSS | Date Created: 7-14-2011 | Last Modified: 8-11-2011 | Index: 551

Example error message: 2010-07-09 16:42:41,654 ERROR (PerfERDC:137) - service Platform Performance Gatherer (192) on host DKLBMMDB1 (34) Error getting data from agent: Java heap space Throwable:...

By: CSS | Date Created: 8-26-2010 | Last Modified: 8-10-2011 | Index: 495

If you did not log out of the up.time UI before upgrading to up.time 6.0.1 (refer to step 6 of Upgrading and Applying up.time Service Packs), you may see the following error after attempting to...

By: CSS | Date Created: 12-21-2011 | Last Modified: 8-14-2013 | Index: 572

This error message indicates a general network connectivity error from the monitoring station to the monitored agent servers. It has only been seen on windows monitoring stations and is generally...

By: CSS | Date Created: 12-31-1969 | Last Modified: 6-27-2013 | Index: 280

Monitor: MySQL (Advanced Metrics) Status Message: ------------------------------------------------ Status: CRIT Message: Insufficient status data returned Response time: 437...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 287

This error is normally a result of the CPU time interval within the performance monitor being shorter than the data collection rate of the associated agents performance data collector. More...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 289

On Windows systems the "explorer" process will not exist if there are no users logged on to the system. If this is the case, we recommend using the "winlogon" process as it is always running on the...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-10-2011 | Index: 290

At times you may notice an error in the uptime.log or alert profile test function indicating that up.time was unable to send mail to a specific email address. An example of the error message is...

By: CSS | Date Created: 10-10-2009 | Last Modified: 8-13-2011 | Index: 421

Typically this error indicates that the SMTP server you have configured up.time to relay messages through requires authentication or that the user you are authenticating as doesn't have permissions...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-10-2011 | Index: 291

This error message indicates that up.time isn't able to find the SQL Server performance counters on the target server. There are a few common items to check in this case: - Is the hostname /...

By: CSS | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 288