2017-10-30 6 views
1

ich auf WSO2 IOT-Server 3.1.0 festgelegt haben, aber ich kann keine Daten wischen:WSO2: Daten können nicht wischen

Erreur in Benachrichtigung: WIPE_DATA Vorgang ist fehlgeschlagen auf Gerät xxx (ID auszuführen : xxxxxx)

Können Sie mir helfen? danke.


Hier ist Protokolle.

11-09 15:48:34.912 24757 24757 D org.wso2.iot.agent.services.AlarmReceiver: Recurring alarm; requesting alarm service. 
11-09 15:48:34.923 24757 27610 D OperationManager: New OperationManager created. 

11-09 15:48:34.924 24757 27610 I MessageProcessor: Get pending operations from:http://xx.xx.xx.xx:8280/api/device-mgt/android/v1.0/devices/2bd583e008ccbf2f/pending-operations 
11-09 15:48:34.925 24757 27610 D MessageProcessor: Reply Payload: [] 
11-09 15:48:34.926 24757 27610 D APIController: APIController created. 
11-09 15:48:34.926 24757 27610 D APIController: invokeAPI called 
11-09 15:48:34.926 24757 27610 D IdentityProxy: requestToken called. 
11-09 15:48:34.926 24757 27610 D IdentityProxy: token is expired false 
11-09 15:48:34.926 24757 27610 D IdentityProxy: token expiry Thu Nov 09 15:50:42 GMT+01:00 2017 
11-09 15:48:34.926 24757 27610 D IdentityProxy: Using Access Token: efc13b79-ffba-334f-84a1-62b4eaa4fff7 
11-09 15:48:34.936 24757 25055 D APIController: Retrieved token expires on:Thu Nov 09 15:50:42 GMT+01:00 2017 
11-09 15:48:34.938 24757 25055 I System.out: (HTTPLog)-Static: isSBSettingEnabled false 
11-09 15:48:34.938 24757 25055 I System.out: (HTTPLog)-Static: isSBSettingEnabled false 
11-09 15:48:35.002 24757 25055 D APIController: Result :[{"enabled":true,"code":"APPLICATION_LIST","type":"COMMAND","id":107,"status":"PENDING","createdTimeStamp":"2017-11-09 15:48:25.862","isEnabled":false},{"code":"WIPE_DATA","type":"PROFILE","id":106,"status":"PENDING","createdTimeStamp":"2017-11-09 15:47:46.023","isEnabled":true,"payLoad":"{\"pin\":\"3381\"}"}] 
11-09 15:48:35.005 24757 25055 D MessageProcessor: Pending Operations List: [{"enabled":true,"code":"APPLICATION_LIST","type":"COMMAND","id":107,"status":"PENDING","createdTimeStamp":"2017-11-09 15:48:25.862","isEnabled":false},{"code":"WIPE_DATA","type":"PROFILE","id":106,"status":"PENDING","createdTimeStamp":"2017-11-09 15:47:46.023","isEnabled":true,"payLoad":"{\"pin\":\"3381\"}"}] 
11-09 15:48:35.017 24757 25055 D MessageProcessor: Restarting to send quick update of received pending operations. 
11-09 15:48:35.020 24757 25055 I LocalNotification: Polling stopped! 
11-09 15:48:35.025 24757 25055 I LocalNotification: Polling started! Interval: 30000 
11-09 15:48:35.727 24757 24757 D LocationService: Status changed to: 2 Provider: gps 
11-09 15:48:36.113 24757 25055 D OperationManager: Application list sent 
11-09 15:48:36.114 24757 25055 D OperationManagerBYOD: Started to wipe data 
11-09 15:48:36.116 24757 24757 D APIController: [{"enabled":true,"code":"APPLICATION_LIST","type":"COMMAND","id":107,"status":"PENDING","createdTimeStamp":"2017-11-09 15:48:25.862","isEnabled":false},{"code":"WIPE_DATA","type":"PROFILE","id":106,"status":"PENDING","createdTimeStamp":"2017-11-09 15:47:46.023","isEnabled":true,"payLoad":"{\"pin\":\"3381\"}"}] 
11-09 15:48:36.662 24757 24757 D org.wso2.iot.agent.services.AlarmReceiver: Recurring alarm; requesting alarm service. 
11-09 15:48:36.669 24757 27621 D OperationManager: New OperationManager created. 

