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