The warning section in the README describing how we need to delete the pvc to change the default password is not correct.

We can indeed reset that password without having to delete the PVC by:

1. Deleting the file /var/lib/neo4j/data/dbms/auth
2. Running neo4j-admin set-initial-password <new password>
3. Deleting the pod / restart the service

I will create a PR with this section updated.

Hi,
I see that there are 2 possible pods(containers) being created by the statefuleset.yaml file.
securityContext needs to be configured at pod/container level while it is configured outside the containers block. This is preventing me to run neo4j-community StatefulSet with added securityContext(s).
This needs to be fixed I believe.

Very first helm install of the neo4j-community chart with a clean volume is resulting in: Unable to obtain lock on file: /data/databases/store_lock issue.

Directories in use:
home: /var/lib/neo4j
config: /var/lib/neo4j/conf
logs: /logs
plugins: /plugins
import: /var/lib/neo4j/import
data: /var/lib/neo4j/data
certificates: /var/lib/neo4j/certificates
run: /var/lib/neo4j/run
Starting Neo4j.
2021-06-18 14:22:18.148+0000 INFO Starting...
2021-06-18 14:22:21.255+0000 INFO ======== Neo4j 4.2.4 ========
2021-06-18 14:22:32.893+0000 ERROR Failed to start Neo4j on dbms.connector.http.listen_address, a socket address. If missing port or hostname it is acquired from dbms.default_listen_address.
java.lang.RuntimeException: Error starting Neo4j database server at /var/lib/neo4j/data/databases
at org.neo4j.graphdb.facade.DatabaseManagementServiceFactory.startDatabaseServer(DatabaseManagementServiceFactory.java:207) ~[neo4j-4.2.4.jar:4.2.4]
...
Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.internal.locker.LockerLifecycleAdapter@17ca8b92' was successfully initialized, but failed to start. Please see the attached cause exception "No locks available".
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:463) ~[neo4j-common-4.2.4.jar:4.2.4]
... 5 more
Caused by: org.neo4j.kernel.internal.locker.FileLockException: Unable to obtain lock on file: /var/lib/neo4j/data/databases/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)
at org.neo4j.kernel.internal.locker.Locker.storeLockException(Locker.java:175) ~[neo4j-kernel-4.2.4.jar:4.2.4]

Here are the versions in my environment:

Kubernetes v1.19
Helm v3.6.0
kubeadm 1.19.7
Nodes running Ubuntu 20.04.1 LTS

I suspect neo4j is restarting for some reason and as reported in neo4j/docker-neo4j#289, neo4j is not clearing the lock from previous start and failing.

Have you experienced a similar issue anytime? Any ideas why an auto-restart may be happening? I'm seeing the same issue with the helm chart from neo4j-contrib.

Hello,

Would it be reasonable to add jmx reporting support for Neo4j? I'm looking for a way to expose basic metrics from Neo4J that can then be consumed by a Prometheus instance and receive alerts when the Neo4J deployment has any issue.

I'm more than happy to open a PR for this.
Thank you.

macOS 10.15.7
kind v0.10.0 go1.15.8 darwin/amd64

########### CONFIG ##############
image: "neo4j"
imageTag: "3.5.25"
imagePullPolicy: "IfNotPresent"
name: "neo4j"
service:
type: ClusterIP
core:
standalone: true
persistentVolume:
mountPath: /Users/jonas/code/cartography/data
acceptLicenseAgreement: "yes"
neo4jPassword: password

########## PERMS ON MOUNT PATH ##########
❯ ls -la /Users/jonas/code/cartography/data
total 0
drwxrwxrwx 2 jonas staff 64 Feb 25 15:02 .

########## INITIAL RESULT ##########
❯ kubectl logs -l "app=neo4j-community"
import: /var/lib/neo4j/import
data: /var/lib/neo4j/data
certificates: /var/lib/neo4j/certificates
run: /var/lib/neo4j/run
Starting Neo4j.
2021-02-26 16:17:40.596+0000 INFO ======== Neo4j 3.5.25 ========
2021-02-26 16:17:40.620+0000 INFO Starting...
2021-02-26 16:17:45.025+0000 INFO Bolt enabled on 0.0.0.0:7687.
2021-02-26 16:17:48.365+0000 INFO Started.
2021-02-26 16:17:50.574+0000 INFO Remote interface available at http://localhost:7474/

########### GET neo4j.log VIA KUBECTL EXEC INTO NEO4J CONTAINER ##############
2021-02-26 20:16:00.446+0000 ERROR Failed to start Neo4j: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@7a362b6b' was successfully initialized, but failed to start. Please see the attached cause exception "Store and its lock file has been locked by another process: /data/databases/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)". Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@7a362b6b' was successfully initialized, but failed to start. Please see the attached cause exception "Store and its lock file has been locked by another process: /data/databases/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)".
org.neo4j.server.ServerStartupException: Starting Neo4j failed: Component 'org.neo4j.server.database.LifecycleManagingDatabase@7a362b6b' was successfully initialized, but failed to start. Please see the attached cause exception "Store and its lock file has been locked by another process: /data/databases/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)".

'/' is a read only filesystem on MacOS so of course overriding the default mount path is required. Have you ever successfully executed this helm chart against MacOS with a non-default path? I'm very curious to know how you achieved that.

Thanks!