Skip to main content
NetApp Stage KB

AIQUM Service failed to start due to "Invalid record type" error in server log file

Views:
Visibility:
Public
Votes:
0
Category:
active-iq-unified-manager
Specialty:
OM
Last Updated:

Applies to

  • Active IQ Unified Manager (AIQUM) 9.9P1
  • Below steps are for AIQUM installed on Linux. Similar steps can be followed for Windows OS

Issue

  • NetApp Active IQ Acquisition Service is stopped after starting
  • server.log shows java.lang.IllegalStateException with Invalid record type

ERROR [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ224000: Failure in initialisation: java.lang.IllegalStateException: Invalid record type 13
    at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.loadMessageJournal(AbstractJournalStorageManager.java:1173) [artemis-server-2.10.1.jar:2.10.1]
    at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.loadJournals(ActiveMQServerImpl.java:3194) [artemis-server-2.10.1.jar:2.10.1]
    at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart2(ActiveMQServerImpl.java:2872) [artemis-server-2.10.1.jar:2.10.1]
    at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:72) [artemis-server-2.10.1.jar:2.10.1]
    at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:600) [artemis-server-2.10.1.jar:2.10.1]
    at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:527) [artemis-server-2.10.1.jar:2.10.1]
    at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:373) [artemis-jms-server-2.10.1.jar:2.10.1]
    at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:211) [wildfly-messaging-activemq-19.0.0.Final.jar:19.0.0.Final]
    at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65) [wildfly-messaging-activemq-19.0.0.Final.jar:19.0.0.Final]
    at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100) [wildfly-messaging-activemq-19.0.0.Final.jar:19.0.0.Final]

  • au.log shows Failed to start acquisition after repeating java.net.ConnectException

INFO  [WrapperStartStopAppMain] c.o.s.a.f.m.CommunicationManager (CommunicationManager.java:422) - java security noSuchAlgorithm exception for https://localhost:443 java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.connect0(Native Method) ~[?:?]
    at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:101) ~[?:?]
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:399) ~[?:?]
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:242) ~[?:?]
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:224) ~[?:?]
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) ~[?:?]
    at java.net.Socket.connect(Socket.java:609) ~[?:?]
    at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:299) ~[?:?]
    at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) ~[?:?]
    at sun.net.NetworkClient.doConnect(NetworkClient.java:182) ~[?:?]
..
ERROR [WrapperStartStopAppMain] c.o.s.a.f.Main (Main.java:71) - Main - failed to start services: Failed to start acquisition - server not deployed; gave up after 3600 seconds com.onaro.sanscreen.server.sessions.SummaryException:  - Failed to get Summary SessionServer returned HTTP status 404.
    at com.onaro.sanscreen.acquisition.framework.mgmt.CommunicationManager.getSummarySessionFromREST(CommunicationManager.java:562) ~[au-framework.jar:9.9.0-2021.08.J1133]
    at com.onaro.sanscreen.acquisition.framework.mgmt.CommunicationManager.waitForServerToFullyDeployed(CommunicationManager.java:450) ~[au-framework.jar:9.9.0-2021.08.J1133]
    at com.onaro.sanscreen.acquisition.framework.mgmt.CommunicationManager.doStart(CommunicationManager.java:144) ~[au-framework.jar:9.9.0-2021.08.J1133]
    at com.onaro.sanscreen.acquisition.framework.mgmt.FrameworkService.start(FrameworkService.java:75) ~[au-framework.jar:9.9.0-2021.08.J1133]
    at com.onaro.sanscreen.acquisition.framework.mgmt.ServiceManager.doStart(ServiceManager.java:221) ~[au-framework.jar:9.9.0-2021.08.J1133]

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
67c50fa2-cb40-49f6-89aa-287f4201802e