Nope, we are on a red-hat enterprise setup. We built from tar files and set up two deployments of neo4j running side by side. Changed the process information for the second and the config for the broadcast ip/port to be different. They both run and c...
Thanks for this! I found the issue to be that the 'run' directory in Linux holds a file called 'graph.db.pid' and that held my pid information incorrectly. I removed it after turning off the database and it let it start up. Though now my issue is tha...
I've done the port configuration though it says the instance is already running at a process ID. What would make it think it's the same if the port values are different?
I'm confused with this as I've gotten it for development purposes and have a social login completed. Though the expiration still exists. Is this intended?
I'm assuming that it simply renews, as you mentioned, without hesitation or issue?
