ODK Central Backup Fails (ECONNRESET)

Support
1

For the past 4 days, the automatic backups have failed to complete successfully on my instance of Central. Yesterday, I reset the connection to GDrive thinking that could solve the issue but I had the same error message today.

	
{"stack":"FetchError: request to https://www.googleapis.com/upload/drive/v3/files?fields=id&uploadType=multipart failed, reason: read ECONNRESET\n at ClientRequest.<anonymous> (/usr/odk/node_modules/node-fetch/lib/index.js:1461:11)\n at ClientRequest.emit (events.js:412:35)\n at ClientRequest.emit (domain.js:470:12)\n at TLSSocket.socketErrorListener (_http_client.js:475:9)\n at TLSSocket.emit (events.js:400:28)\n at TLSSocket.emit (domain.js:470:12)\n at emitErrorNT (internal/streams/destroy.js:106:8)\n at emitErrorCloseNT (internal/streams/destroy.js:74:3)\n at processTicksAndRejections (internal/process/task_queues.js:82:21)","message":"request to https://www.googleapis.com/upload/drive/v3/files?fields=id&uploadType=multipart failed, reason: read ECONNRESET","success":false}

I'm currently rocking

versions:
24ee74e5f974a518aa1cc8b06e7addb3be6b4690 (v1.3.3-2-g24ee74e)
 5cc6fd79d112ce36d6298c61bb8817689c4c323b client (v1.3.2)
 1d1a3a59969e61383da74119e405e67778b7a170 server (v1.3.3)

Any pointers will be greatly appreciated.

2

Hi @aankrah! This isn't an error that I think we've seen before. Have you made any changes to your Central server or to your network setup recently? Also, how large is your latest backup on Google Drive?

I reset the connection to GDrive

Just to check, does that mean that you terminated backups, then set them up again?

One thing to try would be to upgrade to Central v1.4, because we did update how we connect to Google's APIs. However, it's good practice to have a backup before upgrading. Are you able to download an immediate backup from the backups page?

4

Hello @Matthew_White! Thanks for responding. To answer your questions, I am not sure of any changes to the server or network.

[Realizing I hadn't sent that 2+ months later :man_facepalming:t4:]
Still don't know what the issue was, but it seemed to have fixed itself 2 days after the initial post.

1 Like