Home Explore Help
Sign In
cecf
/
deploy
5
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: e4538f3d9b
Branches Tags
deploy
/
neo4j-helm
/
doc
/
docs
/
modules
/
ROOT
/
pages
/
troubleshooting.adoc

troubleshooting.adoc 2.6 KB
History Raw

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253 
  1. [#troubleshooting]
    2. 

  2. = Troubleshooting & FAQs
    3. 

  3. 

  4. [NOTE]
    5. 

  5. This material covers only Kubernetes specifics of running Neo4j.  It is not intended to
    6. 

  6. be troubleshooting guidance for the Neo4j product itself; for that, please consult the Neo4j 
    7. 

  7. operations manual and other sources.
    8. 

  8. 

  9. == I specified a password on install and it didn't work
    10. 

  10. 

  11. Are you starting with empty disks?
    12. 

  12. 

  13. The most common issue associated with the helm chart is persistent volume claim reuse. For example, if you deploy `mygraph`, delete this instance, and then redeploy a new, different `mygraph`, it will not get clean empty PVCs, but will reuse the old PVCs from the previous deployment. 
    14. 

  14. 

  15. A common problem is to install an instance with one password, which gets written to Neo4j's system 
    16. 

  16. database.  Later, when those PVCs are reused, an intial password cannot be set because it's already
    17. 

  17. been set.
    18. 

  18. 

  19. [NOTE]
    20. 

  20. **When you uninstall a helm distribution it does not remove persistent volume claims.**
    21. 

  21. 

  22. Make sure to ensure the disks you're starting with are empty to avoid file permissioning and other issues.
    23. 

  23. 

  24. == APOC installation Fails
    25. 

  25. 

  26. Neo4j's method for installing plugins requires internet access.  If you are in a locked-down networking environment, the automatic plugin installation may fail.  In this case, you should
    27. 

  27. set `plugins: []` and use an `initContainer` to copy the appropriate plugins and extensions into
    28. 

  28. your install manually.
    29. 

  29. 

  30. == I tried to run a backup and it started a new cluster!
    31. 

  31. 

  32. This repo contains two helm charts; one for backup and the other to install a cluster or standalone instance.  Ensure that when you run `helm install` you are pointing to the right directory.
    33. 

  33. 

  34. == Something's going wrong, where do I look for logs?
    35. 

  35. 

  36. Neo4j comes with a built-in `debug.log` file that is stored in the logs directory.  This is the place
    37. 

  37. to check when you run into trouble.  Inspect this file and look for `Exception` error messages, and often
    38. 

  38. the product logs will tell you what the issue is.
    39. 

  39. 

  40. == Can I host my own docker containers?
    41. 

  41. 

  42. Yes.
    43. 

  43. 

  44. When you use this repo, you'll be pulling images for causal cluster, backup, and so on from
    45. 

  45. the repository that's provided.  If you wish to host your own Docker images, you need to adjust
    46. 

  46. the Makefile in `tools` that builds the docker images to point to your repo.  You may then specify
    47. 

  47. values to your install process that change the `image` and `imageTag` you are running.  Check the
    48. 

  48. repo's top level README for information about building the tooling containers.
    49. 

  49. 

  50. == Something Else?
    51. 

  51. 

  52. The https://community.neo4j.com/c/neo4j-graph-platform/cloud/76[Neo4j Community Site] is a great place
    53. 

  53. to ask for help.
    54.