Avamar Server: Avamar Virtual Edition integration with vSphere WebClient not working <Tomcat process not starting>

Summary: Tomcat process not starting

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Manually modified "server.xml" file

Avamar Virtual Edition integration with vSphere WebClient not working
Unable to start "Tomcat" after deploying EBR plugin
If the EBR plugin is removed "Tomcat" starts right away.

Error in /usr/local/avamar-tomcat/logs

INFO [ost-startStop-1][ionConfigWebApplicationContext#doClose]: Closing Root WebApplicationContext: startup date [Tue May 23 16:47:55 IST 2017]; root of context hierarchy Exception in thread "ConfigListener" java.nio.file.ClosedWatchServiceException at sun.nio.fs.AbstractWatchService.checkOpen(Unknown Source) at sun.nio.fs.AbstractWatchService.checkKey(Unknown Source) at sun.nio.fs.AbstractWatchService.take(Unknown Source) at com.emc.avamar.vmware.lcrs.upload.config.ConfigurationChangeListener.startWatcher(ConfigurationChangeListener.java:101) ============================================================================== When running "ebrserver.pl" error was: ERROR: Failed to match requested line in tomcat config file at [/usr/local/avamar-tomcat/conf/server.xml] ERROR: Failed to properly update tomcat config file [/usr/local/avamar-tomcat/conf/server.xml]


   

Cause

/usr/local/avamar-tomcat/conf/server.xml had incorrect entry made manually.


The issue was caused by a duplicate entry customer has in "server.xml" file

Customer had 2 entries for the same Connector: Connector port="8543" maxHttpHeaderSize="32768" maxHttpHeaderSize="8192" Which is incorrect. There should only by one "maxHttpHeaderSize" with its value The entry should have been as per the one below. ======================================================== Connector port="8543" maxHttpHeaderSize="32768" protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" maxKeepAliveRequests="1" clientAuth="false" sslProtocol="TLS" Server="Avamar" ciphers="TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA,TLS_ECDHE_ECD

Resolution

  • Ensure that "/usr/local/avamar-tomcat/conf/server.xml" contains the correct entries and format.
  • Ensure file has right permissions and owner:  admin:admin
  • Make sure to make a backup copy of the file before making any modifications.

Additional Information

When "/usr/local/avamar-tomcat/conf/server.xml" contains wrong entries, Tomcat process will not start.

Also /usr/local/avamar-tomcat/logs/catalina.out log will NOT log any infomation.

Affected Products

Avamar

Products

Avamar
Article Properties
Article Number: 000065455
Article Type: Solution
Last Modified: 30 May 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.