deployer: Deploy fails with multiplexing enabled
- Deployer version: 6.8.0
- Deployment OS: Debian 9.13
export APP_ENV='stage' APP_DEBUG='0'; if [ -f /var/www/*************/.dep/deploy.lock ]; then echo 'true'; fi
< ssh multiplexing initialization
< Warning: Permanently added '**************,***.***.***.**' (ECDSA) to the list of known hosts.
< unix_listener: cannot bind to path /root/.ssh/deployer_deployer@**************.LiZt386qtCUqfmHr: No such file or directory
deploy example:
host('**************')
->stage('stage')
->set('deploy_path', '/var/www/stage-{{application}}')
->multiplexing(true)
->addSshOption('UserKnownHostsFile', '/dev/null')
->addSshOption('StrictHostKeyChecking', 'no')
->user('deployer');
when i disable multiplexing it works again
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 26 (22 by maintainers)
Actually trying different paths before initializing multiplexing is a good idea. We can try this. I can write a PR for it.
Yes, we can try to fix the issue. As this issue not wide spread it’s difficult propose a fix.
Let’s create a pr with a fix?
Hi @antonmedv any news on this topic, maybe we should use deployer user’s home dir for socket? or try a bunch of different paths until one succeeds? i would happy to send a PR, but not sure which dir would be suitable