Hi, I am unable to reproduce your crash. I assume you did a "make cleanall" before you rebuilt the stack. Also, I assume you're using the latest source.
> I tried to provision the ACE as you suggested but the error code now is the > same when I run the apps without using the OBT: 17 > > The OBT crashes every time I select option 4 (Discover owned devices), > regardless of any > previous step. Well, if you were able to provision the ACE, then you'd have to have used options 4/5/6 to discover an owned device first. So, your 2nd statement wouldn't be accurate. It suggests that option 4 worked for you once without crashing, and it then somehow stopped working??? Also, if you saw error code 17, then it suggests that you probably did not provision a credential at all to the Client and the Server. Try this after a fresh build: -Run the OBT, Client and Server. -Use option 1 to discover the unowned Client and Server. -Use option 7 twice to onboard the Client and Server. -Use option 4 to discover the owned Client and Server. -Use option 11 to provision pairwise credentials to the Client and Server. -Use option 13 twice to provision an ACE to both the devices. (Only the Server needs an ACE. But I see that simpleclient/simpleserver do not configure a device name for you to able to distinguish one from the other, as you only see their UUIDs. So, for sake of simplicity in your current testing, you can provision it to both) After this, the Client and Server should be able to communicate. If you're still seeing a crash, then I'd have to look at logs and a backtrace from gdb captured with a DEBUG=1 build to make sense of your situation. What OS/machine are you using? Are the OBT, Client and Server all running on the same machine? Thanks, -Kishen. -- Kishen Maloor Intel Corporation From: Thiago Moura <thiago...@gmail.com> Date: Tuesday, August 27, 2019 at 9:32 AM To: "Maloor, Kishen" <kishen.mal...@intel.com> Cc: iotivity-dev <iotivity-dev@lists.iotivity.org> Subject: Re: [dev] OBT Crash Hi Kishen Thanks for the prompt reply. I tried to provision the ACE as you suggested but the error code now is the same when I run the apps without using the OBT: 17 The OBT crashes every time I select option 4 (Discover owned devices), regardless of any previous step. I built with DEBUG option now. These are logs just before the crash: DEBUG: ../../messaging/coap/coap.c <coap_parse_token_option:815>: -Done parsing------- DEBUG: ../../messaging/coap/engine.c <coap_receive:167>: Parsed: CoAP version: 1, token: 0x81B2, mid: 23612 DEBUG: ../../messaging/coap/engine.c <coap_receive:175>: type: NON DEBUG: ../../messaging/coap/engine.c <coap_receive:589>: created new response buffer for uri oic/res DEBUG: ../../messaging/coap/engine.c <coap_receive:639>: calling oc_ri_invoke_client_cb [1] 22738 segmentation fault (core dumped) ./onboarding_tool On Tue, Aug 27, 2019 at 12:28 PM Maloor, Kishen <kishen.mal...@intel.com<mailto:kishen.mal...@intel.com>> wrote: Hi, > I'm experimenting the latest changes on iotivity-lite and cannot run the > simpleclient / server apps. > First, when I use the pairwise credential option, the server returns error > code 6. You have to both provision credentials and provision an access control entry (ACE) to the server (option 12 or 13 - 13 is simpler) for the two to communicate. Error code 6 maps to OC_STATUS_UNAUTHORIZED. So it seems you only provisioned credentials, but did not provision the ACE. > And if I select the option to discover owned devices to try a different > provision, the OBT chash. Did it crash soon after you used options 4/5/6 to discover owned devices? It would be great if this were reproducible, and you could provide the exact sequence of options you used in the tool. > Is this a known issue? No. Thanks, -Kishen. -- Kishen Maloor Intel Corporation From: <iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>> on behalf of Thiago Moura <thiago...@gmail.com<mailto:thiago...@gmail.com>> Date: Tuesday, August 27, 2019 at 7:50 AM To: iotivity-dev <iotivity-dev@lists.iotivity.org<mailto:iotivity-dev@lists.iotivity.org>> Subject: [dev] OBT Crash Hi I'm experimenting the latest changes on iotivity-lite and cannot run the simpleclient / server apps. First, when I use the pairwise credential option, the server returns error code 6. And if I select the option to discover owned devices to try a different provision, the OBT chash. Is this a known issue? regards, -- Thiago Guedes Cunha de Moura cel.: (31)99484-9864 -- Thiago Guedes Cunha de Moura cel.: (31)99484-9864 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10272): https://lists.iotivity.org/g/iotivity-dev/message/10272 Mute This Topic: https://lists.iotivity.org/mt/33046681/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
