---
title: Resolving multiple active administrative nodes
description: Follow these steps to fix your cluster if multiple administrative consoles are active.
component: pingfederate
version: 13.0
page_id: pingfederate:server_clustering_guide:pf_resolving_multiple_active_admin_nodes
canonical_url: https://docs.pingidentity.com/pingfederate/13.0/server_clustering_guide/pf_resolving_multiple_active_admin_nodes.html
revdate: July 15, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Resolving multiple active administrative nodes

Follow these steps to fix your cluster if multiple administrative consoles are active.

## About this task

In rare situations, usually when the active/passive admin console feature is misconfigured, multiple consoles on a cluster can be active. PingFederate usually resolves this conflict automatically by determining which active console was most recently made active. When this is not possible, it can result in multiple active consoles.

This is an improper cluster state that you must resolve. While multiple consoles are active, PingFederate cannot determine from which active console to pull synchronization data.

## Steps

1. Check the configuration of your consoles to determine which should remain active.

2. Do the following with the consoles that you want to make passive:

   1. Manually shut down the console.

   2. Delete the `admin-node-mode.xml` file.

   3. Restart the inactive console.

3. Go to **System > Server > Cluster Management** to make sure that passive consoles are synchronizing only with the remaining active console.

   Learn more in [Monitoring active and passive administrative nodes](pf_monitoring_active_passive_admin_nodes.html).