Error (timeout) on pulling site from DevKinsta

Q: Date/Time this occurred (Provide your time zone also)
A: 2023-06-22 12:17:48 MESZ

Q: DevKinsta Version
A: 2.11.0 (this has been happening since I am using DEV Kinsta in March 2023)

Q: OS Version
A: Microsoft Windows 11 Pro N Version 10.0.22621 Build 22621

Q: Docker Desktop Version
A: 4.18.0

Q: Were any error codes or messages observed? If so, what were they?
A:

[2023-06-22 12:17:46.617] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:46.698] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:46.905] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:47.139] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:47.368] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:47.574] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:47.798] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:48.025] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:48.044] [warn] [terminalExec] Error:
rsync: connection unexpectedly closed (5771280 bytes received so far) [receiver]

[2023-06-22 12:17:48.080] [warn] [terminalExec] Error: rsync error: error in rsync protocol data stream (code 12) at io.c(231) [receiver=3.2.7]

[2023-06-22 12:17:48.086] [warn] [terminalExec] Error: rsync: connection unexpectedly closed (465958 bytes received so far) [generator]
rsync error: timeout in data send/receive (code 30) at io.c(231) [generator=3.2.7]

[2023-06-22 12:17:48.231] [info] [ProgressIndicator] { isFailed: false, isOpen: true }
[2023-06-22 12:17:48.476] [info] [terminalExec] Child process exited with code 30
[2023-06-22 12:17:48.478] [error] [downloadSite] Error while downloading files Error: Encountered an error in child process 8716: 30. rsync: connection unexpectedly closed (465958 bytes received so far) [generator]
rsync error: timeout in data send/receive (code 30) at io.c(231) [generator=3.2.7] at handleChildProcessClosure (C:\Users\a\AppData\Local\Programs\DevKinsta\resources\app.asar\main.prod.js:2:733315)
at ChildProcess. (C:\Users\a\AppData\Local\Programs\DevKinsta\resources\app.asar\main.prod.js:2:732272)
at ChildProcess.emit (node:events:513:28)
at ChildProcess.emit (node:domain:489:12)
at maybeClose (node:internal/child_process:1091:16)
at Socket. (node:internal/child_process:449:11)
at Socket.emit (node:events:513:28)
at Socket.emit (node:domain:489:12)
at Pipe. (node:net:313:12)
[2023-06-22 12:17:48.548] [error] [ipcMainStep] Error in operation SITE_PULL, step rsync: Error: Encountered an error in child process 8716: 30. rsync: connection unexpectedly closed (465958 bytes received so far) [generator]
rsync error: timeout in data send/receive (code 30) at io.c(231) [generator=3.2.7]
at handleChildProcessClosure (C:\Users\a\AppData\Local\Programs\DevKinsta\resources\app.asar\main.prod.js:2:733315)
at ChildProcess. (C:\Users\a\AppData\Local\Programs\DevKinsta\resources\app.asar\main.prod.js:2:732272)
at ChildProcess.emit (node:events:513:28)
at ChildProcess.emit (node:domain:489:12)
at maybeClose (node:internal/child_process:1091:16)
at Socket. (node:internal/child_process:449:11)
at Socket.emit (node:events:513:28)
at Socket.emit (node:domain:489:12)
at Pipe. (node:net:313:12)
[2023-06-22 12:17:48.763] [info] [ProgressIndicator] { isFailed: true, isOpen: true }
[2023-06-22 12:18:49.581] [info] [useMailhog] Mail socket closed.

Q: Detailed Description of the Problem
A: While pulling the environment from the remote Server it fails after some time. It is possible to pull smaller portions (30 - 60 MB).

Hello @diantonie and welcome to DevKinsta Community!
Does the pull always fail at the very same percentage?

Regards,
Alessandro

Hello @Alessandro

Thanks for the reply. I believe the error has smth to do with Hyper-V and the files beeing on the windows filesystem.

I saw that DevKinsta now uses a //wsl directory to store the files (it was not set for me two months ago when I installed it and I switched to Hyper-V because it was too slow) so I switched back to wsl2 and here the issue does not occur anymore.

Thanks!

That’s great news @diantonie! Thanks for sharing your solution :+1:

All the best!
Alessandro