×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

This documentation supports the 21.05 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

AR System 21.05 ... Troubleshooting Troubleshooting Approval Server

Troubleshooting when approvals are not processed or other unexpected behaviors occur

Best practice

When approvals are not processed as expected, we recommend that you first restore Approval Server by restarting it.
 This topic describes how to restart Approval Server  without restarting Action Request System .

Symptoms

You notice that approvals are not processed or you encounter any other unexpected behaviors.

Scope

  • One or more users might experience the symptoms.
  • In a Server Group environment, the symptoms can affect one or more servers.

Resolution

When approvals are not processed or you notice other unexpected behaviors, perform the following steps to troubleshoot the issue:

StepTaskDescription
1.

Connect to Approval Server .

Use a Remote Desktop Protocol (RDP) client or a Secure Socket Shell (SSH) client to connect to Approval Server .

2.

Determine on which AR System Plug-in Server the Approval Server plug-in is running.

  1. In the ar.cfg file or on the Centralized Configuration form, search for the ARSYS.ARDBC.PREVIEW plug-in alias for AR System server .

  2. Check the <Server Name>:<Port> with which the plug-in alias is associated. In the following example, REM01 is the name of AR System server and 9999 is the port number.

    Server-Plugin-Alias: ARSYS.ARDBC.PREVIEW ARSYS.ARDBC.PREVIEW REM01:9999

    The preceding example indicates that the plug-in server is running on port 9999 on AR System server REM01. Port 9999 indicates that the Approval Server plug-in is running on the default Java Plug-in Server of AR System .

3.Determine the process ID (PID) that is assigned to the plug-in server.

Check the armonitor.log file to determine which PID is assigned to the plug-in server. We recommend that you start checking from the bottom of the log file where the most recent entries are displayed and move up until you see the most recent process name that matches the plug-in server.

For example, the following image shows the process name that matches the plug-in server:


4.

End the task or kill the task.
  1. Perform one of the following steps:
      • (Windows) Open Task Manager.
      • (Linux) Check the PID by running the pgrep command-line utility.

  2. Perform one of the following steps:
      • (Windows) Click End Task.
      • (Linux) Use the kill command.

The following image shows the highlighted process ID in Task Manager:


5.Restart the plug-in server by using the AR Monitor process.

The AR Monitor process should begin the restarting process for the plug-in server almost instantly. If successful, this process is assigned a new PID. If the process does not restart automatically, check the armonitor.log file and the plug-in server logs for errors and troubleshoot further.

6.

Restart AR System server .

In some scenarios, you cannot restart only the plug-in server that is running Approval Server without restarting AR System server . In such a case, you must restart the AR System server process to resolve the issue that is affecting the approval process.

Related topic

Contacting Support

Was this page helpful? Yes No Submitting... Thank you
Last modified by Anagha Deshpande on May 02, 2022
troubleshooting approvals_not_processed non_expected_behavior best_practices

Comments

Log in or register to comment.

Runtime issues
Troubleshooting Assignment Engine
© Copyright 1991-2021 BMC Software, Inc. © Copyright 1991-2021 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.