Virtual machine exited abruptly: redis and postgres

I have 2 machines down one containing redis and the other postgres. No errors up until that and they didn’t seem to have problems with memory. I’m trying to get them back up but restarting them does nothing:

Redis

2023-09-14T02:49:29.019 app[918592eb4e3e83] yyz [info] 26041:C 14 Sep 2023 02:49:29.019 * DB saved on disk

2023-09-14T02:49:29.028 app[918592eb4e3e83] yyz [info] 26041:C 14 Sep 2023 02:49:29.028 * RDB: 1 MB of memory used by copy-on-write

2023-09-14T02:49:29.050 app[918592eb4e3e83] yyz [info] 531:M 14 Sep 2023 02:49:29.050 * Background saving terminated with success

2023-09-14T03:43:31.871 runner[918592eb4e3e83] yyz [info] machine did not have a restart policy, defaulting to restart

2023-09-14T03:45:06.141 app[918592eb4e3e83] yyz [error] 2023-09-14T03:45:06.141716580 [01H2PTGTKCZFGRAZEDT05EV477:main:ERROR:src/firecracker/src/main.rs:321] Configuration for VMM from one single json failed: InvalidJson

2023-09-14T03:45:39.465 runner[918592eb4e3e83] yyz [info] machine did not have a restart policy, defaulting to restart

2023-09-14T03:45:56.960 app[918592eb4e3e83] yyz [error] 2023-09-14T03:45:56.960888431 [01H2PTGTKCZFGRAZEDT05EV477:main:ERROR:src/firecracker/src/main.rs:321] Configuration for VMM from one single json failed: InvalidJson

2023-09-14T03:45:56.962 app[918592eb4e3e83] yyz [warn] Virtual machine exited abruptly

2023-09-14T03:46:01.558 runner[918592eb4e3e83] yyz [info] machine did not have a restart policy, defaulting to restart

2023-09-14T05:40:43.358 app[918592eb4e3e83] yyz [error] 2023-09-14T05:40:43.358578863 [01H2PTGTKCZFGRAZEDT05EV477:main:ERROR:src/firecracker/src/main.rs:321] Configuration for VMM from one single json failed: InvalidJson

2023-09-14T05:40:43.359 app[918592eb4e3e83] yyz [warn] Virtual machine exited abruptly

2023-09-14T05:40:43.386 runner[918592eb4e3e83] yyz [info] machine exited with exit code 0, not restarting

Postgres

2023-09-14T05:30:28.498 app[3d8d37daed7289] yyz [warn] Virtual machine exited abruptly

2023-09-14T05:31:36.805 app[3d8d37daed7289] yyz [error] 2023-09-14T05:31:36.805577058 [01H0VV30CSAKM5BMH7J5A9NT7D:main:ERROR:src/firecracker/src/main.rs:321] Configuration for VMM from one single json failed: InvalidJson

2023-09-14T05:31:36.806 app[3d8d37daed7289] yyz [warn] Virtual machine exited abruptly

2023-09-14T05:31:37.157 app[3d8d37daed7289] yyz [error] 2023-09-14T05:31:37.157922628 [01H0VV30CSAKM5BMH7J5A9NT7D:main:ERROR:src/firecracker/src/main.rs:321] Configuration for VMM from one single json failed: InvalidJson

2023-09-14T05:31:37.158 app[3d8d37daed7289] yyz [warn] Virtual machine exited abruptly

2023-09-14T05:31:38.973 health[3d8d37daed7289] yyz [warn] Health check for your postgres database is warning. Your database might be malfunctioning.

2023-09-14T05:31:38.973 health[3d8d37daed7289] yyz [warn] Health check for your postgres vm is warning. Your instance might be hitting resource limits.

2023-09-14T05:31:38.973 health[3d8d37daed7289] yyz [warn] Health check for your postgres role is warning. Your cluster's membership might be affected.

2023-09-14T05:31:41.974 health[3d8d37daed7289] yyz [error] Health check for your postgres database has failed. Your database is malfunctioning.

2023-09-14T05:31:47.972 health[3d8d37daed7289] yyz [error] Health check for your postgres role has failed. Your cluster's membership is inconsistent.

2023-09-14T05:31:50.972 health[3d8d37daed7289] yyz [error] Health check for your postgres vm has failed. Your instance has hit resource limits. Upgrading your instance / volume size or reducing your usage might help.

Looks just like one of my machines in YYZ as well, could be a host is down/failing–status page doesn’t show anything however.

Seeing this on one of my machines as well - on my personal status page there was an error with the underlying server recently. We are still trying to heal but I’m on the verge of re-deploying.

I’m seeing this in YYZ as well on a Postgres machine.

I also had it on some other machines last week also in Toronto.

I had to redeploy those ones to get it working.

We had an issue after the host your machines are on rebooted and have resolved the underlying problem for existing machines and pushed out a fix so it doesn’t happen again.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.