Unsolved
This post is more than 5 years old
1 Rookie
•
1 Message
0
2760
December 12th, 2016 10:00
NetWorker Management Console Timeout after ~30min-1hr
Has anybody else ever found that NMC Java Client hangs at 5% then says "Lost Connection to Console Server, closing client" anywhere from 30-60 minutes of idle time?
NMC 8.2.1 on Solaris 10.. apparently before the move to 8.2.1 this wasn't an issue (upgrade happened before I joined the team), but since then, if I'm not constantly using the client, it'll die on me (which is really annoying!)
I've checked with the network people, and they say there is no forced closing of connections on idle timeout.. no firewall rules in place to kill idle connections... I haven't noticed anything between versions of Java (1.7 or 1.8 still time out)..
I've tried opening the console from the server itself to see if it is a NetWorker issue or some environmental condition, but it doesn't like it when I try (Java is installed, but is an older version..might not be able to handle running the UI on the server, and I can't upgrade the installed Java for the time being)
So I'm reaching out to you, to see if anybody has encountered this before and perhaps know of how to resolve it.
Any thoughts/troubleshooting steps would be greatly appreciated!
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
December 12th, 2016 14:00
I've seen this only related to network (eg. in country A it works fine, but from country B it fails) and it is related to office network in my case. I can't explain why do you see it with change of NMC version, but it might be related perhaps to some other component which has hardcoded timeout in such case (eg. Apache). I personally never stick with NMC for long so I can't say that I ever been in NMC longer than 20 minutes, but I noticed if I left it idle then I would get what you described under circumstances I described.
SimoB
1 Message
0
August 17th, 2020 20:00
Hi,
Did you figure it out ?
I'm getting the same issue since we moved to NW 9.1.
NMC and NW are in same sever.
Any ideas ?
Thanks for your reply.
BR
crazyrov
6 Operator
•
1.3K Posts
0
August 17th, 2020 23:00
Hi @SimoB ,
Check the token timeout which is under NMC -> Setup -> Configure Authentication Service Token Timeout. But if the connection between your management host(eg: you laptop or jump-host) and the NMC server is being terminated then you might want to take a look at the firewall between there 2 systems.
CrashCart
2 Intern
•
69 Posts
0
August 19th, 2020 10:00
Not sure if this applies to your situation, but for me, NMC starts acting cranky and crashes (symptoms like progress bar at 5%, which never gets past that, and the whole thing just stops responding) every once in a while.
It happens recurringly and often enough that I just have it in my calendar to restart NMC once a month - "systemctl restart gst" works wonders in my environment as far as NMC goes