В большинстве случаев, когда архивирование приостановлено, причной является неправильная настройка Архива или почтового сервера. Другой причиной могут быть изменения рабочей среды (например, пароль журналируемого аккаунта изменился или на сервере закончилось дисковое пространство). Самостоятельная остановка не является нормальным поведением сервера, и остановки в архивировании должны быть крайне редки. Если они происходят часто, свяжитесь со службой поддержки для определения причин и быстрого решения этой проблемы.
Архивирование работает стабильно
Если сервер архивирует правильно, открыв вкладку Статус системы -> Графики, вы увидите синие и зеленые линии. Это свидетельствует о том, что сообщения получены от почтового сервера (они обозначены синими линиями) и заархивированы (обозначены зелеными линиями). Совершенно нормально, если за какое-то время принятых сообщений больше, чем заархивированных. Во время периодов низкой активности почтового сервера (к примеру, поздно вечером) сервер Архива нагонит и заархивирует оставшиеся сообщения.
Сообщения не поступают/не архивируются
Если во вкладке Статус системы -> Графики нет никаких линий, сервер не получает никаких писем от почтового сервера.
Возможные причины, почему сервер не получает писем, могут быть в следующем:
- Все в порядке! Просто в данный момент нет писем, поступающих на ваш почтовый сервер.
- General Misconfiguration - Архива и почтовый сервер неверно настроены.
- IMAP Journaling Issues - Решения проблем архивирования, связанных с IMAP журналированием
- SMTP/Milter Archiving Issues - Решение SMTP/Milter archiving problems
- No Disk Space Left - На одном из ваших дисков закончилось свободное место.
Архива или почтовый сервер неправильно настроены
Refer to Mail Servers for general configuration instructions.
- An IMAP Client Connection is not created and connected to the Exchange Journal Account, or the connection is disabled
Resolution: a) Ensure the IMAP Connection is created in Configuration->Connections and enabled. See Client Connections for more information.
b) Test connectivity to the mail server, by clicking in Test Connection in Configuration->Connections->IMAP Connection.
- The Journal Account password is expired/changed.
Resolution:
a) Reset the journal account password in Exchange
b) Ensure the journal account is not disabled
c) Ensure the account password has not expired
d) Ensure Journal account force password change is off - The Exchange IMAP service is stopped or frozen.
Resolution: Restart the IMAP Service on the mail server. - There are too many messages (>20,000) in the journal account.
Resolution: a) Uncheck all checkboxes in Connections>IMAP (except enabled), lower polling interval to 10 msec. Check to see if archiving speeds up. OR
b) Worst case scenario - Recreate the Journal account and reconfigure envelope journaling to forward mails to the new account. Use Exchange import to import old mails. - The polling interval specified in Client Connections->IMAP may be set to a figure that is either too high or too low.
Resolution: The polling interval should never be lower than 10 msec. If it is too high, it may not keep up with the mail flow in your organization and emails will build up the journal account. Once the journal account is too full, Exchange may find it difficult to deal with the large number of emails in the journal account. - IMAP Idle is enabled - some mail servers, such as Microsoft Exchange, fail to deliver messages when IMAP Idle is enabled after a long period.
Resolution: Disable IMAP Idle in IMAP Client Connection - Lost connectivity to your mail server
Resolution: a) Telnet to port 143 or 443 to the mail server address from your Архива server. If there is no response (output), there is likely to be a basic connectivity issue
b) Ensure there is no firewall anywhere along the network path to the mail server (including those running on both servers) blocking communications on port 143 or 443
c) Ensure there are no DNS issues at play by telnetting to the IP address of the Mail Server (i.e. not using the fully qualified domain name)
d) Verify that general network connectivity is available to both servers (e.g. check that the green link light on each network card is visible)
To kick-off IMAP journaling after archiving has stopped, disable Enable check box in Journal Accounts. Click Save. Click Enable check box in Journal Account. Click Save.
If IMAP journaling stops after checking all of the above, please contat us. Alternatively, use SMTP journaling in place of IMAP journaling.
- An SMTP/Milter Listener Connection is not created, enabled or listening on the correct port
Resolution: In the Listeners Configuration section, confirm that an SMTP/Milter Listener is created, is listening on the correct port and is enabled
Telnet to the appropriate port on the Архива server IP address. If a response is received, the listener service is listening as it should.
For a more comprehensive SMTP test: Download and install the Thunderbird mail client on your desktop. Configure a dummy account, to send to Архива's SMTP server on the correct port. You may need to switch Архива's SMTP server to use port 25 for the experiment. Use Thunderbird to send a test message. If all is well, the test message should appear in the search results.
- No traffic is being sent to Архива from the mail server
Execute the following Linux commands to check for SMTP traffic on the default port of 8091:sudo tcpdump -w smtp.dump -i lo port 8091 (loopback)
sudo tcpdump -w smtp.dump -i any port 8091 (any interface)
cat smtp.dump to see smtp traffic
Execute the following to determine whether there is any mail flowing on port 8091:sudo tcpdump -w milter.dump -i lo port 8092 (loopback)
sudo tcpdump -w milter.dump -i any port 8092 (any interface)
cat milter.dump to see milter traffic
Enable Troubleshoot Logging in Configuration->Logs enable Troubleshoot Logging. When a message appears in the log, debug statements will be outputted.
- In Configuration->Listeners, ensure there are no IP address restrictions defined. if so, delete them.
One or more of your disks has run out of space. Please check the disk space on all volume index and store locations, including appropriate paths listed in File System Layout. Refer to system requirements for information on how much disk space is needed and for guidance on how your disks should be partitioned.
Received OK, Yet No Archiving
If only blue bars appear in Status->Charts, emails are being received from the mail server, however cannot be archived and indexed. The unprocessed messages will reside in a local receive queue until the problem is resolved, whereupon the messages will be requeued for archiving.
Possible explanations for the server receiving mails, but not archiving are as follows:
- Misconfiguration - Archiving may not be occuring due to a simple misconfiguration or misunderstanding of the product.
- License Troubles - The server may stop archiving due to an invalid license (only applicable to v2)
- Operating System or File Permissions - If archiving to a remote storage device, the server may have insufficient permissions to write to it.
- Corrupted Audit Index - The audit index is corrupted. This can cause system instability and archiving may stop.
- Insufficient Amount of Memory Allocated - Insufficient memory is allocated to the server.
- Not Enough Disk Space Left - Insufficient disk space is remaining.
Server misconfigurations include:
- Encryption password not set.
Resolution: Set an encryption password in Volumes.
- There is no UNUSED/ACTIVE volume is configured. There must be at least one ACTIVE or UNUSED volume, in Configuration->Volumes.
Resolution: Define a new UNUSED volume in Volumes. - Insufficient permissions to write to the remote disk.
Resolution: Refer to Network Attached Storage for further instruction. - Invalid routes are specified in Configuration->Routes
Resolution: Delete/adjust routing configurations in Configuration->Routes (note: try deleting all routes, as the server will be default archive everything) - Unintended archive rules specified in Configuration->Archive Rules
Resolution: Ensure that the defined archive rules have the desired consequences and are specified correctly.
Note: If no routes are specified, the server will by default archive everything.
In Архива v2 (not Архива v3), archiving may stop due to an invalid license. A license may be invalid due to one of the following:
- Your mailbox limit has exceed the license quota. If this is the case, an appropriate alert will appear in Configuration->Alerts
Resolution: Upgrade your license by logging to the Архива website, select Licenses, choose License, click Extend, purchase, and install it in About.
- A corrupted index can lead to an invalid license. When MailArchiva conducts a license check, internally, it executes a search across all volumes. If an index is corrupt, the license check may fail.
Resolution: Reindex the troublesome volume index by clicking on reindex in Configuration->Volumes. - The license file has been accidentally modified during transit
Resolution: Obtain a new license file by logging into the Архива website and downloading your license.
Operating System & File Permissions
If archiving to a network attached storage device, Архива may not have sufficient privileges to write to the remote storage location.
- The Архива email archiving server is running under the USER account and not the ADMINISTRATOR account.
Resolution: Change the service account. - Write permissions are not enabled on the parent directory of the store
Resolution: You are sharing the store directory. Please share the parent directory of the store rather (Windows querk) - Архива is not running under an account with sufficient access rights.
Resolution: Please make sure the Архива service is running under an Administrator/root account - The email archive server does not have write access to the NAS or SAN disk
Resolution: The NAS or SAN disk is not connected or permissions are set incorrectly
Refer to Network Attached Storage for further instruction.
The server will stop archiving or will become unstable if the audit log is corrupted.
In the event that an audit log is corrupted, an alert may appear in Status->Alerts. Alternatively, indexing related errors as described below will appear in the debug.log file.
ERROR Jan/21 09:36:18 - failed to commit index:null
java.lang.NullPointerException
at com.stimulus.archiva.index.LuceneIndex.commit(LuceneIndex.java:259)
at com.stimulus.archiva.index.LuceneIndex$IndexCommit.run(LuceneIndex.java:277)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
java.lang.NullPointerException
at com.stimulus.archiva.index.LuceneIndex.commit(LuceneIndex.java:259)
at com.stimulus.archiva.index.LuceneIndex$IndexCommit.run(LuceneIndex.java:277)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
To resolve the audit corruption problem, simple reindex the audit log by clicking the Reindex button in Configuration->Logs. Once the reindexing process is complete, it is a good idea to restart the server.
The server operating environment may not meet the minimum requirements, or the server may be configured to use an unsufficient amount of memory. Refer to Out of Memory for possible resolutions.