Re: connection of Agent to Management is continuously dropping
Are you by any chance using IBM java 1.7.x on your management server ? We had a similar problem where connection from cloud agent on CPVM/SSVM to management server got disconnected with an SSL error, but we are not using SSL on management server at all. After switching back to java-1.7.0-openjdk, the problem went away without any other configuration changes. Yiping On 6/14/15, 11:40 PM, Devender Singh dev1986en...@gmail.com wrote: I have disable SS by setting secstorage.encrypt.copy to false, and changing consoleproxy.url.domain to empty. but after restarting the console proxy vm I am getting below error. netstat -na | grep 8250 tcp 867 0 x.x.x.x:37789 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38275 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 .x.x.x:37942 y.y.y.y:8250 CLOSE_WAIT by Devender kumar Singh On Fri, Jun 12, 2015 at 4:53 PM, Devender Singh dev1986en...@gmail.com wrote: After upgrading cloudstack 4.2.1 to 4.4.2 we are facing console proxy agent issue . connection of Agent to Management is continuously dropping netstat -na | grep 8250 tcp 867 0 x.x.x.x:37789 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38275 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 .x.x.x:37942 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x3:38327y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37810 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37737 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37775 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37858 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38039 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37960 y.y.y.y:8250 CLOSE_WAIT
Re: connection of Agent to Management is continuously dropping
I have disable SS by setting secstorage.encrypt.copy to false, and changing consoleproxy.url.domain to empty. but after restarting the console proxy vm I am getting below error. netstat -na | grep 8250 tcp 867 0 x.x.x.x:37789 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38275 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 .x.x.x:37942 y.y.y.y:8250 CLOSE_WAIT by Devender kumar Singh On Fri, Jun 12, 2015 at 4:53 PM, Devender Singh dev1986en...@gmail.com wrote: After upgrading cloudstack 4.2.1 to 4.4.2 we are facing console proxy agent issue . connection of Agent to Management is continuously dropping netstat -na | grep 8250 tcp 867 0 x.x.x.x:37789 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38275 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 .x.x.x:37942 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x3:38327y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37810 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37737 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37775 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37858 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38039 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37960 y.y.y.y:8250 CLOSE_WAIT
Re: connection of Agent to Management is continuously dropping
Hi Devender, I've experience a similar issue a few times in my test environments, so i took a closer look at what was causing it... If you're experiencing the same issue, here's the symptoms, cause and resolution: Symptoms: - SSL fails to start on tomcat; - SSL connection fails to establish between agent and management; Diagnose: Run: file /etc/cloudstack/management/cloudmanagementserver.keystore On a good setup should display: /etc/cloudstack/management/cloudmanagementserver.keystore: Java KeyStore On a bad setup should display: /etc/cloudstack/management/cloudmanagementserver.keystore: data Cause: Management server has been setup to use encryption for configuration stored in DB. (This affects all fields marked as Hidden in the configuration table in mysql) DB Encryption secret is missing or wrong in /etc/cloudstack/management/db.properties (This happens when you uninstall and reinstall and db.properties gets replaced with fresh one) Resolution: Option 1: Restore a previous copy of your db.properties to decrypt configuration values correctly and restart management server. Option 2(only if you don't have a backup but you should ;) ): Delete ssl.keystore from table, this will make server to create a fresh one on restart. On startup, server always creates a new instance of the keystore file, based on what is read from the configuration table or creates and stores a new one if none is there. Let me know if this helps :) Cheers, Rafael On Fri, Jun 12, 2015 at 1:23 PM, Devender Singh dev1986en...@gmail.com wrote: After upgrading cloudstack 4.2.1 to 4.4.2 we are facing console proxy agent issue . connection of Agent to Management is continuously dropping netstat -na | grep 8250 tcp 867 0 x.x.x.x:37789 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38275 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 .x.x.x:37942 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x3:38327y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37810 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37737 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37775 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37858 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38039 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37960 y.y.y.y:8250 CLOSE_WAIT
connection of Agent to Management is continuously dropping
Hi Team, After upgrading cloudstack 4.2.1 to 4.4.2 we are facing console proxy agent issue . connection of Agent to Management is continuously dropping netstat -na | grep 8250 tcp 867 0 x.x.x.x:37789 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38275 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 .x.x.x:37942 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x3:38327y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37810 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37737 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37775 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37858 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38039 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37960 y.y.y.y:8250 CLOSE_WAIT Thanks and Regards, Devender Kumar Singh
connection of Agent to Management is continuously dropping
After upgrading cloudstack 4.2.1 to 4.4.2 we are facing console proxy agent issue . connection of Agent to Management is continuously dropping netstat -na | grep 8250 tcp 867 0 x.x.x.x:37789 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38275 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 .x.x.x:37942 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x3:38327y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37810 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37737 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37775 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37858 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:38039 y.y.y.y:8250 CLOSE_WAIT tcp 867 0 x.x.x.x:37960 y.y.y.y:8250 CLOSE_WAIT
