---
title: "Messaging Service Errors"
slug: "messaging-service-errors-3-1-1"
tags: ["Portal"]
updated: 2026-11-09T08:37:16Z
published: 2026-11-09T08:37:16Z
canonical: "kb.ctera.com/messaging-service-errors-3-1-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.ctera.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Messaging Service Errors

**Note**

The status in the **Messaging** page changes to an error if all the messaging servers are down but only to a warning if at least one messaging server is still running.

Problems with the CTERA Messaging Service are displayed, with the reason, either as part of the status bar message or the **Messaging Service Status** column.

The banner can also provide information. For example, when there is not enough available storage on the messaging server the banner status is **READ-ONLY MODE** instead of **ERROR**.

When more than one messaging server is deployed, high availability (HA) is employed. As long as the status one of them is **ACTIVE**, the CTERA Messaging Service continues to function properly.

## CTERA Messaging Service Logs

All CTERA services that require the CTERA Messaging service, for example the Varonis log, write to the same volume. In order that the logs do not grow too large, which can cause storage issues, you can set how long messages in the logs are retained.