Avamar: MCS nie uruchamia się, zgłaszając komunikat "Unable to connect to node rabbit@localhost: nodedown"
Summary: MCS nie uruchamia się, zgłaszając "unable to connect to node rabbit@localhost: nodedown".
Symptoms
Podczas ponownego uruchamiania usługi Management Console Service (MCS) rejestrowany jest komunikat o wyjątku: (/usr/local/avamar/var/mc/server_log/mcserver.log.0)
Caused by: org.springframework.amqp.AmqpConnectException: java.net.ConnectException: Connection refused
at org.springframework.amqp.rabbit.support.RabbitExceptionTranslator.convertRabbitAccessException(RabbitExceptionTranslator.java:51)
at org.springframework.amqp.rabbit.connection.AbstractConnectionFactory.createBareConnection(AbstractConnectionFactory.java:185)
at org.springframework.amqp.rabbit.connection.CachingConnectionFactory.createConnection(CachingConnectionFactory.java:228)
at org.springframework.amqp.rabbit.connection.ConnectionFactoryUtils$1.createConnection(ConnectionFactoryUtils.java:77)
at org.springframework.amqp.rabbit.connection.ConnectionFactoryUtils.doGetTransactionalResourceHolder(ConnectionFactoryUtils.java:125)
at org.springframework.amqp.rabbit.connection.ConnectionFactoryUtils.getTransactionalResourceHolder(ConnectionFactoryUtils.java:67)
at org.springframework.amqp.rabbit.connection.RabbitAccessor.getTransactionalResourceHolder(RabbitAccessor.java:102)
at org.springframework.amqp.rabbit.core.RabbitTemplate.execute(RabbitTemplate.java:618)
at org.springframework.amqp.rabbit.core.RabbitAdmin.declareQueue(RabbitAdmin.java:133)
at com.avamar.mc.jms.push.JmsPushService.enable(JmsPushService.java:418)
at com.avamar.mc.jms.push.JmsPushService.start(JmsPushService.java:191)
at com.avamar.asn.service.ServiceContainerImpl.installService(ServiceContainerImpl.java:472)
... 6 more
Polecenie Rabbimq Stan zgłasza błąd: Unable to connect to node rabbit@localhost: nodedown
service rabbitmq-server status
Status of node rabbit@localhost ...
Error: unable to connect to node rabbit@localhost: nodedown
Program Backup and Recovery Manager (BRM) jest włączony:
grep Brm /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml
<entry key="enableBrmService" value="true" /> Cause
Przyczyna jest nieznana, jednak poniżej przedstawiono potencjalne obejście problemu.
Resolution
1. Zaloguj się do węzła Avamar Utility Node jako „admin”.
2. Podnieś poziom uprawnień do uprawnień root.
3. Zmień nazwę pliku binarnego /usr/local/avamar/var/rabbitmq/mnesia katalog:
mv /usr/local/avamar/var/rabbitmq/mnesia /usr/local/avamar/var/rabbitmq/mnesia.`date +%y%m%d`
4. Ponowne uruchomienie rabbitmq:
service rabbitmq-server start
5. Sprawdź, czy /usr/local/avamar/var/rabbitmq/mnesia katalog istnieje:
ls -ld /usr/local/avamar/var/rabbitmq/mnesia*
Przykładowe dane wyjściowe:
drwxr-x--- 4 rabbitmq rabbitmq 97 Jul 21 19:46 /usr/local/avamar/var/rabbitmq/mnesia
drwxr-xr-x 4 rabbitmq rabbitmq 97 Jan 22 16:30 /usr/local/avamar/var/rabbitmq/mnesia.250721
6. Uruchom ponownie MCS na Avamar: Ponowne uruchamianie serwera konsoli zarządzającej.