-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on registering local node on cluster #7059
Comments
We'd need the entire log, please. |
|
I am wondering if it is caused by any files which need read or wirte rights ? |
It looks like the starting node is unable to register on Hazelcast cluster. Could you try to replace |
Could you please tell me in which file should i configure this ip ? Thanks. |
Hi, lvca:
The problem remains. |
Now I have no ideas, the log is as follows:
|
I also try my own ip, the issue remains. |
Dear friend |
Hi, @CrazyBeeline , I still have this problem, even the different nodes can established the socket connection, maybe @lvca can fix it and make it more steady later. |
Hi guys, I'm unable to reproduce it. Could you please try with last version on 2.2.x branch? |
Dear friend |
@CrazyBeeline In order to help other users wit a similar error, do you have any ideas what could be the cause? |
Hi, Thanks for your patience while we continue our analysis on this issue We feel this might be linked to the installed java version. Are you using java 1.7 in the system where the issue is happening? Many Thanks, |
This has just been fixed in 2.2.16-SNAPSHOT to work with Java 7. |
Thanks @SDIPro Link to the commit that fixes the issue: 7b44e0d Release Notes updated No changes needed in the documentation |
OrientDB Version, operating system, or hardware.
Operating System
Expected behavior and actual behavior
Starting node in cluster for the first time
./dserver.sh (default configuration)
Steps to reproduce the problem
Error on publishing local server configuration [OHazelcastPlugin]
Any help would be appreciate ! Thanks !
The text was updated successfully, but these errors were encountered: