HCL Notes and Domino 9.0 Social Edition Forum - Traveler Contacts not syncing

Jun 19, 2013, 9:21 AM

4 Posts

Check the logs

There is a usage log that has a lot of information:

Usage logging

The usage log shows every sync and device command that the system performs on behalf of mobile users.

The log is a text file located in <Domino data root>\IBM_TECHNICAL_SUPPORT\traveler\logs\NTSUsage_YYMMDD_HHMMSS.log. The timestamp corresponds to the date and time that the log file was created. It will wrap when it reaches the maximum defined usage log size, but the logging system can be configured to store older versions of the files. Usage logger limits are defined in the file <Domino data root>\traveler\cfg\NTSLogging.properties.

Each line in the file represents a single transaction and the transactions are logged once they complete (not when they begin). This allows you to easily see who is syncing, how often, and whether or not there were any errors. All usage log entries are included in the Activity logs as well, but since the activity logs contain much more information, they will wrap more frequently.

The below example details a sample transaction log:

"07/12 14:58:37.817" 9.27.157.16 9.37.16.125 "CN=John Doe/O=ACME" http://acme.ibm.com/mail%2Ftest13.nsf sp 200 2390 "Lotus Traveler Android 8.5.3" Android_26608076e563affa 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 "S2D Mail 2A"

At the beginning of the usage log, columns identify the data. The column names are as follows:

Timestamp: Time stamp of the request.
Device Address: IP address of the device.
Note: If there is a front-end proxy, then this address will be the proxy address instead of the actual device.
Server Address: IP address of the server.
User ID: User Identification (what the HTTP server normalized the user name to - not necessarily what the user entered on the device).
Database URL: URL of the database (mail file) to be synced.
Sync Origin: Identifies who requested the sync (ps = prime sync, dm = device manual, dp = device push, sp = server push).
Status Code: Code indicating the status of the ended sync For example, 200 = success, 408 = timed out, 409 = sync was cancelled because a new sync came in while the old one was running, 500 = server error, 503 = server too busy.
Duration: Number of milli-seconds that the action took to complete.
User Agent: HTTP User Agent header reported by the device (for a prime sync, there is no real device, so it is logged as "primesync" for the User Agent).
Device ID: Device Identification.
D->S Mail Adds: Number of mails created on the Device and sent to the Server.
D->S Mail Modifies: Number of mails created on the Device and sent to the Server.
D->S Mail Deletes: Number of mails created on the Device and sent to the Server.
D->S Contacts Adds: Number of address book entries created on the Device and sent to the Server.
D->S Contacts Modifies: Number of address book entries created on the Device and sent to the Server.
D->S Contacts Deletes: Number of address book entries created on the Device and sent to the Server.
D->S Calendar Adds: Number of events created on the Device and sent to the Server.
D->S Calendar Modifies: Number of events created on the Device and sent to the Server.
D->S Calendar Deletes: Number of events created on the Device and sent to the Server.
D->S Todo Adds: Number of todos created on the Device and sent to the Server.
D->S Todo Modifies: Number of todos created on the Device and sent to the Server.
D->S Todo Deletes: Number of todos created on the Device and sent to the Server.
D->S Journal Adds: Number of journal entries created on the Device and sent to the Server.
D->S Journal Modifies: Number of journal entries created on the Device and sent to the Server.
D->S Journal Deletes: Number of journal entries created on the Device and sent to the Server.
D->S Folder-Add: Number of mail folders created on the Devicer and sent to the Server
D->S Folder-Update: Number of mail folders modified on the Device and sent to the Server
D->S Folder-Delete: Number of mail folders deleted on the Device and sent to the Server
D<-S Mail Adds: Number of mails created on the Server and sent to the Device.
D<-S Mail Modifies: Number of mails created on the Server and sent to the Device.
D<-S Mail Deletes: Number of mails created on the Server and sent to the Device.
D<-S Contacts Adds: Number of address book entries created on the Server and sent to the Device.
D<-S Contacts Modifies: Number of address book entries created on the Server and sent to the Device.
D<-S Contacts Deletes: Number of address book entries created on the Server and sent to the Device.
D<-S Calendar Adds: Number of events created on the Server and sent to the Device.
D<-S Calendar Modifies: Number of events created on the Server and sent to the Device.
D<-S Calendar Deletes: Number of events created on the Server and sent to the Device.
D<-S Todo Adds: Number of todos created on the Server and sent to the Device.
D<-S Todo Modifies: Number of todos created on the Server and sent to the Device.
D<-S Todo Deletes: Number of todos created on the Server and sent to the Device.
D<-S Journal Adds: Number of journal entries created on the Server and sent to the Device.
D<-S Journal Modifies: Number of journal entries created on the Server and sent to the Device.
D<-S Journal Deletes: Number of journal entries created on the Server and sent to the Device.
D<-S Folder-Add: Number of mail folders created on the server and sent to the Device
D<-S Folder-Update: Number of mail folders modified on the server and sent to the Device
D<-S Folder-Delete: Number of mail folders deleted on the server and sent to the Device
Summary: A brief summary showing non-zero counts for device or server updates. For example, "S2D Mail 2A" means two mail documents were synced from the server to the device as adds.

If there is nothing in the log, you could increase the information:

tell traveler Log Level level

Sets the logging capture level to FINEST, FINER, FINE, INFO, WARNING, or SEVERE.

But depending on the size of your organization, I would limit it to a specific user:

Log collection for user-based problems

Perform the following procedure to generate a good set of logs for troubleshooting a user-based problem.

Increase the log level for a specific user that is exhibiting the problem by running the following command:
```
tell traveler log adduser finest <username>
```
Include the field data in your log report by running the following command:
```
tell traveler log fields *
```
Ask the user to reproduce the problem and submit a Traveler Problem Report (TPR). For more information, see Device logs.
After the user submits the TPR, run the following command:
```
tell traveler dump <username>
```