Skip to content
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.

When using an older version of Neo4J (3.5) the latest changes in 4.3.2-1 chart cause startup errors #212

Open
stephenpope opened this issue Sep 7, 2021 · 0 comments

Comments

@stephenpope
Copy link

Describe the bug
When using Neo4J 3.5 as the base image then the latest changes in : https://github.com/neo4j-contrib/neo4j-helm/blob/master/templates/common-configmap.yaml#L24
.. cause Neo4J to error on startup.

To Reproduce
Steps to reproduce the behavior:

  1. Install with these values
  acceptLicenseAgreement: "yes"
  authEnabled: false
  imageTag: "3.5"

Expected behavior
Neo4J starts up.

Error Logs

Starting Neo4j.
2021-09-07 13:58:52.945+0000 ERROR [o.n.s.CommunityBootstrapper] Failed to start Neo4j on unknown address. Invalid connector setting: dbms.connector.bolt.connection_keep_alive_for_requests
org.neo4j.graphdb.config.InvalidSettingException: Invalid connector setting: dbms.connector.bolt.connection_keep_alive_for_requests
	at org.neo4j.kernel.configuration.ConnectorValidator.lambda$null$1(ConnectorValidator.java:144)
	at java.util.Optional.orElseThrow(Optional.java:290)
	at org.neo4j.kernel.configuration.ConnectorValidator.lambda$validate$2(ConnectorValidator.java:143)
	at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
	at java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1699)
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
	at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
	at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
	at org.neo4j.kernel.configuration.ConnectorValidator.validate(ConnectorValidator.java:141)
	at org.neo4j.kernel.configuration.IndividualSettingsValidator.validate(IndividualSettingsValidator.java:61)
	at org.neo4j.kernel.configuration.Config.migrateAndValidateAndUpdateSettings(Config.java:807)
	at org.neo4j.kernel.configuration.Config.<init>(Config.java:420)
	at org.neo4j.kernel.configuration.Config.<init>(Config.java:84)
	at org.neo4j.kernel.configuration.Config$Builder.build(Config.java:314)
	at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:108)
	at org.neo4j.server.ServerBootstrapper.start(ServerBootstrapper.java:91)
	at org.neo4j.server.CommunityEntryPoint.main(CommunityEntryPoint.java:32)
2021-09-07 13:58:52.948+0000 INFO [o.n.s.CommunityBootstrapper] Neo4j Server shutdown initiated by request

Additional context
There is no way to bypass or work around this other than revert to 4.2.8-1

@stephenpope stephenpope changed the title When using an older version of Neo4J (3.5) the latest changed in 4.3.2-1 chart cause startup errors When using an older version of Neo4J (3.5) the latest changes in 4.3.2-1 chart cause startup errors Sep 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant