Main process exited, code=exited, status=242/NUMA_POLICY #13550
Replies: 2 comments
|
This is expected behavior by design and not a bug. 1. What Exit Code
|
|
Thanks, it's all clear! |
|
This is expected behavior by design and not a bug. 1. What Exit Code
|
|
Thanks, it's all clear! |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello,
Description of the issue
I'm creating this issue, because if we start otbr-agent without any ethernet or wifi interface connected, then when we connect the ethernet cable in the interface, otbr-agent switch to ethernet interface, but it seems to be stopped with error code 242.
We just would like to know if it is a normal situation or a bug ?
How we start otbr-agent
We start ot-br-agent like this:
We have multiple backbone interface and for the tests they are disconnected on startup and connected at some point.
Some logs
Logs that appear when the ethernet cable is connected:
Logs with strace:
What I understand
The message from systemd, seems to be a wrong interpretation of the returned value of the application.
We see in strace that the application return -14.
And
-14 = 242 = OT_ERROR_NO_ACKdepending on the signed/unsigned form of 8 bits integer.Is it normal to exit with OT_ERROR_NO_ACK in such situation ?
Unique issue that I found with the
242/NUMA_POLICYpattern was: openthread/ot-br-posix#2152 and it also threat about dynamic changes of backbone interfaces 💃Note:
Except this, otbr-agent works perfectly, we are running like this since the begining maybe.
In our side we just want to make sure that this is not a bug, in other terms we wan't to make sure that "stopping otbr-agent with exit code 242/-14 is wanted/normal in this situation"
All reactions