Use the following steps to help debug email server authentication issues.
Enter "telnet"
Enter "set LOCAL_ECHO"
Enter "open mail.YourDomain.com 25" (replace YourDomain.com with your domain). Enter "HELO"
Enter "AUTH LOGIN"
You now need to enter your email and password encoded in BASE64. For help converting to Base64, click on our conversion tool. Enter your email, click Encode, copy that value in the telnet session and then press ENTER. Next, enter your password in the conversion tool, copy that value in the telnet session and press ENTER.
If you have successfully authenticated, the server will return: 235 authenticated.
Enter "MAIL FROM YourUserName@YourDomain.com" (replace YourUserName@YourDomain.com with your email address). Enter "RCPT TO DestinationEmail" (replace DestinationEmail with the destination email).
Enter "DATA"
Enter "Subject: Test using telnet"
Enter "" (send a blank line to separate the headers from the message body) Enter "This is a test to see if I can SMTP auth from my PC"
Enter "." The server should return: 250 Message queued Enter "quit"
The Test Service Instance feature is not designed to trigger action or alert profiles associated with the monitor.

The following warning message will appear in the Uptime Infrastructure Monitor web interface when it detects that the Data Collector service is not running:

up.time Data Collector is unavailable.
Please contact your administrator to have the Data Collector restarted.
When this occurs, try to restart the Data Collector service manually Starting (or restarting) and Stopping Uptime Infrastructure Monitor Wait until the service is started and then reload the browser window.
If the error message remains review the article, 'up.time Data Collector' is unavailable error in web interface If the issue still persists contact support@uptimesoftware.com.
Example thread pool backlog entries from an uptime.log file:
2010-05-18 03:15:07,473 WARN (Launcher:117) - Thread pool backlog: Events in queue: 110 Available: 0 Busy:75 2010-05-18 03:15:07,474 WARN (Launcher:117) - Thread pool backlog: Events in queue: 111 Available: 0 Busy:75 2010-05-18 03:15:07,474 WARN (Launcher:117) - Thread pool backlog: Events in queue: 112 Available: 0 Busy:75
These warning messages indicate that Uptime Infrastructure Monitor's task scheduler is taking on new tasks faster than current tasks can be executed. These messages are generally not an indication of a significant problem if they occur intermittently and in short bursts. However, if these messages are sustained for extended periods of time, please contact uptime Support for guidance on potential system tuning.
There are various reasons why you may be seeing these messages:
The serviceThreads variable in the uptime.conf file is set to a higher value than the connectionPoolMaximum parameter. Note that the connectionPoolMaximum value should be at least 10% higher than the serviceThreads value.
Your hardware platform is saturated and can't execute tasks quickly enough.
The average time required to complete a task is simply too long. If you have many monitors that consistently fail or reach their timeout setting, this can substantially impact the Uptime Infrastructure Monitor task list. uptime Support can provide further information and guidance on how to improve task execution performance and optimize the size of your task list.
Add troubleshooting article