Hello I hope someone can help me :pray: Our Linstor production cluster just went down and I’m not able to get it back up. The controller is in a crashloop spitting out this error message every time: ERROR REPORT 66CE118B-00000-000000 ============================================================ A…

LINSTOR’s complaint appears to be that it cannot allocate using port 7077 as it’s already being used. LINSTOR defaults to using ports 7000 - 7999 to allocate for resources, but if something is already running on a port and LINSTOR attempts to assign it, it will result in an error. Is that the case …

Thanks for your prompt reply. Fortunately, I was able to restore the LINSTOR controllers within 2 hours of the outage. Upon further investigation, I found that there were multiple DRBD resource definitions attempting to use the same TCP port (7077), which led to the controller crash. Specifically,…

One thing I forgot to mention is that, prior to this issue, the control plane of the Kubernetes cluster went down. I believe this affected LINSTOR as it could not communicate with the K8S API. Having said that, I would expect LINSTOR to be able to resist such an outage without resulting in data corr…

To confirm, which backend are using currently for LINSTOR? This can be displayed here: kubectl exec deploy/linstor-op-cs-controller – cat /etc/linstor/linstor.toml A LINSTOR cluster within k8s using an etcd database might run into problems like you’ve encountered, which is why the current guidance…

We’re running into a similar issue again, where the entire LINSTOR cluster is down. The controller seems to be stuck in a boot loop, and from what I can tell, this appears to be caused by a corrupted LINSTOR state. I’m looking for guidance on: 1. What might be causing this issue? 2. How can the L…

I tried fixing the database by deleting records that it was complaining about, but now I’m not longer getting any hints on what to do next: ERROR REPORT 6798A7C6-00000-000001 ============================================================ Application: LINBIT? LINSTOR Module: …

There isn’t much you can do in this case besides restore the database from backup, it appears that LINSTOR is looking for a reference to a storage pool which is not specified within these records. I see you’ve also commented on the Github issue here so I’ll link that as it provides some relevant di…

Thanks for your response, @liniac . Unfortunately, the last backup was made over a year ago, which suggests that backups are only created during upgrades. Reverting to that backup would result in significant data loss, which I’m not ready to accept. Instead, I’m attempting to delete all LINSTOR CRDs…

To my surprise, the deletion strategy actually worked! The LINSTOR controller is now able to boot again, and the cluster is back online. Below I’ll share more context and the steps I took to resolve the issue. Context We run LINSTOR in a K3s cluster, backed by an external MySQL database that store…

Linstor-controller just went down

LINSTOR

boedy August 28, 2024, 8:34am 6

#/etc/linstor/linstor.toml
[db]
  connection_url = "k8s"

We are running Linstor using the Piraeus operator on a K3S cluster with MySQL as backing its datastore.

Topic		Replies	Views
Linstor controller crashes LINBIT SDS Integrations kubernetes	3	262	December 7, 2024
Linstor Controller Crashing General kubernetes , drbd	1	154	May 16, 2025
Former primary node stuck in emergency mode after reboot DRBD Reactor kubernetes , drbd , drbd-reactor	6	180	December 17, 2025
How to install Reactor for Linstor-controller-HA in a k8s environment? LINSTOR kubernetes , drbd	3	151	December 10, 2024
LINSTOR Operator v2.8.1 Release Announcements kubernetes , drbd	0	60	April 10, 2025

Linstor-controller just went down

Related topics