Closed jdauvill closed 4 years ago
Thanks for the report.
Paging @dongbohu. We'll look into this ASAP, collecting debugging info to see why this has happened. And then restart the server. Should be back up by Tues Sep 14 sometime.
The neo4j web server seems working okay now. @dhimmel, did you restart the docker process?
No I didn't do anything. I can confirm that as of ~8 hours ago the problem existed, but now does not.
Any chance we can get some debugging info from the logs?
On Tue, Sep 24, 2019, 8:21 AM dongbohu notifications@github.com wrote:
The neo4j web server seems working okay now. @dhimmel https://github.com/dhimmel, did you restart the docker process?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hetio/hetionet/issues/25?email_source=notifications&email_token=AAIQ4B4GPLXFIVTRWRMTAZ3QLIA3ZA5CNFSM4IZJHUQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7OEAXQ#issuecomment-534528094, or mute the thread https://github.com/notifications/unsubscribe-auth/AAIQ4B4JPKRD6PUZKAL3F4DQLIA3ZANCNFSM4IZJHUQQ .
@dhimmel: I am in San Diego for DjangoCon now. If you can log into the AWS EC2 instance, feel free to check docker logs. If you can't, I will do it after I am back on Thursday.
This seems to be the error when the server was not working on 09/23:
org.eclipse.jetty.util.SharedBlockingCallback$BlockerTimeoutException
also seems to have been a problem in https://github.com/hetio/hetionet/issues/9, https://github.com/neo4j/neo4j/issues/9209, https://github.com/neo4j/neo4j/issues/4430.
Perhaps we should upgrade to the latest patch release of Neo4j
@dhimmel: You mean Community Edition 3.5.11? https://neo4j.com/download-center/#community
Currently we use:
But there is a 3.2.14-enterprise
release, so 6 patch versions ahead of what we're using, each with various changes.
I believe 3.2 is the last Neo4j enterprise versions that are open source. Therefore if we wanted to update to 3.5, we'd have to switch to community. There aren't any major features of enterprise that we use, but sometimes small features get made enterprise. Anyways, lot's of testing will be required to make sure the upgrade doesn't break anything, especially if incrementing major versions or from enterprise to community.
Or perhaps we wait till 4.0 is released and upgrade then.
Sooner or later the support of 3.2.X will be stopped and we'll have to do a major upgrade. If we upgrade from 3.2.X to 4.0 directly, wouldn't it be even more risky?
Sooner or later the support of 3.2.X will be stopped and we'll have to do a major upgrade
There's no reason why we have to use a supported version. If an old version works that is not supported, we can use it.
But anyways in https://github.com/hetio/hetionet/pull/26, I upgrade to 3.5.12
. Didn't seem to break anything and it's nice to have the latest features. Perhaps the upgrade will also fix these downtime issues (or introduce new ones :smiling_imp:).
Hi, Unfortunately I can't access Hetionet at https://neo4j.het.io/browser/ See screen-shots below: