New
Question Luis Gallardo · Mar 24

Hi!
We are deploying the iris image in a Kubernetes environment and the cluster state is "Hung" , looking the alerts endpoint we get 2 alerts:

[
  {
     "time":"2026-03-24T13:45:44.548Z",
     "severity":"2",
     "message":"System appears to have failed over from node a69a9f137593"
  },
  {
     "time":"2026-03-24T13:46:30.274Z",
     "severity":"2",
     "message":"Error: <PROTECT>KillAlive+1^%SYS.CDIRECT in SERVERS"
  }
]
Any idea / help where those are comming from and how to address them?

1
0 33
Question Luis Gallardo · Mar 17

We are trying to run the HS solution inside of a container, but we are getting the following errors un start up
03/17/26-10:19:05:108 (1386) 1 [Generic.Event] Cannot lock /usr/irissys/mgr/hslib/ err(13): will try accessing readonly
03/17/26-10:19:08:174 (1386) 1 [Generic.Event] Cannot lock /usr/irissys/mgr/enslib/ err(13): will try accessing readonly

I understand that those databases should be mounted as read only don't needing the lock, any idea how to fix it? or where should I look to configure it correctly?
Thanks!

03/17/26-10:19:08:176 (1463) 0 [Database.
2
0 48