Search the knowledge base:
/var/adm/messages kernel: cdrom: open failed | Rating | Views | |
---|---|---|---|
On some agent server configurations these types of log messages may appear whenever the up.time monitoring station attempts to contact the agent Jun 25 19:19:20 server1 kernel: cdrom: open... By: CSS | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 307 |
4865 |
/var/adm/messages: inetd uptmagnt connection warnings | Rating | Views | |
---|---|---|---|
On some UNIX or Linux servers you may notice repeated messages like the ones below in your messages log once you start monitoring the server with up.time. Jul 2 14:43:27 hostname inetd[486]:... By: CSS | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 308 |
3382 |
Data collector won't start - "Not a trusted IP" error in uptime.log | Rating | Views | |
---|---|---|---|
If your data collector service will not start due to an error in uptime.log similar to: xxx.xxx.xxx.xxx: is not a trusted ip xxx:xxx:000:xxx:xxx:0X0x:x000: is not a trusted ip It is usually due... By: CSS | Date Created: 10-2-2009 | Last Modified: 8-10-2011 | Index: 382 |
2409 |
ERROR: Connection pool congestion | Rating | Views | |
---|---|---|---|
Example uptime.log entries: 2010-05-09 15:59:16,447 WARN (RealSessionFactory:63) - Connection pool congestion: busy: 450 idle: 50 total:500 maximum: 500 2010-05-09 15:59:16,447 WARN... By: CSS | Date Created: 6-5-2010 | Last Modified: 8-13-2011 | Index: 441 |
2188 |
ERROR: Thread pool backlog | Rating | Views | |
---|---|---|---|
Example uptime.log entries: 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... By: CSS | Date Created: 6-5-2010 | Last Modified: 2-20-2013 | Index: 442 |
2090 |
License Reload message on UI instance | Rating | Views | |
---|---|---|---|
On a uiOnlyInstance you may notice many log messages similar to those below: 2010-08-12 10:13:03,819 DEBUG (LicenseProxyCommandExecutor:19) - Running License Reload on Monitoring Station...... By: CSS | Date Created: 8-13-2010 | Last Modified: 8-10-2011 | Index: 477 |
1816 |
php error_log file growing due to deprecated messages | Rating | Views | |
---|---|---|---|
Example log messages: [02-Jun-2010 14:29:51] PHP Deprecated: Function split() is deprecated in C:\Program Files\uptime software\uptime\GUI\classes\protocol\ProtocolParser.inc on line 30... By: CSS | Date Created: 6-5-2010 | Last Modified: 8-13-2011 | Index: 440 |
3319 |
phperror.log file filled with "File does not exist" errors | Rating | Views | |
---|---|---|---|
The default error logging level in is ALL messages. This can cause a number of messages to be registered in the phperror.log, causing it to grow to very large sizes. Some example messages are:... By: CSS | Date Created: 8-13-2010 | Last Modified: 8-13-2011 | Index: 478 |
2219 |
Resolving JVM_BIND Errors in up.time | Rating | Views | |
---|---|---|---|
By: CSS | Date Created: 6-7-2006 | Last Modified: 8-9-2011 | Index: 075 |
9639 |
Resolving uptimeagent Daemon Messages | Rating | Views | |
---|---|---|---|
By: CSS | Date Created: 6-13-2006 | Last Modified: 10-28-2011 | Index: 081 |
5902 |
up.time causing excessive ESX connection logging | Rating | Views | |
---|---|---|---|
When up.time connects to an ESX server to collect performance data it registers a unique connection to the hosts API. This can cause an increase in logging on the server as each poll (for example... By: CSS | Date Created: 8-6-2010 | Last Modified: 8-10-2011 | Index: 467 |
1854 |
up.time does not start - Java heap size too high | Rating | Views | |
---|---|---|---|
If the up.time 4 Data Collector fails to start and messages like those below are found in the wrapper.log you may have to adjust your java heap size to a lower value. wrapper.log: ........ STATUS... By: CSS | Date Created: 10-10-2009 | Last Modified: 8-13-2011 | Index: 422 |
2701 |
uptime.log shows error: java.sql.SQLException ORA-00018 | Rating | Views | |
---|---|---|---|
This error indicates that the up.time Data Collector was unable to open more sessions with your Oracle database backend. This can have a negative impact on up.time performance and stability.... By: CSS | Date Created: 8-5-2010 | Last Modified: 8-10-2011 | Index: 465 |
2218 |