1 |
Alan McKinnon <alan.mckinnon@×××××.com> writes: |
2 |
|
3 |
> On 07/01/2018 17:45, Melleus wrote: |
4 |
>> Melleus <melleus@×××××××××××.org> writes: |
5 |
>> |
6 |
>>> Neil Bothwick <neil@××××××××××.uk> writes: |
7 |
>>> |
8 |
>>>> On Sat, 06 Jan 2018 18:46:25 +0200, Melleus wrote: |
9 |
>>>> |
10 |
>>>>>> What do the logs say? |
11 |
>>>>> That's all I could find in syslog: |
12 |
>>>>> |
13 |
>>>>> connmand[6709]: Aborting (signal 11) [/usr/sbin/connmand] |
14 |
>>>>> |
15 |
>>>>>> Can you start it manually? |
16 |
>>>>> |
17 |
>>>>> No, it pretends to start but fails silently. |
18 |
>>>> |
19 |
>>>> Looking at the man page, try adding --debug=DEBUG and --nodaemon |
20 |
>>> |
21 |
>>> Thank you for helping me. |
22 |
>>> |
23 |
>>> --debug=DEBUG is almost silent, but just --debug is more verbose. |
24 |
>>> |
25 |
>>> All I see is that something wrong is happening here: |
26 |
>>> |
27 |
>>> connmand[2434]: src/iptables.c:__connman_iptables_append() -t mangle -A connman-INPUT -j CONNMARK --restore-mark |
28 |
>>> connmand[2434]: Aborting (signal 11) [connmand] |
29 |
>> |
30 |
>> Thanks again for pointing me to logs. Those iptables was a |
31 |
>> problem. There are the closed bug #573174. Iptables higher than 1.6 |
32 |
>> breaks connman. The solution is to use iptables lower than 1.6 or |
33 |
>> connman higher than 1.32. So the combination of connman v1.29 and |
34 |
>> iptables v1.6.1-r2 just cannot work. But unfortunately for me they both |
35 |
>> have stable keyword. I beleive that this is a some kind of bug. |
36 |
>> After I masked iptables higher than 1.6, reemerged the packages and |
37 |
>> reboot, everything works like it should. |
38 |
>> |
39 |
>> I don't know whether developers are reading this thread, but it would be |
40 |
>> very nice to keyword only v1.4.21-r1 of iptables with stable keyword |
41 |
>> (like they have done with kernel recently) or promote to stable some |
42 |
>> version of connman higher than 1.32 upstream. This would completely |
43 |
>> have this bug eliminated even before someone other than me hits it. |
44 |
> |
45 |
> |
46 |
> Post your finding to b.g.o. |
47 |
> |
48 |
> It's a simple matter to limit which versions of iptables can be used |
49 |
> with each version of connman. Tracking that, and making changes when |
50 |
> they become known, is what being a package maintainer is all about. |
51 |
|
52 |
connman-1.35-r1 arrives to stable. So no need to tinker with iptables |
53 |
version anymore. The issue dissolved completely. |