PostGreSql Database won't start

[Mastadamus]

So today I updated SearX and RocketChat. I installed open project and a very short time later i received a notice it had ran out of memory. I then uninstalled it. I notice later on this night that my PostGreSql database service will not restart and its stuck in the following loop

Mar 28 15:03:59 [GET] /healthcheck
Mar 28 15:04:28 [DELETE] /databases/dbdd647f60a4644987a519043c095f93c5
Mar 28 15:04:28 remove: removing database dbdd647f60a4644987a519043c095f93c5
Mar 28 22:53:05 Detected existing installation
Mar 28 22:53:05 Resetting root password
Mar 28 22:54:43 Detected existing installation
Mar 28 22:54:43 Resetting root password
Mar 28 22:56:06 Detected existing installation
Mar 28 22:56:06 Resetting root password
Mar 28 22:57:21 Detected existing installation
Mar 28 22:57:21 Resetting root password
Mar 28 22:58:47 Detected existing installation
Mar 28 22:58:47 Resetting root password
Mar 28 23:00:08 Detected existing installation
Mar 28 23:00:08 Resetting root password
Mar 28 23:01:24 Detected existing installation
Mar 28 23:01:24 Resetting root password
Mar 28 23:02:49 Detected existing installation

these errors coincide with the original running out of memory issues with open project

Any help would be greatly appreciated. I didn't see anything about postgresql in the troubleshooting guide.

[Mastadamus]

@mastadamus This has fixed itself. I have no idea why or how it was stuck in a loop but after a solid hr of it repeating that it magically fixed itself.

[robi]

@mastadamus perhaps the 6.2.7 update applied

[Mastadamus]

@robi lol I don't know but it was weird. My logs show that loop continuing for a LONG time. Then right when I make the help post and go back to check it magically rights itself lol.

[girish]

Is it possible that you were running our of disk space but after some time space got cleared? You can also see dmesg output and see if you have any oom errors there. (You will see a stack dump there).

[Mastadamus]

@girish I got loads of disk space left. Im unsure why. The only thing i can think of is another one of my VM's were undergoing a checkpoint merge in hyper-V I wonder if that affected the PostGreSql database temporarily since they share the same storage space.