Yesterday my UTM hangs completly and I had to restart it (hard reset) [:O].
Unable to login using WebAdmin, SSH or even console from vSphere.
It's the 1st time I faced a similar issue on this VM hosted on an ESXi 5.5. Other VMs on this host were still working well.
Please find a short extract a short extract of the system log
2014:01:22-00:54:40 set postgres[4076]: [3-1] LOG: checkpointer process (PID 4078) was terminated by signal 9: KilledJan 22 00:54:40 postgres[4076]: [4-1] LOG: terminating any other active server processes
2014:01:22-00:54:40 set postgres[4076]: [5-1] LOG: archiver process (PID 4082) exited with exit code 1
2014:01:22-00:54:40 set postgres[16438]: [3-1] WARNING: terminating connection because of crash of another server processJan 22 00:54:40 postgres[16438]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014:01:22-00:54:40 set postgres[16438]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2014:01:22-00:54:40 set postgres[10916]: [3-1] WARNING: terminating connection because of crash of another server processJan 22 00:54:40 postgres[10916]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014:01:22-00:54:40 set postgres[10916]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2014:01:22-00:54:40 set ulogd[16435]: pg1: server closed the connection unexpectedly
2014:01:22-00:54:42 set ulogd[16435]: pg1: connect: FATAL: the database system is in recovery mode
2014:01:22-00:54:40 set postgres[4081]: [11-1] WARNING: terminating connection because of crash of another server process
2014:01:22-00:54:40 set postgres[4081]: [11-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014:01:22-00:54:40 set postgres[4081]: [11-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2014:01:22-00:54:41 set postgres[4076]: [6-1] LOG: all server processes terminated; reinitializing
2014:01:22-00:54:42 set postgres[10561]: [7-1] FATAL: the database system is in recovery mode
2014:01:22-00:54:42 set postgres[10560]: [7-1] LOG: database system was interrupted; last known up at 2014-01-21 23:53:05 GMT
2014:01:22-00:54:43 set postgres[4076]: [7-1] LOG: startup process (PID 10560) was terminated by signal 9: Killed
2014:01:22-00:54:43 set postgres[4076]: [8-1] LOG: aborting startup due to startup process failure
2014:01:22-00:54:40 set postgres[6722]: [3-1] WARNING: terminating connection because of crash of another server processJan 22 00:54:40 postgres[6722]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014:01:22-00:54:40 set postgres[6722]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2014:01:22-00:54:40 set postgres[5594]: [3-1] WARNING: terminating connection because of crash of another server processJan 22 00:54:40 postgres[5594]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014:01:22-00:54:40 set postgres[5594]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2014:01:22-00:54:40 set postgres[6721]: [3-1] WARNING: terminating connection because of crash of another server processJan 22 00:54:40 postgres[6721]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014:01:22-00:54:40 set postgres[6721]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2014:01:22-00:54:41 set postgres[6745]: [3-1] WARNING: terminating connection because of crash of another server processJan 22 00:54:41 postgres[6745]: [3-2] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2014:01:22-00:54:41 set postgres[6745]: [3-3] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2014:01:22-00:54:46 set ulogd[16435]: pg1: connect: could not connect to server: No such file or directory
2014:01:22-00:54:51 set ulogd[16435]: pg1: connect: could not connect to server: No such file or directory
2014:01:22-00:54:56 set ulogd[16435]: pg1: connect: could not connect to server: No such file or directory
2014:01:22-00:55:01 set ulogd[16435]: pg1: connect: could not connect to server: No such file or directory