Hi Mike, On pe, 2014-07-11 at 17:11 -0400, Mike Purvis wrote: > Hi Jukka, > > > I'm not sure what has happened to my installed connman, but I now seem > unable to command it at all: > > > $ connmanctl connect wifi_c4d987b634ba_4c562d343236_managed_psk > Error /net/connman/service/wifi_c4d987b634ba_4c562d343236_managed_psk: > Rejected send message, 2 matched rules; type="method_call", > sender=":1.12" (uid=1000 pid=1717 comm="connmanctl connect > wifi_c4d987b634ba_4c562d343236_") interface="net.connman.Service" > member="Connect" error name="(unset)" requested_reply="0" > destination="net.connman" (uid=0 pid=642 comm="connmand --nobacktrace > -I p5p1 ") >
I have never seen this error. Did this work earlier and you have not upgraded your dbus or rest of the system? Anyway, this does not look like a connman issue. > > This looks like a dbus permissions problem, so I tried sudo: > > > $ sudo connmanctl connect wifi_c4d987b634ba_4c562d343236_managed_psk > Error /net/connman/service/wifi_c4d987b634ba_4c562d343236_managed_psk: > Input/output error This looks like your wifi AP was not found in the scans so the connect just failed because of that. Make sure you see your AP in "connmanctl services" list before trying to connect, otherwise the connect will just fail. > > > I stopped the upstart job and launched connman in the foreground: > > > $ sudo connmand -d -n -I p5p1 > > > > There's a lot of debug output; I've captured it in a file > here: https://gist.github.com/mikepurvis/bfd728f76a660223bbe4 > There is lot of data but I could not pin point any obvious errors in the log. The p5p1 interface is ignored correctly. The log also says that system tries to auto connect to LV-426, but dhcp server does not give a lease. Then the log ends so I do not know what happened next. Cheers, Jukka > > Thoughts? > > > On 8 July 2014 08:42, Jukka Rissanen <[email protected]> > wrote: > Hi Mike, > > On ti, 2014-07-08 at 08:33 -0400, Mike Purvis wrote: > > > I also tried moving my service definition > > > to /var/lib/connman/example.config, but this > registered no > > response > > > either. > > > > > > So you are saying that even with this file, the > system does > > not set the > > IP address of the ethernet interface when you plug > in the > > ethernet > > cable? Note that ethernet cable (with other end > connected to > > switch) > > needs to be plugged in before connman will handle > the > > interface. > > If so, please supply debug log of the issue (use > pastebin or > > similar > > service for the log file). Start connman with -d > option to get > > the debug > > log. > > > > > > Ah, didn't realise the cable still had to be connected in > order to get > > the static IP. In that case, I'll probably stick to just > managing the > > interface outside of connman— particularly because I'm > getting some > > instability with v1.24, resulting in the daemon needing to > be > > restarted every 30-60mins or so. I'd prefer not to lose my > static SSH > > port while restarting connman. > > > > > > When I have a clearer sense of what's going on with that > problem, I'll > > post some logs and start a new thread. > > > Please do report any issues if possible. The latest version > has been > very stable for me so would be very interested to see your > issues. > > > Cheers, > Jukka > > > > > _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
