Deployment over 12 hours fails due to expired IdentityFile "no such identity" about deployer HOT 3 CLOSED

wow, I never thought it would be possible for a deploy to take this long.

The reason is that SSH keys are normally cleaned up when deploy is finished, but if something happens (say the worker crashes) it gets left on the server which isn't great so there is a cronjob to clean up keys older than 12 hours.

For now the simplest fix is to change app/Console/Commands/ClearOldkeys.php and increase the KEEP_FILES_FOR_HOURS constant. Maybe I should make it a config option?

Trying to figure out if the deploy which uses the key is still actually running because much more complicated, although it may be doable.

from deployer.

Thanks for your response, Stephen.
I'll try to update the constant and see if it helps. Maybe a configurable option is a good idea even if it's rarely going to be changed.
The command used to take just a couple of hours until we moved our servers to AWS and they reduce RDS instance Write IOPS and CPU when it's heavily used unless you pay a lot. But we need to run it maybe once a month so it's not worth it.

from deployer.

Hi Stephen, I can confirm that changing KEEP_FILES_FOR_HOURS constant in app/Console/Commands/ClearOldKeys.php to a longer period works and we were able successfully complete the deployment.
Thank you!

from deployer.