Admin console keeps logging out

[GXW]

I have had my eisy up and running since last July and have had no problems with the admin console until this past weekend where it keeps logging out after about 10 minutes.  I have tried searching the forums for a solution but have not been able to fix this.  It started happening after I attempted to install the VUE plugin and as part of the process had clicked on the "Install Dev. Packages" as indicated from this thread 

While I was not able to get the VUE successfully connected I have since not been able to keep my Admin Console logged in and would like to get that fixed as it stops tracking events in the event viewer once it logs out.

Any advice on how to correct this so my admin console will remain logged in and connected?

Thanks

[Techman]

The admin console is not designed to run continiously, but it should stay connected for more than 10 minutes. It's possible that Java is shutting down, or something is interferring with java, which would close the admin console.

 

[paulbates]

It's hard to know as @Techman points out.

When you launch iox from the launcher, do you pick the "Cloud" option from the finder? This would refresh iox itself if something happened to it due to adding dev packages. If that doesn't work, do the "generic" clear cache, reinstall java and iox.

[Geddy]

@GXW as @Techman points out the admin console isn't designed to remain open 24/7. The question is why do you need/want to do that? Are you having issues that you are troubleshooting or are you just leaving it open with the event viewer for your entertainment?

These systems are to be automated and not require non-stop monitoring. If you are having issues then they should be resolved and not something that you just simply try to keep the event viewer open endlessly. It's probably using too many resources and possibly causing Java to fail or stop the admin console process. 

ISY (IoX) does have an event log if you're interested in what's going on. It can be downloaded from admin console and reviewed outside of the IoX system. 

[dbwarner5]

@GXW While it's true what is pointed out above, you should expect more than 10 minutes of connection. Something else is going on. 

Have you tried loading the AC with a direct connection versus with the launcher? 

Go to you browser and type in http://<your eisy ip>:8080/admin.jnlp  

This should download an Admin file to your computer. click on this link and it should take you directly to the sign in for your eisy on your LAN.

This will at lease eliminate Internet connections as an issue. 

[Ross]

22 hours ago, Geddy said:

@GXW as @Techman points out the admin console isn't designed to remain open 24/7. The question is why do you need/want to do that? Are you having issues that you are troubleshooting or are you just leaving it open with the event viewer for your entertainment?

These systems are to be automated and not require non-stop monitoring. If you are having issues then they should be resolved and not something that you just simply try to keep the event viewer open endlessly. It's probably using too many resources and possibly causing Java to fail or stop the admin console process. 

ISY (IoX) does have an event log if you're interested in what's going on. It can be downloaded from admin console and reviewed outside of the IoX system. 

I have my admin console open (minimized usually) at all times.  When it locks up every 5 days or so, I shut it down and reopen it.

I'm a tinkerer and I like having it available for when I get a thought.  I also get ideas from these forums and immediately try it out.  It's just easier to have it be a click away than wait the 2 minutes to boot up (finding the start file, entering the password, waiting for my programs to load).

I assume (and hope) it's not harmful to have it always available.  

Ross

[Guy Lavoie]

I've also been leaving the admin console open for days on end, at least when I was still actively implementing new devices and programs. After reading several posts about it not being a good idea, I'm avoiding doing that now. I'm not sure exactly how it might affect the operation of the eisy itself, but it certainly does end up freezing sometimes, which can be a cause of unneeded resource (cpu, memory, sockets) consumption.