Python script - issues connecting with ArcGIS on semi-regular basis

[Jon_Bryce]

Hi all.  I've been tasked with writing a Python script that runs every 5 mins, downloading Surveys from the website to the local server.   I have this working (took me a while...) but I continually get connection errors at certain times of day (2:40am), and they continue for several hours before righting themselves.

I've reproduced this on a separate server: both use Arcgis module (2.1.0.3).  

Relevant parts..

..

from arcgis.gis import GIS

..

# Connect to ArcGIS

#

logline("Opening GIS, username >" + <xxx> + "<")

#

try:

    gis_connection = GIS(username=<xxx>, password=<yyy>)

    logline ("Connected OK")

except Exception as e:

    #

    logline(

            "Error opening GIS connection - Error returned is : >"

            + str(e) + "<" )

My log shows ...

4/10/2023 08:00:43 : Error opening GIS connection - Error returned is : >A connection error has occurred: HTTPSConnectionPool(host='www.arcgis.com', port=443): Max retries exceeded with url: /sharing/rest/generateToken (Caused by ProtocolError('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)))<

Is this the memory leak problem from this post?

https://community.esri.com/t5/arcgis-enterprise-portal-questions/python-script-error-10054-connectio...

I've introduced a periodic garbage collect as per that post's suggestions, but that didn't seem to help. 

Any other suggestions?   (Do I need to explicitly close the connection to the website at the end of each iteration of the script, for example?)

Thanks for any suggestions...  

[David_McRitchie]

Hey Jon,

How are you scheduling your python script? I have seen this issue come up from a user case before.

The resolution to this was scheduling the script from within ArcGIS Pro rather than scheduling it directly with Windows Task Scheduler. 

Hopefully that fixes this for you as well,

David

[Jon_Bryce]

Thanks David - it was actually easier than that.  The times corresponded exactly with a Veeam backup of that server.   I suspect the issue has always been there and we're only just now detecting it (as this is a new script).    I've got my Systems Veeam people looking at what's happening there.  

I wasn't aware that there was a scheduler within ArcGIS Pro - I'll certainly take a look there too.  However I'm trying to get this place to move to a centralized scheduling location - right now things are scattered in all sorts of places, and introducing another place would be counter-productive to that proposal.  

Thanks again for the attention and suggestion though.