If you did not log out of the up.time UI before upgrading (refer to step 5 of Upgrading to up.time 7.2 of Later), you may see the following error after attempting to login after the upgrade:
To resolve this issue, you can force the logout by navigating to: http://servername:9999/main.php?logout=1 where servername:9999 is the name of your server and the port you use to connect to up.time.
Other options to clear the issue include:
|
Oracle database not responding in up.time interface | Rating | Views | |
---|---|---|---|
![]() |
If you are seeing a Database Not Responding message in up.time GUI, with something similar to the following error: =================== Database is not responding ... By: uptime Support | Date Created: 10-14-2009 | Last Modified: 8-13-2011 | Index: 436 |
![]() ![]() ![]() ![]() ![]() |
3101 |
"Database Not Responding" Message Appears in Global Scan | Rating | Views | |
---|---|---|---|
![]() |
When this issue occurs, check the uptime.log file for messages similar to the following: 011-03-29 11:40:48,873 ERROR (ProtocolHandler:79) - In command... By: uptime Support | Date Created: 7-9-2011 | Last Modified: 10-26-2012 | Index: 539 |
![]() ![]() ![]() ![]() ![]() |
2496 |
Monitoring a User Login Web Page | Rating | Views | |
---|---|---|---|
![]() |
By: uptime Support | Date Created: 6-5-2006 | Last Modified: 12-31-1969 | Index: 074 |
![]() ![]() ![]() ![]() ![]() |
10749 |
Plug-in returns UNKNOWN - Error: Problem running monitor | Rating | Views | |
---|---|---|---|
![]() |
Generally this is caused by one of two issues 1) The monitor isn't compatible with the version that you have upgraded to. Ensure that you have the latest version of the monitor, send the full... By: uptime Support | Date Created: 8-20-2010 | Last Modified: 8-13-2011 | Index: 491 |
![]() ![]() ![]() ![]() ![]() |
2283 |
Upgrading to up.time 7.2 and 7.3 | Rating | Views | |
---|---|---|---|
![]() |
By: uptime Support | Date Created: 10-25-2005 | Last Modified: 5-20-2014 | Index: 033 |
![]() ![]() ![]() ![]() ![]() |
27184 |