Skip to main content
NetApp Knowledge Base

AIQUM 9.16 and above shows multiple issues  during fresh installation on RHEL 9.x due to File Access Policy and Firewall daemons

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

Applies to

  • ActiveIQ Unified Manager (AIQUM) 9.16+
  • RedHat Linux (RHEL) 9.x
  • File Access Policy Daemon (fapolicyd)
  • Firewall daemon (firewalld)

Issue

  • AIQUM fresh installation on RHEL 9.x failed even though the pre_install script shows no issue
  • Error on screen (also recorded on /var/log/dnf.log):

[root@AIQUM netapp]# yum localinstall netapp-um-9.18-el9.x86_64.rpmLast metadata expiration check: 0:47:07 ago on Mon 23 Feb 2026 11:33:51 AM CET.

Dependencies resolved.=====================================================================================================================================================================================================Package                                      Architecture                              Version                                                Repository                                       Size=====================================================================================================================================================================================================Installing:netapp-um                                    x86_64                                    9.18-2601081010.el9                                    @commandline                                    1.8 GTransaction Summary=====================================================================================================================================================================================================Install  1 Package

Total size: 1.8 G

Installed size: 1.9 G

Is this ok [y/N]: y

Downloading Packages:

Package netapp-um-9.18-el9.x86_64.rpm is not signed

Error: GPG check FAILED

[root@AIQUM netapp]#

  • Attempting with --nogpgcheck allows the installation to proceed: yum localinstall netapp-um-9.18-el9.x86_64.rpm --nogpgcheck
  • However ocie service failed to start after installation:
  • /var/log/ocie/server.log:

WARN  [org.jboss.modules.define] (main) Failed to define class org.jboss.as.server.jmx.PluggableMBeanServer in Module "org.jboss.as.server" version 18.1.2.Final from local module loader @41ee392b (finder: local module finder @1e67a849 (roots: /opt/netapp/essentials/jboss/modules, /opt/netapp/essentials/jboss/modules/system/layers/base)): org.jboss.modules.ModuleLoadError: Error loading module from /opt/netapp/essentials/jboss/modules/system/layers/base/org/jboss/classfilewriter/main/module.xml

….

Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'unnamed' at path 'jboss-classfilewriter-1.2.5.Final.jar' (position: END_TAG seen ...     <resource-root path="jboss-classfilewriter-1.2.5.Final.jar"/>... @29:70) caused by: java.io.FileNotFoundException: /opt/netapp/essentials/jboss/modules/system/layers/base/org/jboss/classfilewriter/main/jboss-classfilewriter-1.2.5.Final.jar (Operation not permitted)

Caused by: java.io.FileNotFoundException: /opt/netapp/essentials/jboss/modules/system/layers/base/org/jboss/classfilewriter/main/jboss-classfilewriter-1.2.5.Final.jar (Operation not permitted)

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.