Upgrade Issues

Below are tips on how to resolve common problems encountered when upgrading MailArchiva. Please also refer to Server Won't Start for further information on how to troubleshoot server startup issues.

 

Upgrade To MailArchiva V8.11 (Server Won't Start)

 

When MailArchiva V8.11+ is downloaded and installed over any version prior to V8.11, the server may not start. The reason being, MailArchiva V8.11+ upgrades to Tomcat 9 and the auto update system has been changed.

 

Edit C:ProgramDataMailArchivaTomcatconfserver.xml (Windows)
Edit /var/opt/mailarchiva/tomcat/conf/server.xml (Linux) 

 

a) In the host tag, ensure autoDeploy and unpackWARS are set to true.

 

<Host appBase="webapps" autoDeploy="true" name="localhost" unpackWARs="true" startStopThreads="6">

 

b) Remove all update service tag lines as illustrated below:

  <Service name="UpdateService">
    <Engine name="UpdateServiceEngine" defaultHost="localhost">
        <Host name="localhost"  appBase="update"
            unpackWARs="false" autoDeploy="false”> </Host>
    </Engine>
</Service>

 

c) In the TLS connector (if enabled), change the keyPass attribute to keystorePass.

 

<Connector port="443" allowUnsafeLegacyRenegotiation="false"  SSLEnabled="true" scheme="https" secure="true" clientAuth="false" keyAlias="tomcat" keystoreFile="/etc/opt/mailarchiva/ROOT/mailarchivacerts" keyPass="..."] ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA" sslProtocol="TLS" compression="on" compressionMinSize="2048" noCompressionUserAgents="gozilla, traviata" maxThreads="500" minSpareThreads="25" acceptCount="500" connectionTimeout="20000" URIEncoding="UTF-8" protocol="org.apache.coyote.http11.Http11NioProtocol" compressableMimeType="text/html,text/xml,text/plain,text/javascript,application/javascript,application/json"/>

 

d) Ensure the AJP connector includes address and secretRequired attributes as follows:

 

<Connector port="8011" protocol="AJP/1.3" redirectPort="8443" address="0.0.0.0" secretRequired="false" />

 

Afterwards, restart MailArchiva for changes to take effect.

 

Slow startup

 

If you experience an extremely slow startup, it likely means the graph database is corrupted. Refer to GraphDB for a resolution.

 

Invalid License

 

A license file is tied to a specific customer and a major release of MailArchiva. After upgrading, it is necessary to obtain a new license file from Stimulus Software and install the license file.

 

Heap Space Changed

 

When running the installer on Windows, heap space settings may be lost. It is prudent to check the heap space settings after an upgrade. To do this, open the MailArchiva task tray applet from Windows->Program Files->Applet. Right click applet (bottom right corner of Windows task bar), click Configure, select Java tab, verify maximum heap space setting is desirable. Typically, 5G or 6G. 

 

Windows Logon Account Changed

 

The installer may lose the MailArchiva Service Logon Account settings. Therefore, especially in Windows environments that archive to remote storage (e.g. a NAS), after an upgrade it is advisable to reconfigure the logon account of the MailArchiva service. To do this, open Windows Services, right click the MailArchiva service, change the Logon Account to a Windows account with sufficient privileges to read/write to the NAS. Restart MailArchiva service for changes to take effect.

 

Server Will Not Start

 

Incorrect Memory Settings

 

The server may not start if either too much or too little heap space is allocated to MailArchiva. Refer to Heap Space Changed and Memory Settings for further information on adjusting heap space within acceptable limits.

 

Web Console Does Not Show
 

Incompatible Tomcat server.xml File

 

It is possible that MailArchiva includes version of Tomcat that is expecting a newer version of its server.xml with a different structure. The installer preserves the old server.xml to protect against losing potential HTTP/S customizations. Assuming this is the case, the resolution as follows:

 

  • Stop the MailArchiva service
  • Move C:ProgramDataMailArchivaTomcat to C:BackupTomcat or /var/opt/mailarchiva/tomcat to /root/tomcat
  • Rerun the MailArchiva installer

 

Web Console GUI Looks Mangled


Most likely your browser has cached pages. Press Shift + Refresh in your browser to reload the MailArchiva GUI and it should straighten out. 

 

All Volumes UnMounted

 

MailArchiva doesn't have sufficient privileges to read/write to the volumeinfo file residing the root of the volume's store. Refer to Windows Logon Account Changed above.

Was this information helpful?

Found this information useful? Visit mailarchiva.com to learn more about MailArchiva.

The page cannot be found

The page you are looking for might have been removed, had its name changed, or is temporarily unavailable. Please make sure you spelled the page name correctly or use the search box.