Timeouts and login failures after update to 1.4.2
Posted: Wed Jul 27, 2016 10:28 am
Yesterday, I updated both of my cluster servers to 1.4.2. All went smoothly until I noticed timeouts in the web UI as well as login failures without any errors. Here's the behavior I'm seeing:
I log in to the UI and all looks normal. Cluster health looks good and instances are green and happy. After a few minutes of being idle, I'll notice the "System Status" indicators on the top go red. A mouse-over text bubble shows "Could not authenticate. Invalid token given." If I click on any of the menu items, it will spit me back out to the login page. In firefox, populating the login info and clicking "Log In" will let me in. In Chrome, the login page keeps refreshing and won't let me back in. Closing the tab and opening the cluster URL will finally get me back in.
I hope I was successful in describing the behavior. Please let me know what I can check to begin the troubleshooting process. I'd like to stress that this problem has never existed in my cluster prior to upgrading to 1.4.2 yesterday. I'm also using LDAP integration, but even using local logins will produce the same behavior and results. Thank you in advance.
I log in to the UI and all looks normal. Cluster health looks good and instances are green and happy. After a few minutes of being idle, I'll notice the "System Status" indicators on the top go red. A mouse-over text bubble shows "Could not authenticate. Invalid token given." If I click on any of the menu items, it will spit me back out to the login page. In firefox, populating the login info and clicking "Log In" will let me in. In Chrome, the login page keeps refreshing and won't let me back in. Closing the tab and opening the cluster URL will finally get me back in.
I hope I was successful in describing the behavior. Please let me know what I can check to begin the troubleshooting process. I'd like to stress that this problem has never existed in my cluster prior to upgrading to 1.4.2 yesterday. I'm also using LDAP integration, but even using local logins will produce the same behavior and results. Thank you in advance.