Avamar PDM이 "Error while fetching tasks Failed with HTTP error code:404 additional information"과 함께 실패함 HTTP 상태 404 - 찾을 수 없음

Summary: 이 문서에서는 PDM(Proxy Deployment Manager) 오류 메시지를 해결하는 방법에 대해 설명합니다. "Error while fetching tasks. Failed with HTTP error code:404 additional information" HTTP Status 404 - Not Found

Symptoms

Cause

Resolution

Affected Products

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

PDM(Proxy Deployment Manager)을 사용하여 AUI(Avamar User Interface) 또는 Avamar Administrator 콘솔에서 권장 사항을 생성할 수 없음:

Cause

</pre><p><b>Root Cause</b></p><pre>com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.

RabbitMQ 인증 문제가 있습니다.

404 오류 코드는 다음에서 볼 수 있습니다. /usr/local/avamar/var/mc/server_log/mcserver.log.0 Avamar Administrator 콘솔에서 PDM을 사용하는 경우:

WARNING: Failed (https://localhost:8543/deploymanager/auth/login)(attempt 1 of 3): Failed with HTTP error code : 404
  additional information : <!doctype html><html lang="en"><head><title>HTTP Status 404 ▒~@~S Not Found</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 ▒~@~S Not Found</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> The requested resource [/deploymanager/auth/login] is not available</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat</h3></body></html>
08/25-16:53:06.00956 [MCS Counter monitor thread#168] com.avamar.mc.mon.MCSPerformanceMonitor.monitor
FINE: enter
08/25-16:53:06.00975 [RMI TCP Connection(122)-192.168.33.10#1523] com.avamar.mc.pdm.ProxyDeploymentManagerService.submitJsonWithRetry
WARNING: Failed (https://localhost:8543/deploymanager/auth/login)(attempt 2 of 3): Failed with HTTP error code : 404
  additional information : <!doctype html><html lang="en"><head><title>HTTP Status 404 ▒~@~S Not Found</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 ▒~@~S Not Found</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> The requested resource [/deploymanager/auth/login] is not available</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat</h3></body></html>
08/25-16:53:07.00035 [RMI TCP Connection(122)-192.168.33.10#1523] com.avamar.mc.pdm.ProxyDeploymentManagerService.submitJsonWithRetry
WARNING: Failed (https://localhost:8543/deploymanager/auth/login)(attempt 3 of 3): Failed with HTTP error code : 404
  additional information : <!doctype html><html lang="en"><head><title>HTTP Status 404 ▒~@~S Not Found</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 ▒~@~S Not Found</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> The requested resource [/deploymanager/auth/login] is not available</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat</h3></body></html>
08/25-16:53:07.00036 [RMI TCP Connection(122)-192.168.33.10#1523] com.avamar.mc.util.MCException.logException
WARNING: com.avamar.asn.service.ServiceException: Failed with HTTP error code : 404
  additional information : <!doctype html><html lang="en"><head><title>HTTP Status 404 ▒~@~S Not Found</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 ▒~@~S Not Found</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> The requested resource [/deploymanager/auth/login] is not available</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat</h3></body></html>
  at com.avamar.mc.pdm.ProxyDeploymentManagerService.login(ProxyDeploymentManagerService.java:577)
  at com.avamar.mc.pdm.ProxyDeploymentManagerService.getAllTasks(ProxyDeploymentManagerService.java:377)
  at sun.reflect.GeneratedMethodAccessor95.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  at java.lang.reflect.Method.invoke(Unknown Source)
  at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
  at org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:61)
  at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
  at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
  at com.sun.proxy.$Proxy96.getAllTasks(Unknown Source)
  at com.avamar.mc.pdm.ProxyDeploymentManagerServiceContext.getAllTasks(ProxyDeploymentManagerServiceContext.java:69)
  at sun.reflect.GeneratedMethodAccessor94.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  at java.lang.reflect.Method.invoke(Unknown Source)
  at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
  at sun.rmi.transport.Transport$1.run(Unknown Source)
  at sun.rmi.transport.Transport$1.run(Unknown Source)
  at java.security.AccessController.doPrivileged(Native Method)
  at sun.rmi.transport.Transport.serviceCall(Unknown Source)
  at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)

다음 엔드포인트에서 404 오류를 확인합니다.

admin@ave:/usr/local/avamar/var/mc/server_log/>: curl -kv https://localhost:8543/deploymanager/auth/login
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8543 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=CA; L=Irvine; OU=Dell EMC; O=Dell Technologies; CN=ave.lab
*  start date: Jul  1 12:02:13 2022 GMT
*  expire date: Jun 28 12:02:13 2032 GMT
*  issuer: C=US; ST=CA; L=Irvine; OU=Dell EMC; O=Dell Technologies; CN=ave.lab
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
> GET /deploymanager/auth/login HTTP/1.1
> Host: localhost:8543
> User-Agent: curl/7.60.0
> Accept: */*
>
< HTTP/1.1 404
< Content-Type: text/html;charset=utf-8
< Content-Language: en
< Content-Length: 776
< Date: Thu, 25 Aug 2022 14:54:36 GMT
< Connection: close
< Server: Avamar
<
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, Client hello (1):
<!doctype html><html lang="en"><head><title>HTTP Status 404 – Not Found</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404 – Not Found</h1><hr class="line" /><p><b>Type</b> Status Report</p><p><b>Message</b> The requested resource [/deploymanager/auth/login] is not available</p><p><b>Description</b> The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.</p><hr class="line" /><h3>Apache Tomcat</h3></body></html>

스냅샷 관리자 엔드포인트에 다음과 같은 예외 스택이 표시됩니다.

root@ave:/usr/local/avamar/var/mc/server_data/prefs/#: curl -kv https://localhost:8543/snapshotmanager/about
*   Trying ::1...
* TCP_NODELAY set
* Connected to localhost (::1) port 8543 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: C=US; ST=CA; L=Irvine; OU=Dell EMC; O=Dell Technologies; CN=ave.lab
*  start date: Jul  1 12:02:13 2022 GMT
*  expire date: Jun 28 12:02:13 2032 GMT
*  issuer: C=US; ST=CA; L=Irvine; OU=Dell EMC; O=Dell Technologies; CN=ave.lab
*  SSL certificate verify result: self signed certificate (18), continuing anyway.
> GET /snapshotmanager/about HTTP/1.1
> Host: localhost:8543
> User-Agent: curl/7.60.0
> Accept: */*
>
< HTTP/1.1 500
< Content-Type: text/html;charset=utf-8
< Content-Language: en
< Transfer-Encoding: chunked
< Date: Thu, 25 Aug 2022 15:04:43 GMT
< Connection: close
< Server: Avamar
<
<!doctype html><html lang="en"><head><title>HTTP Status 500 – Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:#525D76;} h1 {font-size:22px;} h2 {font-size:16px;} h3 {font-size:14px;} p {font-size:12px;} a {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 500 – Internal Server Error</h1><hr class="line" /><p><b>Type</b> Exception Report</p><p><b>Message</b> Servlet.init() for servlet [snapshotmanager] threw exception</p><p><b>Description</b> The server encountered an unexpected condition that prevented it from fulfilling the request.</p><p><b>Exception</b></p><pre>javax.servlet.ServletException: Servlet.init() for servlet [snapshotmanager] threw exception
        org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:543)
        org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:81)
    [...]
        java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        java.lang.Thread.run(Unknown Source)
</pre><p><b>Root Cause</b></p><pre>org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'snapshotManagerServerConfiguration': Unsatisfied dependency expressed through field 'snapshotRequestHandler'; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'snapshotHandler': Unsatisfied dependency expressed through field 'snapshotTemplate'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getRestTemplate' defined in com.emc.avamar.vmware.snapshot.config.server.SnapshotManagerServerConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.rabbit.core.RabbitTemplate]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'getRestTemplate' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'replySnapshotQueue' defined in com.emc.avamar.vmware.snapshot.config.server.SnapshotManagerServerConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.core.Queue]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'replySnapshotQueue' threw exception; nested exception is org.springframework.amqp.AmqpAuthenticationException: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
        org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:598)
        org.springframework.beans.factory.annotation.InjectionMetadata.inject(InjectionMetadata.java:90)
    [...]
        java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        java.lang.Thread.run(Unknown Source)
</pre><p><b>Root Cause</b></p><pre>org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'snapshotHandler': Unsatisfied dependency expressed through field 'snapshotTemplate'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getRestTemplate' defined in com.emc.avamar.vmware.snapshot.config.server.SnapshotManagerServerConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.rabbit.core.RabbitTemplate]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'getRestTemplate' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'replySnapshotQueue' defined in com.emc.avamar.vmware.snapshot.config.server.SnapshotManagerServerConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.core.Queue]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'replySnapshotQueue' threw exception; nested exception is org.springframework.amqp.AmqpAuthenticationException: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
        org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:598)
    [...]
        java.lang.Thread.run(Unknown Source)
</pre><p><b>Root Cause</b></p><pre>org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'getRestTemplate' defined in com.emc.avamar.vmware.snapshot.config.server.SnapshotManagerServerConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.rabbit.core.RabbitTemplate]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'getRestTemplate' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'replySnapshotQueue' defined in com.emc.avamar.vmware.snapshot.config.server.SnapshotManagerServerConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.core.Queue]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'replySnapshotQueue' threw exception; nested exception is org.springframework.amqp.AmqpAuthenticationException: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
        org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:627)
    [...]
        java.lang.Thread.run(Unknown Source)
</pre><p><b>Root Cause</b></p><pre>org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.rabbit.core.RabbitTemplate]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'getRestTemplate' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'replySnapshotQueue' defined in com.emc.avamar.vmware.snapshot.config.server.SnapshotManagerServerConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.core.Queue]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'replySnapshotQueue' threw exception; nested exception is org.springframework.amqp.AmqpAuthenticationException: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
        org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185)
    [...]
        java.lang.Thread.run(Unknown Source)
</pre><p><b>Root Cause</b></p><pre>org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'replySnapshotQueue' defined in com.emc.avamar.vmware.snapshot.config.server.SnapshotManagerServerConfiguration: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.core.Queue]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'replySnapshotQueue' threw exception; nested exception is org.springframework.amqp.AmqpAuthenticationException: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
        org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:627)
        org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:456)
    [...]
        java.lang.Thread.run(Unknown Source)
</pre><p><b>Root Cause</b></p><pre>org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.amqp.core.Queue]: Circular reference involving containing bean 'snapshotManagerServerConfiguration' - consider declaring the factory method as static for independence from its containing instance. Factory method 'replySnapshotQueue' threw exception; nested exception is org.springframework.amqp.AmqpAuthenticationException: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
        org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185)
    [...]
        java.lang.Thread.run(Unknown Source)
</pre><p><b>Root Cause</b></p><pre>org.springframework.amqp.AmqpAuthenticationException: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
        org.springframework.amqp.rabbit.support.RabbitExceptionTranslator.convertRabbitAccessException(RabbitExceptionTranslator.java:61)
    [...]
        org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        java.lang.Thread.run(Unknown Source)
</pre><p><b>Root Cause</b></p><pre>com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.
        com.rabbitmq.client.impl.AMQConnection.start(AMQConnection.java:339)
        com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:647)
        com.rabbitmq.client.ConnectionFactory.newConnection(ConnectionFactory.java:694)
    [...]
        java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
        java.lang.Thread.run(Unknown Source)
* Closing connection 0
* TLSv1.2 (OUT), TLS alert, Client hello (1):
</pre><p><b>Note</b> The full stack trace of the root cause is available in the server logs.</p><hr class="line" /><h3>Apache Tomcat</h3></body></html>

위의 출력에서 앞에서 언급한 다음 코드 조각을 수집합니다.

threw exception; nested exception is org.springframework.amqp.AmqpAuthenticationException: com.rabbitmq.client.AuthenticationFailureException: ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN. For details see the broker logfile.

Resolution

Avamar 버전 19.x 이상 버전의 경우:

백업 수행 mcserver.xml 에서 RabbitMQ 암호를 업데이트합니다. mcserver.xml 기본값으로 'Avamar_Rabbit' 을 클릭하고 파일을 편집합니다.

cp -p /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml /usr/local/avamar/var/mc/server_data/prefs/x-mcserver.xml

vi /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml

를 변경합니다. <entry key="rabbitmqAP" 기본 암호로 'Avamar_Rabbit'.

<entry key="rabbitmqAP" value="Avamar_Rabbit" />

관리 사용자로 MCS( Management Console Service )를 재시작합니다.

mcserver.sh --restart --force

를 다시 만듭니다. RabbitMQ User/Permissions/Password/vHost 역 root 사용자를 선택하고 다음 GoAV 명령을 사용하여 자동으로 수행합니다.

./goav rabbitmq reset

사용자에게 MCS 및 Tomcat 재시작을 승인하라는 메시지 표시
RabbitMQ 서비스를 중지합니다.
RabbitMQ 제거 mnesia 데이터베이스
RabbitMQ 서비스 시작
shovel 제거
메시지 브로커를 중지합니다
Avamar 및 게스트 RabbitMQ 사용자의 자격 증명을 업데이트합니다.
메시지 브로커 시작
Tomcat을 다시 시작합니다.
MCS 재시작

PDM 권장 사항을 테스트합니다.

Affected Products

Avamar

Article Number: 000203332

Article Type: Solution

Last Modified: 13 يناير 2026

Version: 9

Check if your device is covered by Support Services.

Avamar PDM이 "Error while fetching tasks Failed with HTTP error code:404 additional information"과 함께 실패함 HTTP 상태 404 - 찾을 수 없음

Summary: 이 문서에서는 PDM(Proxy Deployment Manager) 오류 메시지를 해결하는 방법에 대해 설명합니다. "Error while fetching tasks. Failed with HTTP error code:404 additional information" HTTP Status 404 - Not Found

Symptoms

Cause

Resolution

Affected Products

Symptoms

Cause

Resolution

Affected Products

Article Properties

Find answers to your questions from other Dell users

Support Services

Article Properties

Find answers to your questions from other Dell users

Support Services

Avamar PDM이 "Error while fetching tasks Failed with HTTP error code:404 additional information"과 함께 실패함 HTTP 상태 404 - 찾을 수 없음

Summary: 이 문서에서는 PDM(Proxy Deployment Manager) 오류 메시지를 해결하는 방법에 대해 설명합니다. "Error while fetching tasks. Failed with HTTP error code:404 additional information" HTTP Status 404 - Not Found

Detailed Article

Symptoms

Cause

Resolution

Affected Products

Symptoms

Cause

Resolution

Affected Products

Article Properties

Find answers to your questions from other Dell users

Support Services

Article Properties

Find answers to your questions from other Dell users

Support Services