Data Protection Central: RabbitMQ starter ikke

Summary: Denne artikel indeholder en procedure for Data Protection Central (DPC), når RabbitMQ ikke starter efter en softwareopdatering.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Når RabbitMQ ikke starter efter en DPC-softwareopdatering, viser status tjenesten RabbitMQ (rabbitmq-server) aktiveres, men fuldføres aldrig: 
# /usr/local/dpc/bin/dpc status
Version: 19.9.0-13
msm-ui-main: active
msm-monitor: inactive
msm-elg: active
mongod: active
rabbitmq-server: activating
nginx: active
dp-iam: active
FIPS: disabled
#
RabbitMQ-loggen viser fejl, når du åbner meddelelseslageret under opstart. For eksempel i /var/log/dpc/rabbitmq/rabbit@<DPC Hostname>.log, viser det, at RabbitMQ fejler, når man forsøger at genopbygge indekset: 
2024-05-07 23:56:25.408992-04:00 [info] <0.230.0> Running boot step recovery defined by app rabbit
2024-05-07 23:56:25.410137-04:00 [info] <0.423.0> Making sure data directory '/var/lib/dpc/rabbitmq/mnesia/rabbit@<DPC Hostname>/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L' for vhost '/' exists
2024-05-07 23:56:25.412199-04:00 [info] <0.423.0> Starting message stores for vhost '/'
2024-05-07 23:56:25.412425-04:00 [info] <0.428.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_transient": using rabbit_msg_store_ets_index to provide index
2024-05-07 23:56:25.413720-04:00 [info] <0.423.0> Started message store of type transient for vhost '/'
2024-05-07 23:56:25.413970-04:00 [info] <0.432.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": using rabbit_msg_store_ets_index to provide index
2024-05-07 23:56:25.414552-04:00 [warning] <0.432.0> Message store "628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent": rebuilding indices from scratch
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0> ** Generic server <0.369.0> terminating
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0> ** Last message in was {'$gen_cast',
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0>                            {submit_async,
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0>                                #Fun<rabbit_classic_queue_index_v2.11.72031207>,
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0>                                <0.367.0>}}
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0> ** When Server state == undefined
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0> ** Reason for termination ==
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0> ** {function_clause,
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0>        [{rabbit_queue_index,journal_minus_segment1,
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0>             [{no_pub,no_del,ack},
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0>              {{true,
2024-05-07 23:56:25.495894-04:00 [error] <0.369.0>                   <<136,59,154,30,244,191,111,192,154,235,124,189,92,104,1,207,

Cause

RabbitMQ starter ikke på grund af en stor mængde fastlåste meddelelser i køen.

I dette eksempel er der over 800 MB data i køen: 
<DPC Hostname>:/var/lib/dpc/rabbitmq/mnesia # du -h .
20K     ./rabbit@<DPC Hostname>/quorum/rabbit@<DPC Hostname>
20K     ./rabbit@<DPC Hostname>/quorum
58M     ./rabbit@<DPC Hostname>/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/msg_store_persistent
824M    ./rabbit@<DPC Hostname>/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/queues/BV3H25N6AGWF7TDIN2L5RE0DA
824M    ./rabbit@<DPC Hostname>/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/queues
0       ./rabbit@<DPC Hostname>/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L/msg_store_transient
881M    ./rabbit@<DPC Hostname>/msg_stores/vhosts/628WB79CIFDYO9LJI6DKMI09L
881M    ./rabbit@<DPC Hostname>/msg_stores/vhosts
881M    ./rabbit@<DPC Hostname>/msg_stores
20K     ./rabbit@<DPC Hostname>/coordination/rabbit@<DPC Hostname>
20K     ./rabbit@<DPC Hostname>/coordination
881M    ./rabbit@<DPC Hostname>
0       ./rabbit@<DPC Hostname>-plugins-expand
881M    .
<DPC Hostname>:/var/lib/dpc/rabbitmq/mnesia #

Resolution

Du kan løse problemet ved at bruge nedenstående procedure til at genopbygge RabbitMQ-ressourcerne:
  1. Tag et snapshot af den virtuelle DPC-maskine, eller udfør en fuld sikkerhedskopiering af DPC-serveren.
  2. SSH til DPC og log ind som "admin", og skift derefter brugeren til root:
su -
  1. Stop RabbitMQ-tjenesten (rabbitmq-server) med følgende kommando:
service rabbitmq-server stop
  1. Skift mappen til /var/lib/dpc/rabbitmq/mnesia:
cd  /var/lib/dpc/rabbitmq/mnesia
  1. Hvis der er nok ledig plads i /tmp, kopiere dataene til /tmp (valgfrit):
cp -rp * /tmp
  1. Fjern dataene under /var/lib/dpc/rabbitmq/mnesia med følgende kommando:
rm -rf *
  1. Genstart RabbitMQ-tjenesten, filer under /var/lib/dpc/rabbitmq/mnesia bør regenereres:
service rabbitmq-server start
  1. Genstart DPC-tjenesterne:
/usr/local/dpc/bin/dpc restart

Et eksempel på output fra et laboratoriemiljø:
eksempel, der viser RabbitMQ, der regenererer datastrukturen
Figur 1: Et eksempel, der viser RabbitMQ, der regenererer datastrukturen under /var/lib/dpc/rabbitmq/mnesia Under opstart
  1. Log på DPC-brugergrænsefladen for at kontrollere, om DPC'en fungerer som forventet.
  2. Slet de undermapper, der tidligere er flyttet til /tmp hvis data er blevet kopieret i trin 5. 
  3. Når servicen vender tilbage til normal, skal du slette snapshottet af den virtuelle DPC-maskine , hvis det blev taget. 
 

Affected Products

Data Protection Central, PowerProtect DP4400, PowerProtect DP5300, PowerProtect DP5800, PowerProtect DP8300, PowerProtect DP8800, PowerProtect Data Protection Software, Integrated Data Protection Appliance Family , Integrated Data Protection Appliance Software, PowerProtect DP5900, PowerProtect DP8400, PowerProtect DP8900 ...
Article Properties
Article Number: 000225640
Article Type: Solution
Last Modified: 27 Jun 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.