10:40 p.m.
I'm using ConnMan in an ARM embedded Linux system (based on BeagleBone Black).
For a long time, with systems using Linux kernel 3.14.x and 4.4.x, it has been working
very well. Recently, I have done some work to upgrade to Linux kernel 4.9.x. With this
kernel, ConnMan sometimes terminates and restarts shortly after start-up, something that I
don't think it did before.
At least, I think the change is related to the kernel upgrade. The system has also had
other upgrades to other components, but the kernel update seems like the most likely
cause.
Examining recent system logs, I see this message appears shortly before a ConnMan
restart:
Jan 29 17:25:34 wt000043 daemon.err connmand[19746]: Inconsistent IP pool management
(start not found)
Shortly after that message, ConnMan shuts down. Usually it restarts, and everything is
fine. But occasionally, ConnMan never restarts, and the system has no network
connectivity.
What might be a cause for this error? I see in the source code, function
__connman_ippool_deladdr() contains:
info = lookup_info(index, start);
if (!info) {
/* In theory this should never happen */
connman_error("Inconsistent IP pool management (start not found)");
return;
}
--
Craig McQueen
12:41 a.m.
Hi Craig,
Jan 29 17:25:34 wt000043 daemon.err connmand[19746]: Inconsistent IP pool management
(start not found)
Shortly after that message, ConnMan shuts down. Usually it restarts,
and everything is fine. But occasionally, ConnMan never restarts, and
the system has no network connectivity.
If ConnMan crashes, something like systemd will probably restart.
ConnMan can't restart itself.
The error message indicates, that we have a problem finding a
empty IP range in the private address space (192.168.0.0/16, ...).
So we either have a bug in the code trying to find an empty block
or the current network configuration is covering all the private address
ranges and the logic can't find any block.
What might be a cause for this error? I see in the source code,
function __connman_ippool_deladdr() contains:
info = lookup_info(index, start);
if (!info) {
/* In theory this should never happen */
connman_error("Inconsistent IP pool management (start not found)");
return;
Hard to tell without the log. Can you post the log output of ConnMan (or
a post a link the log)? Also the output of 'ip addr' and 'ip route'
would be handy.
Thanks,
Daniel
8:21 p.m.
Daniel Wagner wrote:
Hi Craig,
>
> Jan 29 17:25:34 wt000043 daemon.err connmand[19746]: Inconsistent
> IP pool management (start not found)
>
> Shortly after that message, ConnMan shuts down. Usually it restarts,
> and everything is fine. But occasionally, ConnMan never restarts, and
> the system has no network connectivity.
If ConnMan crashes, something like systemd will probably restart.
ConnMan can't restart itself.
Thanks for explaining. You are right, it turns out it is a system initscript that was
restarting ConnMan (due to a network configuration occurring shortly after power-up). (I
am using initscripts, not system.)
The initscript restart was doing a stop, then a sleep for 1 second, then a start (this is
an initscript from the Yocto project). But, the stop wasn't actually waiting for
connmand to shutdown, so when the start occurred, it failed due to the
not-yet-fully-stopped connmand that was still running.
I have improved the initscript so that the stop operation waits until connmand really has
stopped.
I should also mention, that with ConnMan 1.32, I simply never saw it restart. With ConnMan
1.35, I saw the new instance of ConnMan SEGFAULT. Perhaps the SEGFAULT is worth
investigating.
> Jan 29 17:25:34 wt000043 daemon.err connmand[19746]:
Inconsistent
> IP pool management (start not found)
The error message indicates, that we have a problem finding a empty IP
range in the private address space (192.168.0.0/16, ...).
So we either have a bug in the code trying to find an empty block or the
current network configuration is covering all the private address ranges and
the logic can't find any block.
It seems that this error message was a red herring in my problem.
> What might be a cause for this error? I see in the source code,
function
__connman_ippool_deladdr() contains:
>
> info = lookup_info(index, start);
> if (!info) {
> /* In theory this should never happen */
> connman_error("Inconsistent IP pool management (start not
found)");
> return;
Hard to tell without the log. Can you post the log output of ConnMan (or a
post a link the log)? Also the output of 'ip addr' and 'ip route'
would be handy.
My immediate problem is solved I think, but I would still be happy to provide logs if you
wish to diagnose the "Inconsistent IP pool management (start not found)" error
message. Would you like me to send logs?
--
Craig McQueen
10:24 p.m.
Hi Craig,
The initscript restart was doing a stop, then a sleep for 1 second,
then a start (this is an initscript from the Yocto project). But, the
stop wasn't actually waiting for connmand to shutdown, so when the
start occurred, it failed due to the not-yet-fully-stopped connmand
that was still running.
I see. ConnMan doesn't like that :)
My immediate problem is solved I think, but I would still be happy
to provide logs if you wish to diagnose the "Inconsistent IP pool
management (start not found)" error message. Would you like me to send logs?
If you still have the logs around, yes please. Maybe there is something
obvious wrong and we can fix it.
Thanks,
Daniel
964
days inactive
979
days old
3 comments
2 participants
participants (2)
-
Craig McQueen -
Daniel Wagner