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.

Legacy Volume Format Change

If you are still using legacy V1 and V2 volume formats, it will be necessary to switch to V3 volume format since V1 and V2 volume formats are now marked as read-only. To switch the volume format, go to Configuration→General→Archive, select volume format to V3. Save. Visit Configuration→Volumes, create a new volume and close the existing Active one.h the volume format, go to Configuration→General→Archive, select volume format to V3. Save. Visit Configuration→Volumes, create a new volume and close the existing Active one

Upgrade To MailArchiva V9 (server won't start)

MailArchiva v9 uses an upgraded version of Tomcat (Version 10) application server. After performing an upgrade from MailArchiva V8 to V9, the server may fail to start due to differences in the manner in which TLS is configured in its server.xml file.

Edit C:\ProgramData\MailArchiva\Tomcat\conf\server.xml (Windows)
Edit /var/opt/mailarchiva/tomcat/conf/server.xml (Linux) 

c) In the TLS connector (if enabled), either replace the entire connector or add the SSLHostConfig tag as shown below.

Restart the server. If the server still fails to startup, examine the Tomcat startup logs in /var/opt/mailarchiva/tomcat/logs (Linux) or C:\ProgramData\MailArchiva\Tomcat\logs (Windows) and make corrections as needed.

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:\ProgramData\MailArchiva\Tomcat\conf\server.xml (Windows)
Edit /var/opt/mailarchiva/tomcat/conf/server.xml (Linux) 

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

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

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

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

Afterwards, restart MailArchiva for changes to take effect.

Slow startup

If you experience a slow startup, it could mean the server has run out of entropy or the graph database is busy upgrading/repairing itself. In the former case, install Haveged. In the latter case, it may take a while for the server to complete the repair of the graph database. 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

As of V8.11, MailArchiva won't start if there is any abnormal condition, such as a corrupted graph database. To ascertain why the server won't start, refer to the debug.log files at  /var/log/mailarchiva/ROOT/logs (C:\ProgramData\MailArchiva\ROOT\logs) or /var/log/mailarchiva/core/logs (C:\ProgramData\MailArchiva\core\logs).

Corrupted graph database

If there is a corrupted graph database, the debug.log file in /var/log/mailarchiva/ROOT/ or C:\ProgramData\MailArchiva\ROOT\logs will contain database related errors. 

One possible solution is to delete/rename the graph database:

Stop MailArchiva service

delete C:\ProgramData\MailArchiva\ROOT\database\archiva (Windows)

rm /var/opt/mailarchiva/ROOT/database/archiva (Linux)

Corrupted queue database

If there is a corrupted queue database:

Stop MailArchiva service

rename C:\ProgamData\MailArchiva\ROOT\queue\receive to C:\ProgamData\MailArchiva\ROOT\queue\restore_receive (Windows)

rename C:\ProgamData\MailArchiva\ROOT\queue\index to C:\ProgamData\MailArchiva\ROOT\queue\restore_index (Windows)

mv /var/opt/mailarchiva/ROOT/queue/receive to  /var/opt/mailarchiva/ROOT/queue/restore_receive (Linux)

mv /var/opt/mailarchiva/ROOT/queue/index to  /var/opt/mailarchiva/ROOT/queue/restore_index (Linux)

Corrupted audit index

If there is a corrupted queue database:

Stop MailArchiva service

delete C:\ProgamData\MailArchiva\ROOT\logs\audit/index (Windows)
rm /var/opt/mailarchiva/ROOT/logs/audit/index (Linux)

Restart MailArchiva and reindex the audit log file in Configuration->Logs.

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:\ProgramData\MailArchiva\Tomcat to C:\Backup\Tomcat 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.