11-09 15:48:36.670 24757 27621 I MessageProcessor: Get pending operations from:http://xx.xx.xx.xx:8280/api/device-mgt/android/v1.0/devices/2bd583e008ccbf2f/pending-operations 
11-09 15:48:36.680 24757 27621 D MessageProcessor: Reply Payload: [{"code":"APPLICATION_LIST","complianceType":null,"createdTimeStamp":"2017-11-09 15:48:25.862","enabled":true,"id":107,"operationResponse":"[{\"name\":\"ES%20Explorateur%20de%20Fichiers\",\"package\":\"com.estrongs.android.pop\",\"version\":\"4.1.6.9.6\",\"isSystemApp\":false,\"isActive\":false},{\"name\":\"ipconfig\",\"package\":\"com.mankind.ipconfig\",\"version\":\"1.1\",\"isSystemApp\":false,\"isActive\":false},{\"name\":\"WSO2%20Device%20Management%20Agent\",\"package\":\"org.wso2.iot.agent\",\"version\":\"3.1.21\",\"isSystemApp\":false,\"isActive\":true,\"USS\":30948},{\"name\":\"Google%20Play%20services%20for%20Instant%20Apps\",\"package\":\"com.google.android.instantapps.supervisor\",\"version\":\"2.3-release-174342078\",\"isSystemApp\":false,\"isActive\":false},{\"name\":\"QR%20Scanner\",\"package\":\"com.application_4u.qrcode.barcode\",\"version\":\"1.9.6\",\"isSystemApp\":false,\"isActive\":false}]","payLoad":null,"receivedTimeStamp":null,"status":"COMPLETED","type":"COMMAND"},{"code":"WIPE_DATA","complianceType":null,"createdTimeStamp":"2017-11-09 15:47:46.023","enabled":false,"id":106,"operationResponse":null,"payLoad":{"status":"true"},"receivedTimeStamp":null,"status":"COMPLETED","type":"PROFILE"}] 
11-09 15:48:36.681 24757 27621 D APIController: APIController created. 
11-09 15:48:36.681 24757 27621 D APIController: invokeAPI called 
11-09 15:48:36.681 24757 27621 D IdentityProxy: requestToken called. 
11-09 15:48:36.681 24757 27621 D IdentityProxy: token is expired false 
11-09 15:48:36.681 24757 27621 D IdentityProxy: token expiry Thu Nov 09 15:50:42 GMT+01:00 2017 
11-09 15:48:36.681 24757 27621 D IdentityProxy: Using Access Token: efc13b79-ffba-334f-84a1-62b4eaa4fff7 
11-09 15:48:36.686 24757 25057 D APIController: Retrieved token expires on:Thu Nov 09 15:50:42 GMT+01:00 2017 
11-09 15:48:36.688 24757 25057 I System.out: (HTTPLog)-Static: isSBSettingEnabled false 
11-09 15:48:36.688 24757 24757 D LocationService: Location changed> lat:47.2659288 lon:-1.4888419 provider:network 
11-09 15:48:36.688 24757 25057 I System.out: (HTTPLog)-Static: isSBSettingEnabled false 
11-09 15:48:36.694 24757 24757 D APIController: APIController created. 
11-09 15:48:36.694 24757 24757 D APIController: invokeAPI called 
11-09 15:48:36.694 24757 24757 D IdentityProxy: requestToken called. 
11-09 15:48:36.694 24757 24757 D IdentityProxy: token is expired false 
11-09 15:48:36.694 24757 24757 D IdentityProxy: token expiry Thu Nov 09 15:50:42 GMT+01:00 2017 
11-09 15:48:36.694 24757 24757 D IdentityProxy: Using Access Token: efc13b79-ffba-334f-84a1-62b4eaa4fff7 
11-09 15:48:36.695 24757 24757 D LocationService: Location Event is published. 
11-09 15:48:36.697 24757 25056 D APIController: Retrieved token expires on:Thu Nov 09 15:50:42 GMT+01:00 2017 
11-09 15:48:36.698 24757 25056 I System.out: (HTTPLog)-Static: isSBSettingEnabled false 
11-09 15:48:36.699 24757 25056 I System.out: (HTTPLog)-Static: isSBSettingEnabled false 
11-09 15:48:36.700 24757 24757 D LocationService: Location changed> lat:47.2659288 lon:-1.4888419 provider:network 
11-09 15:48:36.702 24757 24757 D LocationService: Ignore publishing. Duplicate location timestamp. 
11-09 15:48:36.704 24757 24757 D LocationUpdateReceiver: Location> Lat:47.2659288 Lon:-1.4888419 Provider:network 
11-09 15:48:36.707 24757 25058 I System.out: (HTTPLog)-Static: isSBSettingEnabled false 
11-09 15:48:36.707 24757 25058 I System.out: (HTTPLog)-Static: isSBSettingEnabled false 
11-09 15:48:36.709 24757 24757 D LocationUpdateReceiver: Location> Lat:47.2659288 Lon:-1.4888419 Provider:network 
11-09 15:48:36.733 24757 24757 D LocationService: Status changed to: 2 Provider: gps 
11-09 15:48:36.751 24757 25056 D APIController: Result :{"responseCode":"Event is published successfully."} 
11-09 15:48:36.751 24757 25056 D org.wso2.iot.agent.events.publisher.HttpDataPublisher: Result for request: 312 is 201 
11-09 15:48:36.753 24757 24757 D APIController: {"responseCode":"Event is published successfully."} 

In Protokollen scheint alles in Ordnung zu sein. Danke für Hilfe.

+0

ist das iOS oder Android? –

+0

Können Sie auch feststellen, ob es sich um ein Client-seitiges Protokoll oder ein Serverprotokoll handelt? Wenn dies ein Client-seitiges Protokoll ist, können Sie die Umgebung beschreiben? zB Gerätetyp, OS-Version Haben Sie auch ein anderes Gerät getestet und sehen konsistente Ergebnisse? –

+0

Es ist Android. Es ist ein Serverprotokoll. Ich habe keine weiteren Details, da sich das Protokoll in Benachrichtigungen befindet. Centos 7, Android-Version 7.0 und 5.0. Auf Android 5.0, sagt es, dass Wipe ein Erfolg ist, aber das Telefon nicht neu starten und macht nicht wischen .. danke für Hilfe. Wenn Sie mehr Protokolle benötigen, können Sie mir sagen, wo ich sie finden kann? –

Antwort

0

Wir haben ein Problem mit der Wipe-Operation auf Android gefunden und dies mit der neuen Version unseres Android-Agenten behoben, die mit IoT Server 3.1.0 kompatibel ist.

Finden Sie die apk-Datei und den neuen Quellcode here.

Danke,

Verwandte Themen