[gentoo-user] Connman refuses to work

[gentoo-user] Connman refuses to work

[Melleus]

After last system update my connman refuses to work. It throws a
message:
The name net.connman was not provided by any .service files

There is connman service installed in default runlevel. Connman version
is 1.29. I had not changed any configuration file before it stopped
working. I suspect that this is somehow tied with the questionable
design of the softwares related to systemd (I moved to Gentoo with
OpenRC to escape from systemd intervention). But I cannot really
understand what is happening. Does anybody have similar problem? How to
solve it?

Thanks ahead of time.

[gentoo-user] Re: Connman refuses to work

[Melleus]

Melleus <melleus@openmailbox.org> writes:

> working. I suspect that this is somehow tied with the questionable
> design of the softwares related to systemd (I moved to Gentoo with
> OpenRC to escape from systemd intervention). But I cannot really
> understand what is happening. Does anybody have similar problem? How to
> solve it?

I found that with stable keyword I have kernel version 4.9.72 and linux
headers version 4.13 installed on my system. But if they both keyworded
as stable there should not be any incompatibility? Or not?

Re: [gentoo-user] Connman refuses to work

[Rich Freeman]

On Sat, Jan 6, 2018 at 7:33 AM, Melleus <melleus@openmailbox.org> wrote:
> After last system update my connman refuses to work. It throws a
> message:
> The name net.connman was not provided by any .service files
>
> There is connman service installed in default runlevel. Connman version
> is 1.29. I had not changed any configuration file before it stopped
> working. I suspect that this is somehow tied with the questionable
> design of the softwares related to systemd (I moved to Gentoo with
> OpenRC to escape from systemd intervention). But I cannot really
> understand what is happening. Does anybody have similar problem? How to
> solve it?

What service manager are you actually using?  Are you actually booted
using openrc, or systemd?

-- 
Rich

[gentoo-user] Re: Connman refuses to work

[Melleus]

Rich Freeman <rich0@gentoo.org> writes:

> On Sat, Jan 6, 2018 at 7:33 AM, Melleus <melleus@openmailbox.org> wrote:
>> After last system update my connman refuses to work. It throws a
>> message:
>> The name net.connman was not provided by any .service files
>>
>> There is connman service installed in default runlevel. Connman version
>> is 1.29. I had not changed any configuration file before it stopped
>> working. I suspect that this is somehow tied with the questionable
>> design of the softwares related to systemd (I moved to Gentoo with
>> OpenRC to escape from systemd intervention). But I cannot really
>> understand what is happening. Does anybody have similar problem? How to
>> solve it?
>
> What service manager are you actually using?  Are you actually booted
> using openrc, or systemd?

I use openrc. Connman pretends to start, but when checking its status with:

/etc/init.d/connman status

I get

* status: crashed

message. So for some unclear reason it cannot start properly.

Re: [gentoo-user] Re: Connman refuses to work

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 466 bytes --]

On Sat, 06 Jan 2018 17:37:37 +0200, Melleus wrote:

> I use openrc. Connman pretends to start, but when checking its status
> with:
> 
> /etc/init.d/connman status
> 
> I get
> 
> * status: crashed
> 
> message. So for some unclear reason it cannot start properly.

What do the logs say?

Can you start it manually?


-- 
Neil Bothwick

Give a man a fish and you feed him for a day; teach him
to use the Net and he won't bother you for weeks.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: Connman refuses to work

[Melleus]

Neil Bothwick <neil@digimed.co.uk> writes:

> On Sat, 06 Jan 2018 17:37:37 +0200, Melleus wrote:
>
>> I use openrc. Connman pretends to start, but when checking its status
>> with:
>> 
>> /etc/init.d/connman status
>> 
>> I get
>> 
>> * status: crashed
>> 
>> message. So for some unclear reason it cannot start properly.
>
> What do the logs say?
That's all I could find in syslog:

connmand[6709]: Aborting (signal 11) [/usr/sbin/connmand]

> Can you start it manually?

No, it pretends to start but fails silently.

Re: [gentoo-user] Re: Connman refuses to work

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

On Sat, 06 Jan 2018 18:46:25 +0200, Melleus wrote:

> > What do the logs say?  
> That's all I could find in syslog:
> 
> connmand[6709]: Aborting (signal 11) [/usr/sbin/connmand]
> 
> > Can you start it manually?  
> 
> No, it pretends to start but fails silently.

Looking at the man page, try adding --debug=DEBUG and --nodaemon


-- 
Neil Bothwick

Physics is like sex: sure, it may give some practical results, but
  that's not why we do it.                            Richard Feynman

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[gentoo-user] Re: Connman refuses to work

[Melleus]

Neil Bothwick <neil@digimed.co.uk> writes:

> On Sat, 06 Jan 2018 18:46:25 +0200, Melleus wrote:
>
>> > What do the logs say?  
>> That's all I could find in syslog:
>> 
>> connmand[6709]: Aborting (signal 11) [/usr/sbin/connmand]
>> 
>> > Can you start it manually?  
>> 
>> No, it pretends to start but fails silently.
>
> Looking at the man page, try adding --debug=DEBUG and --nodaemon

