search

ratt-ru / radiopadre-client

Minimal client-side scripts to run radiopadre notebooks
MIT License
5 stars 0 forks source link

Auto-init build fail with non-zero exit status 127 #50

Open o-smirnov opened 2 years ago

o-smirnov commented 2 years ago

Discussed in https://github.com/ratt-ru/radiopadre-client/discussions/49

Originally posted by **rstofi** November 18, 2022 I've tried to `--auto-init` from local to a remote machine, but I got the following error message: ```shell radiopadre.client: ssh virtualenv -p python3 /home/krozgonyi/.radiopadre/venv failed with exit code 127 Traceback (most recent call last): ... subprocess.CalledProcessError: Command '['ssh', '-t', '-t', '-o', 'ControlPath=/tmp/ssh_mux_radiopadre_%C', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=1h', 'glowhpc', 'virtualenv -p python3 /home/krozgonyi/.radiopadre/venv']' returned non-zero exit status 127. ``` A working solution is simply to create the virtualenv on the remote via ```shell virtualenv -p python3 /path_to_home/.radiopadre/venv ``` after this `--auto-init` works as expected.
o-smirnov commented 2 years ago

I suspect the --remote-login-shell option needs to be applied to all commands (at the moment it's only applied to the final run-radiopadre command, but not to the "maintenance" commands before that). It may be the case that virtualenv on the remote end is only available to a login shell. I'll modify stuff accordingly.

o-smirnov commented 2 years ago

@rstofi could please test with this new version? It should invoke the login shell (assuming remote_login_shell is set in the config) when creating the virtualenv, hopefully it's a little more seamless now.