Open donrestarone opened 2 years ago
digging deeper into the error it looks like its a simple connection timeout. We should lengthen the wait time to the maximum (maybe 30 seconds?)
Tasks: TOP => deploy:assets:rsync
(See full trace by running task with --trace)
The deploy has failed with an error: Exception while executing as ubuntu@***: rsync -av --delete ./public/assets/ ubuntu@***:/var/www/violet/releases/20220413222925/public/assets/ exit status: 65280
rsync -av --delete ./public/assets/ ubuntu@***:/var/www/violet/releases/20220413222925/public/assets/ stdout: Nothing written
rsync -av --delete ./public/assets/ ubuntu@***:/var/www/violet/releases/20220413222925/public/assets/ stderr: ssh: connect to host *** port 22: Connection timed out
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.2]
end
possible solutions:
new problem since 'fixing' (not yet confirmed) the rsync issue: looks like we need to set an SSH timeout on the target servers (client connection keep alive or something similar)
still an issue (rsync isn't passing the additional parameter see deploy.rb
):
when set in deploy/environment.rb
it worked!
2022-06-29T23:11:57.8727935Z ✔ 02 runner@localhost 163.395s
2022-06-29T23:11:57.8728960Z 02:59 deploy:assets:rsync
2022-06-29T23:11:57.8730519Z 01 rsync -av --delete --timeout 300 ./public/assets/ ubuntu@***:/var/www/violet/releases/20220629230859/public/assets/
2022-06-29T23:11:59.4574684Z 01 sending incremental file list
2022-06-29T23:11:59.4745014Z 01 ./
its getting set to 300 didnt make the deployments more consistent -- reopening