Incorrect memory size allocation

 

The server may not start because:
 

a) MailArchiva has been allocated more RAM than is physically available on your machine

b) MailArchiva has been allocated too little RAM. The minimum amount of allocated RAM should be 384 MB

c) On 32 bit OS platforms, MailArchiva has been allocated more than 1512m (the limit on 32bit Windows OS)
 

 

 

Common resolution

 

Linux repair

 

systemctl stop mailarchiva
Take note of heap space setting in /opt/mailarchiva/server/startserver CATALINA_OPTS
curl -sS https://bs.stimulustech.io/api/v1/download/product/maonprem/linux/latest | grep -oP '"downloadUrl": *"K[^"]*' | xargs curl | tar -xz -C /tmp && cd /tmp/mailarchiva_dist* && ./install
Please choose the same heap space setting as before.
mv /var/opt/mailarchiva/ROOT/queue/receive to mv /var/opt/mailarchiva/ROOT/queue/restore_receive
mv /var/opt/mailarchiva/ROOT/queue/index to mv /var/opt/mailarchiva/ROOT/queue/restore_index

It may also be necessary to clear the folder structures due to the Orient DB database corruption. Doing so will blow away folder structures, if any, but not user information. This is an optional step.

mv /var/opt/mailarchiva/ROOT/database/archiva /root/archiva (or backup location)

systemctl start mailarchiva

 

Windows repair

 

If the MailArchiva task tray applet isn't loaded, load it from the Windows program files menu.

Take note of Heap space settings in the MailArchiva applet. Right click Configure on the MailArchiva task tray applet, select Java tab ()
Download the latest setup from https://bs.stimulustech.io/downloads & run the setup
Follow the exact same heap space settings as used before.
Rename C:ProgramDataMailArchivawebappsROOTqueuereceive to C:ProgramDataMailArchivawebappsROOTqueuerestore_receive
Rename C:ProgramDataMailArchivawebappsROOTqueueindex to C:ProgramDataMailArchivawebappsROOTqueuerestore_index

It may also be necessary to clear the  folder structures due to Orient DB database corruption. Doing so will blow away folder structures, if any, but not user information. This is an optional step.

Rename C:ProgramDataMailArchivawebappsROOTdatabasearchiva to C:archiva (or backup location)
Start MailArchiva from service applet

 

If the server still doesn't start, examine the log files below for clues:
 

/var/opt/mailarchiva/tomcat/logs (Linux)
C:ProgramDataMailArchivaTomcatlogs (Windows)

 

Other reasons why the service won't start

 

• A TLS connector is enabled in server.xml and the keyPass and/or aliases do not correspond with the mailarchivacerts keystore.
• TLS connector attributes in server.xml are sensitive. e.g. keyPass attribute is defined as all lowercase (it must be keyPass and is case sensitive).
• AJP connector must be defined as <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" address="0.0.0.0" secretRequired="false" />

Recently upgraded from a previous version (Windows)

 

If the server doesn't start after having recently upgraded from a previous version, it could be that there is a mix-up in program files. The steps to resolve are as follows:

• Ensure the server is stopped and the MailArchiva Task Tray is exited
• Ensure there are no MailArchiva processes running in the Task Tray
• Make sure that volume data is not stored in the same location as the C:Program FilesMailArchiva location
• Uninstall the MailArchiva software from Program and Features (the configuration will be preserved)
• Everything under C:Program FilesMailArchiva should be deleted
• Rerun the installer
• Start the server

 

Locked files during upgrade (WIndows)

 

While upgrading MailArchiva to a newer version, it is possible that the setup could not shut down the previous version of MailArchiva and its program files could not be overwritten. To resolve this, try switching the MailArchiva Windows service to manual start using the Windows Services applet and reboot the machine. Thereafter, after the machine is rebooted, rerun the installer. 

 

Common listening ports already taken

 

a) The server cannot listen on ports 8090, 8005, 8091, 8092, 8009 since they have already been taken

b) You can check if these ports are taken by doing the following:

From the Windows command-line, type:

 

c) On Windows, you can run MailArchiva in Console mode by running the C:Program FilesMailArchivaServerbinMailArchivaServer.exe file.

d) In the console output, if it complains about a port conflict, you know you need to change ports.

e) On Linux, you should see the symptoms of a port conflict in the /usr/local/mailarchiva/server/logs/catalina.out file.

 

Resolution:

(a) Edit the file server.xml in C:Program FilesMailArchivaServerconf or /usr/local/mailarchiva/server/conf and change the ports

(b) Edit the 8091 (smtp) and 8092 (milter) ports in the MailArchiva server GUI or server.conf file
 

 

 

Directory and file interference

MailArchiva loads multiple tenants based on the contents of the instances and program directoryserverwebapps folders. If there are backup files and directories placed in these folders, system instability can result. The resolution is to:

 

• Ensure that there are no folders other than ROOT (..and other instance names if MT mode enabled), logs, core in /etc/mailarchiva/ and C:ProgramDataMailArchiva
• Ensure that there are no folders other than ROOT in /opt/mailarchiva/server/webapps/ and C:Program FilesMailArchivaserverwebapps

 

Corrupted database

 

 

Stop the server

Rename [application data]/database to [application data]/database_bak

Start the server

 

Corrupted queue database

 

 

It is possible that your queue database is corrupted. 

 

Stop the server

Delete the contents of [application data]/queue/ctl

Start the server

 

Multiple servers running

There are multiple instances of the server running.

From the Windows Task Manager, kill all Java processes before starting the server

On Linux, enter the following command in the command prompt:
 

 

Java runtime path issues

The location of the Java Runtime Environment is not on the PATH environment.

Resolution:

Add C:Program FilesMailArchivajrebin to the Windows PATH.
 

C++ runtime libraries

 

In some installations, Tomcat may not be able to locate the C++ runtime libraries.

Resolution:

Copy C:Program FilesMailArchivajrebinmsvcr71.dll to C:WindowsSystem32 and restart the server.

 

Further debugging

 

If your problem is not helped by any of the above, startup errors are usually displayed in the catalina.out log, located at:
 

 

 

Please also examine the log files in: