Troubleshooting Replicas in SynetoOS 5

Written By Christian Castagna (Administrator)

Updated at October 21st, 2025

Table of Contents

Identify Queued Replicas Kill Queued Replicas Identify Running Replicas Stop Running Replicas Start Replicas

→ Applies to: SynetoOS 5.x

All commands in this article are intended to be executed via SynetoOS CLI.

Step 1. Connect to SynetoOS appliance via SSH as admin

ssh admin@<your_ip_address_or_hostname>

Step 2. Become Super User

sudo su

Identify Queued Replicas

List all queues (excluding those with a count of 0):

kubectl exec -it pods/rabbitmq-0 -- rabbitmqctl list_queues | grep -v -P ".*\t0" | sort

Kill Queued Replicas

Delete an entire queue (replace <queue_name> with the correct information):

kubectl exec -it pods/rabbitmq-0 -- rabbitmqctl delete_queue <queue_name>

Examples of queues are volume_start_replication, etc.

Restart the SynetoOS 5 service (syneto-giove) to ensure the changes take effect

systemctl restart syneto-giove

Identify Running Replicas

List all running replicas:

syneto-giove-cli.sh show | grep repl

List details of all running replicas (database query):

echo "select * from jobs where status in ('RUNNING');" | kubectl exec -i pods/postgres-postgresql-0 -- bash -c 'PGPASSWORD=$POSTGRES_PASSWORD psql -d chronos --user postgres'

Stop Running Replicas

Stop a specific replica (replace <job_id> with your replica job ID identified through the detailed lists):

syneto-giove-cli.sh stop <job_id>

EXAMPLE

syneto-giove-cli.sh stop 8256b248-1f90-4462-98f3-ca51bdb8b143

Start Replicas

Start a specific replica (replace <vm_name> with the correct name of the virtual machine):

syneto-giove-cli.sh start <vm_name>