# Rocky 9\_8 + Apache

**URL:** <https://forums.rockylinux.org/t/rocky-9-8-apache/20852>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [October 20, 2026, 10:23am UTC](https://forums.rockylinux.org/t/rocky-9-8-apache/20852 "2026-10-20T10:23:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ana.gregorio](https://avatars.discourse-cdn.com/v4/letter/a/a88e4f/32.png) [@ana.gregorio](https://forums.rockylinux.org/u/ana.gregorio)\
**Post date:** [October 20, 2026, 10:23am UTC](https://forums.rockylinux.org/t/rocky-9-8-apache/20852/1 "2026-10-20T10:23:36Z")

</div>

We are experiencing an issue on several Rocky Linux 9 servers after OS patching and reboot.

Environment:

- OS: Rocky Linux 9
- Application server: JBoss
- Component: mod\_cluster
- Environment: Production

After patching and rebooting the Rocky Linux servers, JBoss started reporting mod\_cluster communication errors with the Apache/mod\_cluster nodes.

Examples:

MODCLUSTER000043: Failed to send STATUS to Apache/mod\_cluster

MODCLUSTER000042: Error MEM sending STATUS command,  
configuration will be reset:  
MEM: Can’t read node with JVMRoute

The issue appeared after the OS patching/reboot, although at this point we cannot confirm that the Rocky Linux updates are the root cause.

We are currently checking:

- Network connectivity between JBoss and Apache/mod\_cluster
- Firewall status
- SELinux status
- Kernel changes
- Packages updated during the maintenance
- JBoss/mod\_cluster node registration

Could any Rocky Linux 9 update potentially affect mod\_cluster communication, networking, firewall, SELinux, OpenSSL or related components?

Which OS-level logs or package changes would you recommend checking to determine whether the issue is related to the Rocky Linux patching?

Thank you.