Hello
I have Neo4j Enterprise Edition version 5.11.0.
My team was running some cypher scripts against it and suddenly we started to get the following error:
Neo.ClientError.General.WriteOnReadOnlyAccessDatabase
No write operations are allowed on this database. The database is in read-only mode on this Neo4j instance.
I have a couple of questions about it:
1.- Why did the database lock itself into read-only mode?
2.- How can I revert this change? Can I do this from neo4j Browser?
Thanks,
Like Miguel, we are having the same issue after installing version 5.19.0. For two years we have been reading/writing with wild abandon on our standalone server. We seem to have lost the right to write using Neo4j Browser. The strange thing is we can still write through cypher-shell and code. That said, the Browser is a foundational tool in our Neo4j development.
Even with a vanilla install locally of v 5.19.0 - installed through Desktop - I am still locked out of write ability.
Is anyone else experiencing similar loss of write permissions? I can't find any diagnostic information inside or outside Neo4j Community. Could this be a bug?
Henry Bowers
Everstream Analytics
@henry_bowers @miguelgoicocheadeb
can't explain how you ended up this way but
describes how a database may be read only and how to revert.
Has any of this been tried?
Hi @dana_canzano . Thanks for quick response. On our test server all three databases indicate their mode is READ-WRITE:
╒═════════╤══════════╤═══════╤════════════╤════════════════╤═════════╤══════╤═══════════════╤═════════════╤═════════════╤═══════╤═════╤════════════╕
│name │type │aliases│access │address │role │writer│requestedStatus│currentStatus│statusMessage│default│home │constituents│
╞═════════╪══════════╪═══════╪════════════╪════════════════╪═════════╪══════╪═══════════════╪═════════════╪═════════════╪═══════╪═════╪════════════╡
│"cdctest"│"standard"│[] │"read-write"│"localhost:7687"│"primary"│true │"online" │"online" │"" │false │false│[] │
├─────────┼──────────┼───────┼────────────┼────────────────┼─────────┼──────┼───────────────┼─────────────┼─────────────┼───────┼─────┼────────────┤
│"neo4j" │"standard"│[] │"read-write"│"localhost:7687"│"primary"│true │"online" │"online" │"" │true │true │[] │
├─────────┼──────────┼───────┼────────────┼────────────────┼─────────┼──────┼───────────────┼─────────────┼─────────────┼───────┼─────┼────────────┤
│"system" │"system" │[] │"read-write"│"localhost:7687"│"primary"│true │"online" │"online" │"" │false │false│[] │
└─────────┴──────────┴───────┴────────────┴────────────────┴─────────┴──────┴───────────────┴─────────────┴─────────────┴───────┴─────┴────────────┘
If I try any command that would alter a database I get the read-only mode error, including ALTER DATABASE commands.
At this moment you may be wondering "if Henry can't write to a database at all, how the heck did he create cdctest? That's the extra-strange part of this issue: I have full permissions when interacting with neo4j through every interface except the Neo4j Browser when I open it through Neo4j Desktop. Opening Browser directly in my web browser works. cypher-shell works. I haven't tried python yet but I imagine the outcome will be positive there too.
There are two unique aspects of this problematic install compared to our norm (we have been using neo4j for almost three years both in dev and production without anything like this issue):
It is certainly possible that the voodoo came about due to human error. We are not as blocked as I had thought at time of my first post, since we can use the Browser outside Desktop. But what could have caused my local Desktop installation to also throw read-only access mode exceptions for a server I never touched with 5.19 or CDC?
Would it hurt if I reinstalled Neo4j Desktop, wipe the slate clean? Or - before I do - any other avenues of root cause seeking I might try?
@henry_bowers
Check left sidebar-frame of the browser , gear Icon and field named Use read transactions for cypher queries. and to which this setting really only applies if in a cluster. Is your Neo4j running in a cluster?
You nailed it @dana_canzano . Human error indeed. I must have flipped the switch accidentally while editing other settings.
I will wear my public embarrassment with pride, and thank you profusely for figuring out my problem. I imagine we would have figured it out eventually, but you just saved me from days of continued self-hamstringing.
Cheers,
Henry
