DPSearch: Die Avamar-Quelle bleibt im Status "Disconnected", nachdem sie der Suche hinzugefügt wurde

Zusammenfassung: Die Avamar-Quelle verbleibt im Status "Disconnected", nachdem sie der Suche hinzugefügt wurde.

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

Nach der Bereitstellung von DPSearch und dem Hinzufügen einer Avamar-Quelle zu DPSearch bleibt es im Status "getrennt". Das Reparieren des Agenten über die Search Console hilft nicht.
In den search-avamar-action-AvamarSourceName.log Protokollen können wir Folgendes sehen:       

8|P 1|T [qtp688581408-21]|2021-05-25 13:06:15,581|Avamar::logon|ERROR|Failed to log in Avamar server "Avamar Source" with error "Connection or outbound has closed" org.apache.axis2.AxisFault: Connection or outbound has closed
    at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
    at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:83)
    at org.apache.axis2.transport.http.AxisRequestEntity.writeRequest(AxisRequestEntity.java:84)
    at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:499)
    at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114)
    at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
    at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
    at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
    at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:346)
    at org.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:557)
    at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:199)
    at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)
    at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:400)
    at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:225)
    at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:438)
    at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:402)
    at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
    at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
    at com.avamar.mc.sdk10.Mcsdk10Stub.login(Mcsdk10Stub.java:28944)
    at com.avamar.mc.sdk10.client.McSdkClient.connect(McSdkClient.java:70)
    at com.avamar.mc.sdk10.client.McSdkClient.connect(McSdkClient.java:64)
    at com.emc.zinc.avamar.Avamar.logon(Avamar.java:3592)
    at com.emc.zinc.avamar.AvamarConnector.logOn(AvamarConnector.java:41)
    at com.emc.zinc.dpsearch.action.ConnectionHelper.connect(ConnectionHelper.java:39)
    at com.emc.zinc.dpsearch.action.ConnectionHelper.connectSource(ConnectionHelper.java:64)
    at com.emc.zinc.avamar.action.AdminActionResource.performAction(AdminActionResource.java:49)
    at com.emc.zinc.avamar.action.AdminActionResource.connectToSource(AdminActionResource.java:63)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
    at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:144)
    at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:161)
    at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$ResponseOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:160)
    at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:99)
    at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:389)
    at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:347)
    at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:102)
    at org.glassfish.jersey.server.ServerRuntime$2.run(ServerRuntime.java:326)
    at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
    at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
    at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
    at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:317)
    at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:305)
    at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1154)
    at org.glassfish.jersey.jetty.JettyHttpContainer.handle(JettyHttpContainer.java:195)
    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:96)
    at org.eclipse.jetty.server.Server.handle(Server.java:498)
    at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:310)
    at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:258)
    at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
    at java.lang.Thread.run(Unknown Source)
Caused by: com.ctc.wstx.exc.WstxIOException: Connection or outbound has closed
    at com.ctc.wstx.sw.BaseStreamWriter._finishDocument(BaseStreamWriter.java:1421)
    at com.ctc.wstx.sw.BaseStreamWriter.close(BaseStreamWriter.java:241)
    at org.apache.axiom.util.stax.wrapper.XMLStreamWriterWrapper.close(XMLStreamWriterWrapper.java:46)
    at org.apache.axiom.om.impl.MTOMXMLStreamWriter.close(MTOMXMLStreamWriter.java:188)
    at org.apache.axiom.om.impl.llom.OMSerializableImpl.serializeAndConsume(OMSerializableImpl.java:197)
    at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:79)
    ... 56 more
Caused by: java.net.SocketException: Connection or outbound has closed
    at sun.security.ssl.SSLSocketImpl$AppOutputStream.write(Unknown Source)
    at java.io.BufferedOutputStream.flushBuffer(Unknown Source)
    at java.io.BufferedOutputStream.flush(Unknown Source)
    at org.apache.commons.httpclient.ChunkedOutputStream.flush(ChunkedOutputStream.java:191)
    at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:103)
    at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:241)
    at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:214)
    at com.ctc.wstx.sw.BaseStreamWriter._finishDocument(BaseStreamWriter.java:1419)
    ... 61 more
|Avamar.java(3623)|

Ursache

Die Verbindung zwischen DPSearch und Avamar schlägt fehl. DPSearch kann keine Verbindung zum Avamar-Server herstellen, der genaue Grund dafür ist jedoch unbekannt.

Lösung

Um dieses Verhalten zu beheben, starten Sie die DPSearch Avamar-Services auf allen Nodes neu:      
 

service search-avamar-action stop
service search-avamar-worker stop
service search-avamar-action start
service search-avamar-worker start


Wenn die Avamar -Quelle weiterhin getrennt ist, geben Sie das Avamar -Kennwort aus der Quellenkonfiguration in der DPSearch Administration Webnutzeroberfläche ein. Starten Sie den Service erneut oder wenden Sie sich an den Support, um weitere Unterstützung zu erhalten.

Betroffene Produkte

Data Protection Search
Artikeleigenschaften
Artikelnummer: 000187721
Artikeltyp: Solution
Zuletzt geändert: 23 März 2026
Version:  2
Antworten auf Ihre Fragen erhalten Sie von anderen Dell NutzerInnen
Support Services
Prüfen Sie, ob Ihr Gerät durch Support Services abgedeckt ist.