-
Notifications
You must be signed in to change notification settings - Fork 679
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] netlink_connector::receive_cbk received error message: 2 seq 3 #492
Comments
I'm seeing the same when using kernel 6.x. Is it a known bug? |
What version of boost do you use? Maybe a too up to date version might cause troubles. I will give an update tomorrow regarding the linux kernel versions used in our setup. But we aren't using 6.x at least. |
The issue seems to be related to vsomeip >= 3.3.0. Downgrading to vsomeip 3.1.37.1 works fine for me. Here is a bit more of information about my environment
vsomeip >= 3.3.0 never joins the broadcast group and thus never gets the SD messages:
But also note that with vsomeip 3.1.37.1 I also get the error message mentioned in this thread:
|
Okay, thanks for the hint. I will check the concrete vsomeip version. |
Hey @dprogm, just a friendly ping to check whether have you had the time to look into this. |
Hi @hugojacob Sorry for not getting back to you quickly. I had no access to my workstation the last few weeks. I will check the SomeIP version tomorrow and give an update here. But I am pretty sure that we are using the dev state (HEAD of master) of the SomeIP library in conjunction with CommonAPI (see https://github.com/COVESA/capicxx-someip-tools/wiki/CommonAPI-C---SomeIP-in-10-minutes). I will pin the version and check again. |
@hugojacob Small update. I am using Version 3.3.8 and there is no error. I will check the concrete Version from my co-worker too. |
@dprogm the problem is still occurring? from your last comment, it seems not. cc @fcmonteiro |
The problem is still there, I see it, too. My setup:
I digged a bit deeper and found out some interesting things:
Log output with some custom trace messages:
Is it possible to re-open the issue? Seems like a retry mechanism would actually make sense. At least on environments dealing with Android Trout / virtualized network environments. However I have no idea how this causes the EBUSY. But it seems like the similarity between @hugojacob ' setup and mine. |
It seems to be the same as issue #607. There, the two hosts are a Linux-based machine and not AOSP 14 (as @elektronenhirn 's and my setup). |
@elektronenhirn did you try with the fix from #591 ? |
Hello everybody 😉
We are getting the following error on an ARM device which is running the service part. The following error is thrown on startup:
[info] Network interface "bridge0" state changed: up [error] netlink_connector::receive_cbk received error message: 2 seq 3
Normally we are expecting logging output regarding the routing/multicast.
This issue is actually a duplicate of #214, but it is slightly different and there is still no answer available.
We are thinking that this is the reason why the client is not able to connect to the service. Is there any requirement regarding IP addresses (range) or netmask? We are using the 10/8 address space.
Thanks in advance
The text was updated successfully, but these errors were encountered: