Перейти к концу метаданных
Переход к началу метаданных

Вы просматриваете старую версию данной страницы. Смотрите текущую версию.

Сравнить с текущим просмотр истории страницы

« Предыдущий Версия 2 Следующий »

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)
 

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 Архива in a VM, you may need to edit your VM settings to allocate more RAM to the virtual environment.

 

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:

 

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 Архива 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 Архива server GUI or server.conf file
 
Port Information: Refer to Ports for an exhaustive list of ports used by Архива.

 

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)

 

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/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:
 

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)


/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)


 

  • Ни одной