My apology, that was not exactly right, please ignore my previous email. I tried to edit ExecStart=/usr/sbin/connmand -n -d, it was running fine, but still could not bring networks up, the ExecStart=/usr/sbin/connmand -d did not work obviously that was not right. So it is not just increase the debug level which could bring all networks up, it was running the connmand -d in a terminal shell command line that could bring all networks up. It is really puzzled, why running commond -d in a terminate shell command line works, but could not work with systemd service? missing some environment setup? Thank you. - jh On 10/22/19, JH <jupiter.hce(a)gmail.com&gt; wrote: > Hi David, > > How did you edit the service file to add -d? Also, how could you added > -d to service file in Yocto recipe? > > I could not start connman after added -d > > # vi /lib/systemd/system/connman.service > ExecStart=/usr/sbin/connmand -n -d > > Job for connman.service failed because the control process exited with > error code. > See "systemctl status connman.service" and "journalctl -xe" for details. > > Thank you. > > Kind regards > On 10/22/19, David Weidenkopf <David.Weidenkopf(a)arthrex.com&gt; wrote: >> Hi, >> >> We use a yocto build as well. I routinely edit the service file to add -d >> to > How did you edit the service file to add -d? Also, how could you added > -d to service file in Yocto recipe? > > I could not start connman after added -d > > # vi /lib/systemd/system/connman.service > ExecStart=/usr/sbin/connmand -n -d > > Job for connman.service failed because the control process exited with > error code. > See "systemctl status connman.service" and "journalctl -xe" for details. > >> increase logging. We don't use LTE, just WiFi. > > I am using both WiFi and LTE, both could not come up in systemd > service, i could only bring them up run the connmand -d manually. > >> Can you confirm exactly the steps you are trying and the expected result? > > Is it the right way to edit connman.service above? > > Thanks David. > >> David >> ________________________________________ >> From: JH [jupiter.hce(a)gmail.com] >> Sent: Monday, October 21, 2019 2:41 AM >> To: David Weidenkopf >> Cc: Daniel Wagner; connman >> Subject: Re: Insights on connmand -d >> >> Hi Daniel and David, >> >> The connman was built by Yocto recipe, automatically launched by >> systemd service set up by the Yocto connman recipe. >> >> Any suggestion how to fix that issue or any workarounds? The connman >> is installed in an embedded device, currently I use the debug port to >> access the device and to stop systemd connman and to run command -d >> manually, it is not feasible to do it when a device is installed >> remotely. >> >> Thank you. >> >> Kind regards, >> >> - jh >> >> >> >> On 10/2/19, JH <jupiter.hce(a)gmail.com&gt; wrote: >>> On 10/2/19, David Weidenkopf <David.Weidenkopf(a)arthrex.com&gt; wrote: >>>> What user are you running connmand -d as? What user is the service >>>> running >>>> as when you launch using systemctl? >>> >>> Running root in connmand -d and root for systemctl for connman.service >>> in imx6 platform. >>> >>> Thanks David. >>> >>>> >>>> ________________________________________ >>>> From: JH [jupiter.hce(a)gmail.com] >>>> Sent: Monday, September 30, 2019 6:49 PM >>>> To: Daniel Wagner >>>> Cc: connman >>>> Subject: Re: Insights on connmand -d >>>> >>>> Hi Daniel, >>>> >>>> On 10/1/19, Daniel Wagner <wagi(a)monom.org&gt; wrote: >>>>> Hi, >>>>> >>>>> On 9/30/19 12:51 AM, JH wrote: >>>>>> Could anyone give some insights on what connmand -d differs to >>>>>> connmand -n running by systemctl? From reading the documentation, my >>>>>> understanding is it should be identical except increasing debug level >>>>>> to printing out more debug messages, but the systemd service connmand >>>>>> -n incapable of bringing my LTE modem up makes my wandering what I >>>>>> could get wrong here, could the connman -n service messages be >>>>>> blocked >>>>>> by journal logs? Appreciate anyone helps to fix it, >>>>> >>>>> Yes the behavior of ConnMan doesn't change with or without '-d'. It >>>>> executes the exact same code. It's more like enabling a fancy function >>>>> tracer. >>>> >>>> That completed puzzled me, the LTE modem could not be up until I run >>>> systemctl stop connman and connmand -d. It is the latest version 1.36. >>>> >>>> >>>>> I don't know if journald blocks if the logging store gets full or not. >>>>> But you could try to increase the log buffer for testing. Just to rule >>>>> out this problem. >>>> >>>> Changed journald log buffer size, it did not help. Any suggestion how >>>> to debug and fix it? >>>> >>>> Thank you Daniel. >>>> >>>> Kind regards, >>>> _______________________________________________ >>>> connman mailing list -- connman(a)lists.01.org >>>> To unsubscribe send an email to connman-leave(a)lists.01.org >>>> This e-mail and any files transmitted with it are the property of >>>> Arthrex, >>>> Inc. and/or its affiliates, are confidential, and are intended solely >>>> for >>>> the use of the individual or entity to whom this e-mail is addressed. >>>> If >>>> you >>>> are not one of the named recipient(s) or otherwise have reason to >>>> believe >>>> that you have received this message in error, please notify the sender >>>> at >>>> 239-643-5553 and delete this message immediately from your computer. >>>> Any >>>> other use, retention, dissemination forwarding, printing or copying of >>>> this >>>> e-mail is strictly prohibited. Please note that any views or opinions >>>> presented in this email are solely those of the author and do not >>>> necessarily represent those of the company. Finally, while Arthrex uses >>>> virus protection, the recipient should check this email and any >>>> attachments >>>> for the presence of viruses. The company accepts no liability for any >>>> damage >>>> caused by any virus transmitted by this email. >>>> >>> >> This e-mail and any files transmitted with it are the property of >> Arthrex, >> Inc. and/or its affiliates, are confidential, and are intended solely for >> the use of the individual or entity to whom this e-mail is addressed. If >> you >> are not one of the named recipient(s) or otherwise have reason to believe >> that you have received this message in error, please notify the sender at >> 239-643-5553 and delete this message immediately from your computer. Any >> other use, retention, dissemination forwarding, printing or copying of >> this >> e-mail is strictly prohibited. Please note that any views or opinions >> presented in this email are solely those of the author and do not >> necessarily represent those of the company. Finally, while Arthrex uses >> virus protection, the recipient should check this email and any >> attachments >> for the presence of viruses. The company accepts no liability for any >> damage >> caused by any virus transmitted by this email. >> >