-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[network] Binding throws java.lang.OutOfMemoryError: Java heap space on start #3145
Comments
I have the same issue on ARM Ubuntu. |
Encountered the same problem. Fixed it by correcting the entry in dhcpcd.conf. Some process (presumably installing pi-hole) had added those entries wrong. Hope this helps others. |
Same here with 2.3.0 and Debian on X64. Got the issue after Upgrading. |
I found out that in my case installed hamachi is a cause of the issue. |
@cytrus77 I can reproduce it on a clean install with only network binding. |
I can‘t reproduce that. Is that still an issue with latest master? |
I don't know. I would try to test this on weekend and give you some feedback. Maybe one of the other affected users can give some feedback more quickly? |
I just saw 2.4 was released a few days ago. I'll try next days and give feedback. |
Issue still there after update to 2.4.0 (manually done by |
Good. Or not so good, but at least you can reproduce it. I‘ll provide a special version with more debugging to find out what’s going wrong there. |
Please try this version. You should see some "INFO" messages when starting the discovery service. Could you please post these? You can delete all IPv6-entries. Thanks |
OK, I'll give it a try with a clean install. |
@J-N-K How exactly should I test it? |
@bugariu: uninstall the binding from PaperUI or from addons.cfg. Drop the file in you addons-folder (/usr/share/openhab2/addons on most Unix-like systems). But maybe we can take a short-cut. What CIDR suffix is configured (or what netmask?). I guess the OOM occurs when OH tries to construct too many address entries. |
One of the interfaces had an netmask of 255.0.0.0 Changing it to 255.255.255.0 seems to resolve the issue. So it seems that the bug is triggered by the netmask. This would correlate with what @lemval said in his post. So if you try to fix it, just set the netmask to 255.0.0.0 and see if this triggers reported behaviour. |
I could reproduce the bug with a /8 network. |
System:
Changes in runtime/bin/setenv:
Other infos:
How to reproduce:
The text was updated successfully, but these errors were encountered: