Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SSH connection established before remote machine available #364

Closed
flixman opened this issue Jun 21, 2018 · 1 comment
Closed

SSH connection established before remote machine available #364

flixman opened this issue Jun 21, 2018 · 1 comment
Labels

Comments

@flixman
Copy link
Contributor

flixman commented Jun 21, 2018

I have a remote VM that I am using to keep my encrypted ZFS backups. Also, in my current set-up I have some databases that I need to lock/flush before snapshoting them, and also unlock them when done. Then I have writen a script to lock/unlock the DBs, and another to start/stop the VM, so that my znapzendzetup create looks like (ZFSfiler is the SSH host configuration name in .ssh/config):

znapzendzetup create --recursive \
--pre-snap-command="/bin/bash /home/testuser/lock_DBs_for_snapshot.sh start" \
--post-snap-command="/bin/bash /home/testuser/lock_DBs_for_snapshot.sh stop" \
SRC '1d=>1h,7d=>1d,1m=>1w' zfsdata/tothrow \
DST '1d=>1h,7d=>1d,1m=>1w' ZFSfiler:zfsbackup/tothrow \
"/usr/bin/python3 /home/testuser/manageVM.py start" \
"/usr/bin/python3 /home/testuser/manageVM.py stop"

When running the previous command, I get:

Do you want to save this backup set [y/N]? y
ssh: connect to host zfsfiler.westeurope.cloudapp.azure.com port 22: Network is unreachable
NOTE: if you have modified your configuration, send a HUP signal
(pkill -HUP znapzend) to your znapzend daemon for it to notice the change.

So, the machine is obviously not up as (I think) the manageVM.py script has not been run. Have I hit a bug, or am I doing something wrong (and I do not see what)?

@stale
Copy link

stale bot commented Jun 28, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jun 28, 2021
@stale stale bot closed this as completed Jul 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant