Article Number: 540774

printer Print mail Email

VDP: Log in to VDP fails with the error "Unable to connect to the requested VDP Appliance"

Summary: Log in to VDP Appliance from the vCenter fails with the error "Unable to connect to the requested VDP Appliance"

Primary Product: Avamar

Product: Avamar Virtual Edition more...

Last Published: 28 May 2020

Article Type: Break Fix

Published Status: Online

Version: 4

VDP: Log in to VDP fails with the error "Unable to connect to the requested VDP Appliance"

Article Content

Issue


Log in to the VDP Appliance GUI from the vCenter fails with the error:    
 
"Unable to connect to the requested VDP Appliance" 
 

Reviewing the /usr/local/avamar/var/vdr/server_logs/vdr-configure.log log file, the VDP configuration Tomcat process is trying to define the state of the AV installer process. It keeps looping through the following status:    
 
> 2020-01-08 08:55:48,506 INFO  [pool-25-thread-1]-scheduler.AviStateMachine: Switching state from LOGOUT_ERROR to LOGGED_OUT
> 2020-01-08 08:55:48,506 INFO  [pool-25-thread-1]-scheduler.AviStateMachine: Switching state from LOGGED_OUT to LOGOUT_ERROR
> 2020-01-08 08:56:20,042 INFO  [pool-25-thread-1]-scheduler.AviStateMachine: Switching state from LOGOUT_ERROR to LOGGED_OUT
> 2020-01-08 08:56:20,043 INFO  [pool-25-thread-1]-scheduler.AviStateMachine: Switching state from LOGGED_OUT to LOGOUT_ERROR
Confirm if there is an ISO attached to the VDP appliance from the Settings , detach it and restart the  emwebapp.sh service, that would generally fix the error,
However if the problem would still exist, check the directory "/data01/avamar/repo/packages" and confirm if an avp package is still listed under the packages directory.
Review the log file "/usr/local/avamar-tomcat/logs/catalina.out" , multiple errors reported with the statement:
 
"HTTP header too large"
Cause
There was a missing "maxHttpHeaderSize" entry in the configuration file "/usr/local/avamar-tomcat/conf/server.xml".  

The file looks similar to:    
 
Connector SSLEnabled="true" Server="Avamar" ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_....." clientAuth="false" maxKeepAliveRequests="1" maxThreads="150" port="8543" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2"/>

By default, the file configuration file "/usr/local/avamar-tomcat/conf/server.xml" section for port 8543 should have the entry "maxHttpHeaderSize" which looks similar to:    
 
        <Connector port="8543" maxHttpHeaderSize="32768" protocol="org.apache.cyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" maxKeepAliveRequests="1" clientAuth="false" sslEnabledProtocols="TLSv1.1,TLSv1.2" Server=" Avamar ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA......" />

In this case, entry maxHttpHeaderSize="32768" was missing and had  to be added manually.
Resolution
Procedure:   
  1. Take a copy of the file /usr/local/avamar-tomcat/conf/server.xml:    
cp -p /usr/local/avamar-tomcat/conf/server.xml /usr/local/avamar-tomcat/conf/server.xml-BEFOREDATE
  1. Edit the server.xml file:    
vi /usr/local/avamar-tomcat/conf/server.xml
  1. Under the 8543 port section, add the entry maxHttpHeaderSize="32768":   
It should look similar to the following:    
 
Connector SSLEnabled="true" Server="Avamar" ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_ ...." clientAuth="false" maxKeepAliveRequests="1" maxThreads="150" port="8543" maxHttpHeaderSize="32768"  protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2"/>
  1. Save the file and restart the web services:    
emwebapp.sh --restart

Connect to the VDP appliance. The issue should be addressed.
Notes

The entry "maxHttpHeaderSize" should be found by default, in all the VDP versions. It was not present on the file for some unknown reason which should be checked.

Issue


Log in to the VDP Appliance GUI from the vCenter fails with the error:    
 
"Unable to connect to the requested VDP Appliance" 
 

Reviewing the /usr/local/avamar/var/vdr/server_logs/vdr-configure.log log file, the VDP configuration Tomcat process is trying to define the state of the AV installer process. It keeps looping through the following status:    
 
> 2020-01-08 08:55:48,506 INFO  [pool-25-thread-1]-scheduler.AviStateMachine: Switching state from LOGOUT_ERROR to LOGGED_OUT
> 2020-01-08 08:55:48,506 INFO  [pool-25-thread-1]-scheduler.AviStateMachine: Switching state from LOGGED_OUT to LOGOUT_ERROR
> 2020-01-08 08:56:20,042 INFO  [pool-25-thread-1]-scheduler.AviStateMachine: Switching state from LOGOUT_ERROR to LOGGED_OUT
> 2020-01-08 08:56:20,043 INFO  [pool-25-thread-1]-scheduler.AviStateMachine: Switching state from LOGGED_OUT to LOGOUT_ERROR
Confirm if there is an ISO attached to the VDP appliance from the Settings , detach it and restart the  emwebapp.sh service, that would generally fix the error,
However if the problem would still exist, check the directory "/data01/avamar/repo/packages" and confirm if an avp package is still listed under the packages directory.
Review the log file "/usr/local/avamar-tomcat/logs/catalina.out" , multiple errors reported with the statement:
 
"HTTP header too large"
Cause
There was a missing "maxHttpHeaderSize" entry in the configuration file "/usr/local/avamar-tomcat/conf/server.xml".  

The file looks similar to:    
 
Connector SSLEnabled="true" Server="Avamar" ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_....." clientAuth="false" maxKeepAliveRequests="1" maxThreads="150" port="8543" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2"/>

By default, the file configuration file "/usr/local/avamar-tomcat/conf/server.xml" section for port 8543 should have the entry "maxHttpHeaderSize" which looks similar to:    
 
        <Connector port="8543" maxHttpHeaderSize="32768" protocol="org.apache.cyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" maxKeepAliveRequests="1" clientAuth="false" sslEnabledProtocols="TLSv1.1,TLSv1.2" Server=" Avamar ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA......" />

In this case, entry maxHttpHeaderSize="32768" was missing and had  to be added manually.
Resolution

Procedure:   
  1. Take a copy of the file /usr/local/avamar-tomcat/conf/server.xml:    
cp -p /usr/local/avamar-tomcat/conf/server.xml /usr/local/avamar-tomcat/conf/server.xml-BEFOREDATE
  1. Edit the server.xml file:    
vi /usr/local/avamar-tomcat/conf/server.xml
  1. Under the 8543 port section, add the entry maxHttpHeaderSize="32768":   
It should look similar to the following:    
 
Connector SSLEnabled="true" Server="Avamar" ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_ ...." clientAuth="false" maxKeepAliveRequests="1" maxThreads="150" port="8543" maxHttpHeaderSize="32768"  protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2"/>
  1. Save the file and restart the web services:    
emwebapp.sh --restart

Connect to the VDP appliance. The issue should be addressed.

Notes

The entry "maxHttpHeaderSize" should be found by default, in all the VDP versions. It was not present on the file for some unknown reason which should be checked.

Article Attachments

Attachments

Attachments

Article Properties

First Published

Wed Jan 29 2020 10:54:51 GMT

First Published

Wed Jan 29 2020 10:54:51 GMT

Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters