# Reactor on Ubuntu 24

**URL:** <https://forums.linbit.com/t/reactor-on-ubuntu-24/738>\
**Category:** DRBD Reactor\
**Tags:** drbd, drbd-reactor\
**Created:** [April 10, 2025, 5:03am UTC](https://forums.linbit.com/t/reactor-on-ubuntu-24/738 "2025-04-10T05:03:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yathus](https://avatars.discourse-cdn.com/v4/letter/y/b9e5f3/32.png) [@Yathus](https://forums.linbit.com/u/Yathus)\
**Post date:** [April 10, 2025, 5:03am UTC](https://forums.linbit.com/t/reactor-on-ubuntu-24/738/1 "2025-04-10T05:03:52Z")

</div>

Hello,

I try to use reactor on Ubuntu 24.04 after a successful test with Ubuntu 22.04  
My test consist to create 2 nodes + arbitrer (diskelss) and a NFS Server in HA Mode.

I used NFS High Availability Clustering Using DRBD and DRBD Reactor on RHEL 9 Guide.

Everything is working as expected, when i reboot the primary node, the seconday goes primary, except the “unblock port”, iptables always keep rules.

I compare resources agents scripts and there is some difference between ubuntu 22.04 and ubuntu 24.04 …

Do you have any ideas?

Thanks

Yathus

---

<div class="post-metadata">

**Author:** ![Yathus](https://avatars.discourse-cdn.com/v4/letter/y/b9e5f3/32.png) [@Yathus](https://forums.linbit.com/u/Yathus)\
**Post date:** [April 10, 2025, 6:09am UTC](https://forums.linbit.com/t/reactor-on-ubuntu-24/738/2 "2025-04-10T06:09:40Z")

</div>

i found the bug : [[ClusterLabs] About RA ocf💓portblock](https://lists.clusterlabs.org/pipermail/users/2024-October/036398.html)

I have to fix the chain\_isactive() from portblock script.

Now when i reboot the primary, the iptables chains are cleared when secondary comes up.

---

<div class="post-metadata">

**Author:** ![Ryan](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/ryan/32/42_2.png) [@Ryan](https://forums.linbit.com/u/Ryan)\
**Post date:** [April 14, 2025, 11:31pm UTC](https://forums.linbit.com/t/reactor-on-ubuntu-24/738/3 "2025-04-14T23:31:48Z")

</div>

Hi @Yathus,

Have you tried simply overwriting the portblock resource agent from upstream?

See the section “Portblock Resource Agent Workaround” in our blog post [Highly Available NFS for Proxmox With LINSTOR Gateway - LINBIT](https://linbit.com/blog/highly-available-nfs-for-proxmox-with-linstor-gateway/)

Most notably the section:

```shell
wget -O /usr/lib/ocf/resource.d/heartbeat/portblock \
https://raw.githubusercontent.com/ClusterLabs/resource-agents/main/heartbeat/portblock

```

Long story short, the combination of the specific versions of `iptables` and `resource-agents` shipped in Debian 12 will lead to issues. A quick workaround is to use a newer version of the portlblock resource agent.