Server Won't Start

 

Which startup log files to examine?

 

If the server doesn't start, the cause will usually be revealed in catalina.out and stdout.log files. These files are typically located at:

 

/var/opt/mailarchiva/tomcat/logs (Linux)
C:\ProgramData\MailArchiva\Tomcat\logs (Windows)

 

If the Tomcat directory does not exist, create it manually using File Explorer and restart MailArchiva service.

 

Another way to troubleshoot startup on Windows, is to run the MailArchiva process in console mode. Simply run C:\Program Files\MailArchiva\server\bin\MailArchivaServer.exe from the commandline. It should output the reason why the server cannot start to the console.

 

Upgrade to MailArchiva V8.11+

 

Server won't start due upgrade to MailArchiva V8.11+. It may be necessary to follow these additional v8.11 upgrade steps

 

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)
 

How To Change Memory Settings: Refer to Memory Settings for details on how to adjust the product's memory allocation settings.

 

Virtual Environments (VM) Note: if you are running MailArchiva in a VM, you may need to edit your VM settings to allocate more RAM to the virtual environment

 

Other reasons why service wont 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 mixup 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 FIles\MailArchiva location
  • Uninstall the MailArchiva software from Program and Features (the configuration will be preserved)
  • Everything under C:\Program FIles\MailArchiva 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 setup could not shut down the previous version of MailArchiva and its program files could not be overwritten. To resolve, 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 commandline, type:

 

netstat -abn > ports.txt
notepad ports.txt
ctrl+F to search for desired port
From the Linux commandline, type:
netstat -l | grep 8090


c) On Windows, you can run MailArchiva in Console mode by running the C:\Program Files\MailArchiva\Server\bin\MailArchivaServer.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 Files\MailArchiva\Server\conf or /usr/local/mailarchiva/server/conf and and change the ports

(b) Edit the 8091 (smtp) and 8092 (milter) ports in the MailArchiva server GUI or server.conf file
 
Port Information: Refer to Ports for an exhaustive list of ports used by MailArchiva.

 

VMWare Server and Symantec Antivirus often use ports 8005 and 8009, so you may need to switch these ports.
(We typically switch them to 8015, and 8019, respectively)

 

Directory and file interference


MailArchiva loads multiple tenants based on the contents of the instances and program directory\server\webapps 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:\ProgramData\MailArchiva\
  • Ensure that there are no folders other than ROOT in /opt/mailarchiva/server/webapps/ and C:\Program Files\MailArchiva\server\webapps\

 

Corrupted database

 

Safety Warning: If you delete the database, you will lose all folder and tree view information.

 

Stop the server

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

Start the server

 

Corrupted queue database

 

Safety Note: You will not lose any information by deleting the 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:
 

killall java

 

Java runtime path issues


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

Resolution:

Add C:\Program Files\MailArchiva\jre\bin to the Windows PATH.
 

This advice should be taken especially in the case where you get procrun.c errors in C:\Program Files\MailArchiva\Server\logs\jakarta_service*.log files.


C++ runtime libraries

 

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


Resolution:

Copy C:\Program Files\MailArchiva\jre\bin\msvcr71.dll to C:\Windows\System32 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:
 

C:\Program Files\MailArchiva\server\logs\catalina.out (Windows)
C:\Program Files\MailArchiva\server\logs\stdout.log (Windows)

 

/var/opt/mailarchiva/tomcat/logs/catalina.out (Linux)
/var/opt/mailarchiva/tomcat/stdout.log (Linux)

 

Please also examine the log files in:

 

C:\ProgramData\MailArchiva\ROOT\logs (Windows)
C:\ProgramData\MailArchiva\core\logs (Windows)

 

/var/log/mailarchiva/ROOT/logs (Linux)
/var/log/mailarchiva/core/logs (Linux)
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.