Thank you for helping me.

--debug=DEBUG is almost silent, but just --debug is more verbose.

All I see is that something wrong is happening here:

connmand[2434]: src/iptables.c:__connman_iptables_append() -t mangle -A connman-INPUT -j CONNMARK --restore-mark
connmand[2434]: Aborting (signal 11) [connmand]

[gentoo-user] Re: Connman refuses to work

[Melleus]

Melleus <melleus@openmailbox.org> writes:

> Neil Bothwick <neil@digimed.co.uk> writes:
>
>> On Sat, 06 Jan 2018 18:46:25 +0200, Melleus wrote:
>>
>>> > What do the logs say?  
>>> That's all I could find in syslog:
>>> 
>>> connmand[6709]: Aborting (signal 11) [/usr/sbin/connmand]
>>> 
>>> > Can you start it manually?  
>>> 
>>> No, it pretends to start but fails silently.
>>
>> Looking at the man page, try adding --debug=DEBUG and --nodaemon
>
> Thank you for helping me.
>
> --debug=DEBUG is almost silent, but just --debug is more verbose.
>
> All I see is that something wrong is happening here:
>
> connmand[2434]: src/iptables.c:__connman_iptables_append() -t mangle -A connman-INPUT -j CONNMARK --restore-mark
> connmand[2434]: Aborting (signal 11) [connmand]

Thanks again for pointing me to logs. Those iptables was a
problem. There are the closed bug #573174. Iptables higher than 1.6
breaks connman. The solution is to use iptables lower than 1.6 or
connman higher than 1.32. So the combination of connman v1.29 and
iptables v1.6.1-r2 just cannot work. But unfortunately for me they both
have stable keyword. I beleive that this is a some kind of bug.
After I masked iptables higher than 1.6, reemerged the packages and
reboot, everything works like it should.

I don't know whether developers are reading this thread, but it would be
very nice to keyword only v1.4.21-r1 of iptables with stable keyword
(like they have done with kernel recently) or promote to stable some
version of connman higher than 1.32 upstream. This would completely
have this bug eliminated even before someone other than me hits it.

Re: [gentoo-user] Re: Connman refuses to work

[Alan McKinnon]

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


Post your finding to b.g.o.

It's a simple matter to limit which versions of iptables can be used
with each version of connman. Tracking that, and making changes when
they become known, is what being a package maintainer is all about.


-- 
Alan McKinnon
alan.mckinnon@gmail.com

[gentoo-user] Re: Connman refuses to work

[Melleus]

Alan McKinnon <alan.mckinnon@gmail.com> writes:

> On 07/01/2018 17:45, Melleus wrote:
>> Melleus <melleus@openmailbox.org> writes:
>> 
>>> Neil Bothwick <neil@digimed.co.uk> writes:
>>>
>>>> On Sat, 06 Jan 2018 18:46:25 +0200, Melleus wrote:
>>>>
>>>>>> What do the logs say?  
>>>>> That's all I could find in syslog:
>>>>>
>>>>> connmand[6709]: Aborting (signal 11) [/usr/sbin/connmand]
>>>>>
>>>>>> Can you start it manually?  
>>>>>
>>>>> No, it pretends to start but fails silently.
>>>>
>>>> Looking at the man page, try adding --debug=DEBUG and --nodaemon
>>>
>>> Thank you for helping me.
>>>
>>> --debug=DEBUG is almost silent, but just --debug is more verbose.
>>>
>>> All I see is that something wrong is happening here:
>>>
>>> connmand[2434]: src/iptables.c:__connman_iptables_append() -t mangle -A connman-INPUT -j CONNMARK --restore-mark
>>> connmand[2434]: Aborting (signal 11) [connmand]
>> 
>> Thanks again for pointing me to logs. Those iptables was a
>> problem. There are the closed bug #573174. Iptables higher than 1.6
>> breaks connman. The solution is to use iptables lower than 1.6 or
>> connman higher than 1.32. So the combination of connman v1.29 and
>> iptables v1.6.1-r2 just cannot work. But unfortunately for me they both
>> have stable keyword. I beleive that this is a some kind of bug.
>> After I masked iptables higher than 1.6, reemerged the packages and
>> reboot, everything works like it should.
>> 
>> I don't know whether developers are reading this thread, but it would be
>> very nice to keyword only v1.4.21-r1 of iptables with stable keyword
>> (like they have done with kernel recently) or promote to stable some
>> version of connman higher than 1.32 upstream. This would completely
>> have this bug eliminated even before someone other than me hits it.
>
>
> Post your finding to b.g.o.
>
> It's a simple matter to limit which versions of iptables can be used
> with each version of connman. Tracking that, and making changes when
> they become known, is what being a package maintainer is all about.

connman-1.35-r1 arrives to stable. So no need to tinker with iptables
version anymore. The issue dissolved completely.