openSUSE admin

I just figured out that the same 500 happens if I try to comment to the issue.

Logs mention that connection to redis failed.

This is what I'm seeing at a cursory glance...

pagure01 (pagure):~ # systemctl status redis@default
× redis@default.service - Redis instance: default
     Loaded: loaded (/usr/lib/systemd/system/redis@.service; enabled; vendor preset: disabled)
     Active: failed (Result: signal) since Wed 2023-03-08 16:38:42 UTC; 4 days ago
    Process: 25073 ExecStart=/usr/sbin/redis-server /etc/redis/default.conf (code=killed, signal=KILL)
   Main PID: 25073 (code=killed, signal=KILL)
     Status: "Redis is loading..."

Mar 08 16:38:42 pagure01 systemd[1]: redis@default.service: Main process exited, code=killed, status=9/KILL
Mar 08 16:38:42 pagure01 systemd[1]: redis@default.service: Failed with result 'signal'.
Mar 08 16:38:42 pagure01 systemd[1]: Failed to start Redis instance: default.
Mar 08 16:38:42 pagure01 systemd[1]: redis@default.service: Scheduled restart job, restart counter is at 2183.
Mar 08 16:38:42 pagure01 systemd[1]: Stopped Redis instance: default.
Mar 08 16:38:42 pagure01 systemd[1]: redis@default.service: Start request repeated too quickly.
Mar 08 16:38:42 pagure01 systemd[1]: redis@default.service: Failed with result 'signal'.
Mar 08 16:38:42 pagure01 systemd[1]: Failed to start Redis instance: default.
pagure01 (pagure):~ # systemctl start redis@default
Job for redis@default.service failed because a fatal signal was delivered to the control process.
See "systemctl status redis@default.service" and "journalctl -xeu redis@default.service" for details.

Looks like redis is getting killed because we're out of memory. Trying to restart service to free up RAM.

SUSE IT ticket https://sd.suse.com/servicedesk/customer/portal/1/SD-114879