Hi folks, I'm blocked in verifying some of my changes because the "provisioningclient" apps seems to no longer work on 1.3-rel (72e1ab0da3a9ce08e5423b64cb793b3b57493587). Discovery of the unowned device works, but when I try to do JustWorks owner transfer I get:
"09:22.701 DEBUG: OIC_OTM: In DTLSHandshakeCB(endpoint = 0x1934678, info = 0x7f3888087360) 09:22.701 INFO: OIC_OTM: Received status from remote device(fe80::fdfe:3ae0:2a84:fd81%ens33:47305) : 0 09:22.701 DEBUG: OIC_OTM_CTX: IN GetOTMContext 09:22.701 DEBUG: OIC_OTM_CTX: Found the OTMContext for [fe80::fdfe:3ae0:2a84:fd81%ens33:47305] 09:22.701 DEBUG: OIC_OTM: IN OwnershipTransferSessionEstablished 09:22.701 DEBUG: OIC_OTM: IN GetAndVerifyDoxmResource 09:22.701 DEBUG: OIC_OTM: Query=coaps://[fe80::fdfe:3ae0:2a84:fd81%25ens33]:47305/oic/sec/doxm 09:22.701 INFO: OIC_RI_STACK: Entering OCDoResource 09:22.701 DEBUG: OIC_RI_STACK: OCDoRequest: adapter = 1, flags = 48 09:22.701 DEBUG: OIC_RI_STACK: remoteId of devAddr : 09:22.701 DEBUG: OIC_CA_CONN_MGR: CAGenerateToken 09:22.705 DEBUG: OIC_CA_PRTCL_MSG: token len:8, token: 09:22.705 DEBUG: OIC_CA_PRTCL_MSG: 8F 83 76 E2 0D 08 C2 A7 09:22.705 INFO: OIC_RI_CLIENTCB: Adding client callback with token 09:22.705 INFO: OIC_RI_CLIENTCB: 8F 83 76 E2 0D 08 C2 A7 09:22.705 INFO: OIC_RI_CLIENTCB: Added Callback for uri : /oic/sec/doxm 09:22.705 DEBUG: OIC_CA_CONN_MGR: IN CAGetSecurePeerInfo 09:22.705 DEBUG: OIC_CA_CONN_MGR: OUT CAGetSecurePeerInfo 09:22.705 DEBUG: OIC_CA_NET_SSL: In GetCASecureEndpointData" ...and there it hangs. This code appears to use the g_sslContextMutex and by appearances is hanging on that oc_mutex_lock() call. Is this a known issue and is anyone working on it? Thanks, Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170421/8ef24632/attachment.html>
