On two machines, one at home and the other an AWS instance I can no longer install the client
When I run curl -so- https://raw.githubusercontent.com/maidsafe/safe_network/master/resources/scripts/install.sh | bash
either from the command line or in a script I receive the same error on both machines - both Ubuntu 20.04.3
ubuntu@ip-172-31-7-155:~/comnet-install$ curl -so- https://raw.githubusercontent.com/maidsafe/safe_network/master/resources/scripts/install.sh | bash
=> Downloading Safe CLI package from 'https://github.com/maidsafe/safe_network/releases/download/0.55.0-0.53.0-0.46.0/sn_cli-0.46.0-x86_64-unknown-linux-musl.tar.gz'...
=> Saving to '/tmp/tmp.Hqa4yP4e6Q/sn_cli-0.46.0-x86_64-unknown-linux-musl.tar.gz'...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 685 100 685 0 0 6820 0 --:--:-- --:--:-- --:--:-- 6782
Warning: Failed to create the file
Warning: /tmp/tmp.Hqa4yP4e6Q/sn_cli-0.46.0-x86_64-unknown-linux-musl.tar.gz:
Warning: No such file or directory
0 10.2M 0 852 0 0 1316 0 2:16:01 --:--:-- 2:16:01 1316
curl: (23) Failure writing output to destination
=> Unpacking Safe CLI to '/home/ubuntu/.safe/cli'...
tar (child): /tmp/tmp.Hqa4yP4e6Q/sn_cli-0.46.0-x86_64-unknown-linux-musl.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
Works fine on my Kali laptop and on another fresh AWS 20.04 instance.
All the permissions look fine and have not been touched from default - certainly on the AWS instance. I first noticed this yesterday on my home box and now see the same on one of the AWS instances.
Anybody seen anything similar or got hints on exactly what permissions to check?
On AWS ls -al /tmp shows drwxrwxrwt 14 root root 4096 Jan 31 18:10 .
On my home box drwxrwxrwt 27 root root 20480 Jan 31 18:12 .
Most frustrating as my script is now ready to run on a fresh AWS instance or other machine and will download client and node, connect to a (hardwired as yet) comnet and then install rust, vdash and monitor the node.
I vaguely recollect seeing something similar before, but I was busy messing with my router at the time, so I thought I’d done something wrong myself.
I seem to vaguely remember seeing this before once. IIRC I put it down to a corrupted download, tried again and it was fine. However this problem is consistent on both machines now.
Still getting this error when I run curl -so- https://raw.githubusercontent.com/maidsafe/safe_network/master/resources/scripts/install.sh | bash
ubuntu@ip-172-31-7-155:~$ curl -so- https://raw.githubusercontent.com/maidsafe/safe_network/master/resources/scripts/install.sh | bash
=> Downloading Safe CLI package from 'https://github.com/maidsafe/safe_network/releases/download/0.55.2-0.54.0-0.47.0/sn_cli-0.47.0-x86_64-unknown-linux-musl.tar.gz'...
=> Saving to '/tmp/tmp.gwipbUXMO0/sn_cli-0.47.0-x86_64-unknown-linux-musl.tar.gz'...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 685 100 685 0 0 7074 0 --:--:-- --:--:-- --:--:-- 7135
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Warning: Failed to create the file
Warning: /tmp/tmp.gwipbUXMO0/sn_cli-0.47.0-x86_64-unknown-linux-musl.tar.gz:
Warning: No such file or directory
0 10.2M 0 1369 0 0 3618 0 0:49:38 --:--:-- 0:49:38 5326
curl: (23) Failure writing output to destination
=> Unpacking Safe CLI to '/home/ubuntu/.safe/cli'...
tar (child): /tmp/tmp.gwipbUXMO0/sn_cli-0.47.0-x86_64-unknown-linux-musl.tar.gz: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
chmod: cannot access '/home/ubuntu/.safe/cli/safe': No such file or directory
=> Adding statement to '/home/ubuntu/.bashrc' profile to have Safe CLI binary path in the $PATH
=> Profile '/home/ubuntu/.bashrc' already contains a statement to set Safe CLI in the $PATH
then it installs OK. $HOME/tmp has to exist first. I tried mkdir$HOME/tmp && tmp_dir=$HOME/tmp and it failed but its late…
Some weirdness around mktemp I am not understanding…
willie@gagarin:~$ curl -so- https://raw.githubusercontent.com/maidsafe/safe_network/master/resources/scripts/install.sh | bash
=> Downloading Safe CLI package from 'https://github.com/maidsafe/safe_network/releases/download/0.10.2-0.9.0-0.71.1-0.66.2-0.69.0-0.62.1/sn_cli-0.62.1-x86_64-unknown-linux-musl.tar.gz'...
=> Saving to '/tmp/tmp.R1ERHgBkV2/sn_cli-0.62.1-x86_64-unknown-linux-musl.tar.gz'...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 9.9M 100 9.9M 0 0 3413k 0 0:00:02 0:00:02 --:--:-- 4434k
=> Unpacking Safe CLI to '/home/willie/.safe/cli'...
=> Adding statement to '/home/willie/.bashrc' profile to have Safe CLI binary path in the $PATH
=> Profile '/home/willie/.bashrc' already contains a statement to set Safe CLI in the $PATH
willie@gagarin:~$ which curl
/usr/bin/curl
but I installed curl with apt, many many moons ago and its just been kept up to date
works like a charm now! thanks Southside! so we finally got an answer, snapd curl is the issue, maybe if we put in sudoers path the snpad curl it would work but I dont want to complicate it!
TBH, I try to avoid snap.
Seems like there is just too much that could go wrong… like helicopters
I totally see the motivation behind it and am sympathetic to it but for me its like an automatic and a manual gearbox “Im a big boy now and I will decide what gear to use!”
Which is easy for me to say after many many years of getting used to the CLI and apt etc - a tool to help those less experienced is in general A Good Thing - in general…
