Server Won't Start
Incorrect PermGen Size
Архива now requires a minimum PermGen size of 192M. If Архива was recently upgraded or an auto update was applied, it may be that the specified PermGen size is too small for the newly installed code. Refer to Memory Settings for information on how to adjust the PermGen size to the correct value.
Incorrect Memory Size Allocation
The server may not start because:
a) Архива has been allocated too much RAM than is physically available on your machine
b) Архива has been allocated too little RAM. The minimum amount of allocated RAM should be 384 MB
c) On 32 bit OS platforms, Архива has been allocated more than 1512m (the limit on 32bit Windows OS)
Locked Files During Upgrade (WIndows)
While upgrading Архива to a newer version, it is possible that setup could not shutdown the previous version of Архива and its program files could not be overwritten. To resolve, try switching the Архива 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 are already taken
b) You can check if these ports are taken by doing the following:
From the Windows commandline, type:
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 Архива 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
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/kaha/*
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 Files\MailArchiva\jre\bin 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 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)
/opt/mailarchiva/server/logs/catalina.out (Linux)
/opt/mailarchiva/server/logs/stdout.log (Linux)
Please also examine the log files in:
C:\ProgramData\MailArchiva\ROOT\logs (Windows)
C:\ProgramData\MailArchiva\core\logs (Windows)
/etc/opt/mailarchiva/ROOT/logs (Linux)
/etc/opt/mailarchiva/core/logs (Linux)