# Linstor-gateway on diskless satellites

**URL:** <https://forums.linbit.com/t/linstor-gateway-on-diskless-satellites/90>\
**Category:** LINSTOR\
**Created:** [May 13, 2024, 2:22pm UTC](https://forums.linbit.com/t/linstor-gateway-on-diskless-satellites/90 "2024-05-13T14:22:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![rmendes](https://avatars.discourse-cdn.com/v4/letter/r/35a633/32.png) [@rmendes](https://forums.linbit.com/u/rmendes)\
**Post date:** [May 13, 2024, 2:22pm UTC](https://forums.linbit.com/t/linstor-gateway-on-diskless-satellites/90/1 "2024-05-13T14:22:45Z")

</div>

I’m trying to setup an HA NFS server with linstor-gateway. The cluster has 2 combined nodes and 5 satellite nodes. The disks are on the combined nodes and all the 5 satellite nodes are diskless.

When I run “linstor-gateway nfs create” it fails because it’s trying to create the reactor config on the diskless satellites.

How can I make linstor-gateway create the config only on the nodes that have disks ?

Ruben

---

<div class="post-metadata">

**Author:** ![chrboe](https://yyz1.discourse-cdn.com/flex003/user_avatar/forums.linbit.com/chrboe/32/27_2.png) [@chrboe](https://forums.linbit.com/u/chrboe)\
**Post date:** [May 14, 2024, 12:57pm UTC](https://forums.linbit.com/t/linstor-gateway-on-diskless-satellites/90/2 "2024-05-14T12:57:55Z")

</div>

Hi,

could you share some more information about what exactly is failing? Error messages in journal and/or dmesg should usually be a good hint.

Usually, drbd-reactor will try to start the service on a diskful node. It will only attempt to start on a diskless node if no diskful nodes are available.

Technically speaking, this happens because drbd-reactor imposes a 6-second delay before trying to promote a resource on a diskless node, so the diskful nodes have a “head start”.

So if it’s trying to promote the resource on a diskless node, that is only because it already failed on the diskful nodes.

---

<div class="post-metadata">

**Author:** ![rmendes](https://avatars.discourse-cdn.com/v4/letter/r/35a633/32.png) [@rmendes](https://forums.linbit.com/u/rmendes)\
**Post date:** [May 14, 2024, 2:54pm UTC](https://forums.linbit.com/t/linstor-gateway-on-diskless-satellites/90/3 "2024-05-14T14:54:55Z")

</div>

The error is not with drbd-reactor but with linstor-gateway, when setting up the service:

```auto
root@srv-nas2-dc:~# linstor-gateway nfs create nfs-server 10.7.31.209/32 50G --allowed-ips=10.7.31.0/24 --resource-group=nfs-rg
ERRO[0025] failed to create nfs resource: failed to start resources: failed to attach reactor configuration: error attaching file to resource: Message: '(Node: 'srv-prox1-dc') Failed to create temporary file in directory: /etc/drbd-reactor.d'; Reports: '[664219A9-A35B9-000002]' next error: Message: 'Deployed /etc/drbd-reactor.d/linstor-gateway-nfs-nfs-server.toml on resource 'nfs-server' on 'srv-nas2-dc'' next error: Message: 'Deployed /etc/drbd-reactor.d/linstor-gateway-nfs-nfs-server.toml on resource 'nfs-server' on 'srv-nas1-dc'' next error: Message: 'Modification of resource definition 'nfs-server' failed due to an unknown exception.'; Details: 'Resource definition: nfs-server'; Reports: '[660D8D32-00000-000007]'

```

It fails because drbd-reactor is not installed on node srv-prox1-dc which is diskless. I would like that linstor-gateway does not try to configure on the diskless nodes but only on diskfull nodes (srv-nas1-dc and srv-nas2-dc).

---

<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:** [May 14, 2024, 3:50pm UTC](https://forums.linbit.com/t/linstor-gateway-on-diskless-satellites/90/4 "2024-05-14T15:50:06Z")

</div>

LINSTOR Gateway will attempt to configure a DRBD resource on three nodes for quorum purposes. You’ll need to install DRBD Reactor on all nodes in the LINSTOR cluster regardless of nodes being diskfull/diskless. DRBD Reactor will create configurations on the diskless nodes for each resource’s diskless/quorum/TieBreaker component.
