Remedy AR System Server is not responding and encountering timeout errors ARERR 93 for different processes

Knowledge Article

Article Number

000332236

Old Article Number

000131601

Article Type

Solutions to a Product Problem

Title

Remedy AR System Server is not responding and encountering timeout errors ARERR 93 for different processes

Summary

Server not responding and processing very slowly.

Product

Remedy AR System Server

Component

AR System

Applies to

Remedy AR System Server v.9.x

Problem

The AR Server is not responding or responds very slow encountering many time out errors in the arerror.log:
........................
Mon Jul 24 12:59:17 2017 Dispatch : Timeout during data retrieval due to busy server -- retry the operation (arserver_name) ARERR - 93
Mon Jul 24 13:03:55 2017 SLMCS : Timeout during data retrieval due to busy server -- retry the operation (arserver_name) ARERR - 93
Mon Jul 24 13:03:55 2017 BRIE : Timeout during data retrieval due to busy server -- retry the operation (arserver_name) ARERR - 93
Mon Jul 24 13:04:55 2017 Dispatch : Timeout during data retrieval due to busy server -- retry the operation (arserver_name) ARERR - 93
Mon Jul 24 13:07:04 2017 CMDB Dispatcher : Timeout during data retrieval due to busy server -- retry the operation (arserver_name) ARERR - 93
........................

Other symptoms are:
- Server showing very little CPU utilization.
- Emails and notifications not processing.
- Records accumulating in forms such as NTE:SYS-NT Process Conrol, Email Messages, etc..
- Server restart very slow.

NOTE: This article is also available in Spanish, use the link below or search by Article Number 000160930. / NOTA: Este artículo también está disponible en Español, usar el siguiente enlace o buscar por el Número de Artículo 000160930.
Remedy - Server - AR Server no responde y se presentan errores de timeout ARERR 93 para diferentes procesos

Cause

The ar.cfg/ar.conf was modified and thread entries were removed.

Solution

This knowledge article may contain information that does not apply to version 21.05 or later which runs in a container environment. Please refer to Article Number 000385088 for more information about troubleshooting BMC products in containers.

Check the ar.cfg/ ar.conf to ensure Private RPC Socket entries are not missing.

Example of "normal" queues found in the configuration file:
.........................
Private-RPC-Socket: 390601   1   1
Private-RPC-Socket: 390603   1   1
Private-RPC-Socket: 390620   2 12
Private-RPC-Socket: 390621   5 16
Private-RPC-Socket: 390622   4   6
Private-RPC-Socket: 390623   4   6
Private-RPC-Socket: 390624   4   6
Private-RPC-Socket: 390625   4   6
Private-RPC-Socket: 390626   2   6
Private-RPC-Socket: 390627   4   6
Private-RPC-Socket: 390628   4   6
Private-RPC-Socket: 390635   2   8
Private-RPC-Socket: 390680   2   2
Private-RPC-Socket: 390698   2   8
.........................

Other additional information which can be checked is the following article:
REMEDY 9.x Release - CONFIGURATION CHECKLIST from the BMC R&D PERFORMANCE TEAM

Attachment(s):