Support Home Portal Log in
Open navigation

View Server Logs

  • Viewing Server Logs shows the last interaction with the server. This can be a useful debugging tool.
  • This shows all of the logs for the day of the last connection.
  • Logs are highly summarized.
  • If no logs are shown, the device may not have connected, or connected a long time ago.

3rd Party Direct Users

Please note that Server Logs can not be viewed on OEM server if the devices are using the third party direct/option 4 integration method.

To view server logs:

Click on details (1) for the device in question:

__0s5SJTFKPu-cSdIs9DLQWErN0xB4ZRdw.png


Go to the Logs tab. Click on View Server Logs (Last Connected Date) (1)

H1f5IE8dU28C50GKwftg3cjFn-BmuWbG_Q.png


As an example, the following may be displayed:
  • Date and Time of each record
  • The action that the server took
  • Commits show
    • the connector used in [square brackets], 
    • the Result: true if connected server accepted the records. False if the connected server rejected the records
    • the Duration of the operation
    • and how many records were sent in how many uploads. eg: 1r in 1u = 1 record in 1 upload.

 c2f7bdee-aedc-45de-8a98-96938bbb4b0d.png


Interpreting Logs

Successful Commit

"Commit" in OEM is when the device gets an ok response back from the end server, confirming that it has received all records. The server log image shown above is an example of a successful commit. It has the device serial number, the date and time of the record, connector used (marked in square brackets), the number of records uploaded and the result.

Socket Disposed

When an asset in on the move, it may come to areas with poor or marginal cellular coverage. The device might still be able to connect to the network and OEM and will try to upload. Since its in marginal coverage, the connection may drop before the full upload completes. We may then see a difference in the "Since Connected" and "Since Committed", and the server logs will mark this as "Socket Disposed".

Shutdown while Busy With Commit

This log is generally generated by OEM Server when the connection between the end server and the device is terminated while the device tries to commit and waiting for a commit response. Some factors causing this will be

  • End server rejecting the data
  • An unresponsive server leading to timeout on the device
  • Device signal issue - causing the connection to drop. 

Other issues e.g. HTTP 401, HTTP 500

We may see 401 (Unauthorized) - or 500 (Server Not Found) indicating an issue on the server side.

Note

For our 'Edge' range of devices - the equivalent to server logs are the Forwarder logs - Please see this article to find out how to check forwarder logs for debugging.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.