NetWorker: Datos no disponibles debido a problemas de RabbitMQ en Windows Backup Server
Zusammenfassung: Datos no disponibles debido a problemas de rabbitMQ en el servidor de respaldo.
Dieser Artikel gilt für
Dieser Artikel gilt nicht für
Dieser Artikel ist nicht an ein bestimmtes Produkt gebunden.
In diesem Artikel werden nicht alle Produktversionen aufgeführt.
Symptome
- El software del servidor NetWorker se instala en un servidor Microsoft Windows.
- Después de una actualización reciente del servidor de NetWorker, se inician los servicios; sin embargo, nsrwatch y NetWorker Management Console (NMC) no muestran respaldos y los respaldos que se inician manualmente fallan.
- La ventana de alertas de NMC y el informe nmC gstd.raw:
Linux: /opt/lgtonmc/logs/gstd.raw Windows: C:\Program Files\EMC NetWorker\Management\GST\logs\gstd.raw ERROR generated: "Message bus unable to open socket connection to host 'BACKUP-SRV' on port 5672: a socket error occurred" in file "D:/views/nw/19.8/nsrwebui/modules/nsm/gstnsm.c" line #11364
NetWorker: Cómo utilizar nsr_render_log
- El puerto 5672 o 5671 no escucha en el servidor de NetWorker:
nsrports -t localhost -p PORT netstat -ano | findstr PORT
NOTA: El puerto 5672 es el puerto no SSL heredado. El puerto 5671 se utiliza para SSL. En NetWorker 19.7.x y versiones posteriores, el puerto 5672 está deshabilitado y el tráfico de rabbitmq se envía a través del puerto 5671.
- Ejecutó el comando para iniciar el servidor rabbitmq y esta fue la salida:
Configuring logger redirection
Logger - error: {removed_failing_handler,rabbit_log}
13:46:52.589 [error] Error in process <0.206.0> on node rabbit_prelaunch_3804@localhost with exit value:
{eacces,[{erlang,open_port,[{spawn,"inet_gethost 4 "},[{packet,4},eof,binary]],[{file,"erlang.erl"},{line,2258}]},{inet_gethost_native,server_init,2,[{file,"inet_gethost_native.erl"},{line,184}]}]}
13:46:52.589 [error] Supervisor inet_gethost_native_sup had child at module inet_gethost_native at <0.206.0> exit with reason {eacces,[{erlang,open_port,[{spawn,"inet_gethost 4 "},[{packet,4},eof,binary]],[{file,"erlang.erl"},{line,2258}]},{inet_gethost_native,server_init,2,[{file,"inet_gethost_native.erl"},{line,184}]}]} in context child_terminated
13:46:52.589 [error] gen_server inet_gethost_native_sup terminated with reason: {eacces,[{erlang,open_port,[{spawn,"inet_gethost 4 "},[{packet,4},eof,binary]],[{file,"erlang.erl"},{line,2258}]},{inet_gethost_native,server_init,2,[{file,"inet_gethost_native.erl"},{line,184}]}]}
13:46:52.589 [error] CRASH REPORT Process inet_gethost_native_sup with 0 neighbours exited with reason: {eacces,[{erlang,open_port,[{spawn,"inet_gethost 4 "},[{packet,4},eof,binary]],[{file,"erlang.erl"},{line,2258}]},{inet_gethost_native,server_init,2,[{file,"inet_gethost_native.erl"},{line,184}]}]} in gen_server:handle_common_reply/8 line 805
13:46:52.589 [error] Supervisor kernel_safe_sup had child inet_gethost_native_sup started with {inet_gethost_native,start_link,undefined} at <0.205.0> exit with reason {eacces,[{erlang,open_port,[{spawn,"inet_gethost 4 "},[{packet,4},eof,binary]],[{file,"erlang.erl"},{line,2258}]},{inet_gethost_native,server_init,2,[{file,"inet_gethost_native.erl"},{line,184}]}]} in context child_terminated
13:46:52.605 [error] Error in process <0.206.0> on node rabbit_prelaunch_3804@localhost with exit value:
{eacces,[{erlang,open_port,[{spawn,"inet_gethost 4 "},[{packet,4},eof,binary]],[{file,"erlang.erl"},{line,2258}]},{inet_gethost_native,server_init,2,[{file,"inet_gethost_native.erl"},{line,184}]}]}
13:46:52.636 [error]
13:46:52.636 [error] BOOT FAILED
BOOT FAILED
13:46:52.636 [error] ===========
===========
13:46:52.636 [error] ERROR: epmd error for host BACKUP-SRV: {could_not_start_server,inet_gethost_native} (unknown POSIX error)
ERROR: epmd error for host BACKUP-SRV: {could_not_start_server,inet_gethost_native} (unknown POSIX error)
13:46:52.636 [error]
13:46:53.647 [error] Supervisor rabbit_prelaunch_sup had child prelaunch started with rabbit_prelaunch:run_prelaunch_first_phase() at undefined exit with reason {epmd_error,"BACKUP-SRV",{could_not_start_server,inet_gethost_native}} in context start_error
13:46:53.647 [error] CRASH REPORT Process <0.151.0> with 0 neighbours exited with reason: {{shutdown,{failed_to_start_child,prelaunch,{epmd_error,"BACKUP-SRV",{could_not_start_server,inet_gethost_native}}}},{rabbit_prelaunch_app,start,[normal,[]]}} in application_master:init/4 line 138
{"Kernel pid terminated",application_controller,"{application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{epmd_error,\"BACKUP-SRV\",{could_not_start_server,inet_gethost_native}}}},{rabbit_prelaunch_app,start,[normal,[]]}}}"}
Kernel pid terminated (application_controller) ({application_start_failure,rabbitmq_prelaunch,{{shutdown,{failed_to_start_child,prelaunch,{epmd_error,"BACKUP-SRV",{could_not_start_server,inet_gethost
Crash dump is being written to: erl_crash.dump...doneUrsache
Este problema puede ocurrir cuando existe un archivo o directorio no autorizado denominado "programa" en la raíz del volumen donde está instalado NetWorker. Este archivo o directorio puede estar oculto.
Lösung
Identifique si existe un archivo o directorio denominado "programa" en la raíz de cualquier volumen. Si es así, elimine o cambie el nombre del archivo o directorio:
- Abra un símbolo del sistema mediante Ejecutar como administrador.
- Vaya a la raíz del volumen.
Ejemplo:
cd D:\
- Ejecute el siguiente comando para mostrar objetos, incluidos los objetos ocultos.
dir /a
- Si se encuentra un "Programa", elimine o cambie el nombre del objeto.
- Repita los pasos del 1 al 4 para cualquier otro volumen o letra de unidad.
- Reinicie el servicio:
net stop nsrexecd /y net start nsrd
Si NMC está instalado en el mismo sistema:
net start gstd
- Reinicie el host en la siguiente oportunidad.
Betroffene Produkte
Data Protection, NetWorker Family, NetWorker, NetWorker Management ConsoleProdukte
NetWorker Management ConsoleArtikeleigenschaften
Artikelnummer: 000220828
Artikeltyp: Solution
Zuletzt geändert: 09 Okt. 2024
Version: 3
Antworten auf Ihre Fragen erhalten Sie von anderen Dell NutzerInnen
Support Services
Prüfen Sie, ob Ihr Gerät durch Support Services abgedeckt ist.