ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only starting on April 19, 8am Pacific as the migration begins.Read more for important details.

GMS 18.3: Log file shows error (104, 'ECONNRESET')

GMS 18.3 shows the error from the subject:

An Error occurred processing a ping for device: 30947a62e03f1931776ade089e888a23
Traceback (most recent call last):
File "./mobility/lib/device/", line 268, in run
File "./mobility/lib/device/", line 137, in sendPingResponse
File "/usr/lib/python2.7/site-packages/OpenSSL/", line 1538, in send
self._raise_ssl_error(self._ssl, result)
File "/usr/lib/python2.7/site-packages/OpenSSL/", line 1446, in _raise_ssl_error
raise SysCallError(errno, errorcode.get(errno))
SysCallError: (104, 'ECONNRESET')

in the mobility-agent.log. Is this a bug or a configuration error? If this is the result of en failed configuration how should I repair this?

3 Replies
Micro Focus Expert
Micro Focus Expert



Are you seeing these errors specifically for connections from Apple devices?

Is synchronization being delayed for these devices when this error is evident?

Was this GMS installation upgraded from earlier versions of GMS?





Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...


Have the same issue.

My server was new deployed with the actual build (no updated server).

Regards Martin

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Im not sure there is something "to fix" as this seems a communication error on the ping negotiation and/or open ping connection between a device and the GMS server.

The ECONNRESET (which means connection reset by peer) is almost always one of the following:

- TCP/IP encountered via keepalive or timeout that the remote is not responding

- The remote process has closed the socket

In case of GMS and as you see its related to processing a ping request/response for a device both can fit but is also pointing to the device not being available or it closed the open connection with the GMS server for some reason. The ping/heartbeat is a keepalive process so the GMS server is able to let the device know there is a change and the device needs to connect to retrieve new data.

I assume the ping/heartbeat is resumed after some time for the deviceID when it is available again (connected itself to GMS), this could be checked for deviceID 30947a62e03f1931776ade089e888a23 and if there are lines in the mobility-agent.log ( DEBUG loglevel only ) showing the "adding ping for device: heartbeat 30947a62e03f1931776ade089e888a23" behind this is a :xxx which is the number of seconds this delayed ping will stay open.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.