search

hetio / hetionet

Hetionet: an integrative network of disease
https://neo4j.het.io
257 stars 68 forks source link

http://neo4j.het.io/browser/ time out #44

Closed yingding closed 2 years ago

yingding commented 2 years ago

At the time of writing (UTC timestamp: 1637594788), i was not able to connect to http://neo4j.het.io/browser/ and got a time out error.

UTC timestamp: 1637594788
GMT: Monday, 22 November 2021 15:26:28

To convert the timestamp to your timezone time with https://www.epochconverter.com/

Thanks for your help in advance.

dhimmel commented 2 years ago

Thanks for the report. I restarted the instance so it's back up now.

@dongbohu any suggestions on an automated way to restart the VM or docker instance when the Neo4j database stops working? We could do a daily restart such that an outage would never be >24 hours? Or could we detect whether the database fails to respond to a query... and if so restart?

yingding commented 2 years ago

If you can replace the docker with microk8s on an Ubuntu 20.04 LTS, the microk8s will restart the pod/container by itself. There will be no outage.

dongbohu commented 2 years ago

@dhimmel I never used microk8s before. The simplest solution I can think of is to launch a http(s) request and see whether the response is valid. If not, restart the docker container.

dhimmel commented 2 years ago

Closing since we now have uptime alerts, see https://github.com/hetio/hetionet/issues/45.