Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
yingding opened this issue Nov 22, 2021 · 4 comments
Closed

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

yingding opened this issue Nov 22, 2021 · 4 comments

Comments

@yingding
Copy link

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
Copy link
Member

dhimmel commented Nov 22, 2021

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
Copy link
Author

yingding commented Nov 22, 2021

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
Copy link
Contributor

@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
Copy link
Member

dhimmel commented Jul 2, 2022

Closing since we now have uptime alerts, see #45.

@dhimmel dhimmel closed this as completed Jul 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants