Hi Clovis, Since error says 500 internal server error, you have to look at the wso2carbon.log for server errors.
Thanks, Lakshman On Wed, May 24, 2017 at 6:12 AM, Clovis Wichoski <[email protected]> wrote: > Hi Lakshman, > > I reviewed and can build better with version tag 3.1.7 of the agent, the > problem before was about SSLv3 disabled on server, then on agent I forced > to use a lower version. Now I can do enrollment, but cant get the > notifications from server, debuging on device I get follow error: > > 05-23 20:41:43.474 2692-2692/org.wso2.iot.agent E/APIController: > {"code":500,"message":"Internal server error.","description":"The server > encountered an internal error. Please contact administrator.","moreInfo":"", > "error":[]} > 05-23 20:41:43.474 2692-2692/org.wso2.iot.agent E/APIController: > com.android.volley.ServerError > > I tried to enable some DEBUG log, but cant find a usefull message, appears > to be a problem at server side now on > org.wso2.carbon.device.mgt.mobile.android.api > plugin. > > on Server I got: > ==> core/repository/logs/http_access_2017-05-23.log <== > 10.0.0.4 - - [23/May/2017:20:52:11 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:20:54:30 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:20:55:50 -0300] "POST /oauth2/token HTTP/1.1" > 400 87 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:20:56:09 -0300] "POST > /services/APIKeyValidationService > HTTP/1.1" 200 3408 "-" "Axis2" > 10.0.0.4 - - [23/May/2017:20:56:09 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:20:56:49 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:20:58:20 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:20:59:59 -0300] "POST > /services/APIKeyValidationService > HTTP/1.1" 200 7832 "-" "Axis2" > 10.0.0.4 - - [23/May/2017:20:59:59 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:21:00:50 -0300] "POST /oauth2/token HTTP/1.1" > 400 87 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:21:02:11 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:21:03:46 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:21:04:12 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:21:05:52 -0300] "POST /oauth2/token HTTP/1.1" > 400 87 "-" "Synapse-PT-HttpComponents-NIO" > 10.0.0.4 - - [23/May/2017:21:06:01 -0300] "PUT > /api/device-mgt/android/v1.0/devices/17e2fad557210525/pending-operations > HTTP/1.1" 500 160 "-" "Synapse-PT-HttpComponents-NIO" > > Now I will try to check how to figure out why got these errors. > > Best regards. > > Clóvis > > > > Em 22 de mai de 2017 05:24, "Lakshman Udayakantha" <[email protected]> > escreveu: > > Hi Clovis, > > According to the compatibility doc [1], IOT 3.0.0 should work with agent > 2.0.0 version. Could you check the tag and build and see? Anyway, can you > see any error in log (server log or logcat)? > > [1] https://docs.wso2.com/display/IoTS300/WSO2+IoT+Server+an > d+Agent+Compatibility > > Thanks, > Lakshman. > > On Sun, May 21, 2017 at 7:41 PM, Clovis Wichoski <[email protected]> > wrote: > >> >> Hi, >> >> I'm try to configure and test with Sansung Tablet SM-T560 that uses >> Android Kitkat 4.4.4, when I try the application on emulator with same >> version all works fine, but when use with physical device dont get >> enrollment, I'm compiling the sources from git on branch release-2.0.0 (as >> I see that some changes in APIs dont worked with new branches) that work >> with version 3.0.0 of WSO2 IoTS. >> >> Can be any specific issue with physical devices that differ from >> emulator? Any clue? Maybe using another branch or tag? >> >> Best regards >> >> Clóvis >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Lakshman Udayakantha > WSO2 Inc. www.wso2.com > lean.enterprise.middleware > Mobile: *0717429601* > > > -- Lakshman Udayakantha WSO2 Inc. www.wso2.com lean.enterprise.middleware Mobile: *0717429601*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
