Score:3

Ubuntu

curl: (23) Failure writing output to destination

Sanyifejű

5/14/23, 5:29 PM

I want to run the following on ubunt 20.04:

sh <(curl -L https://nixos.org/nix/install) --daemon

what I got is this:

sh <(curl -L https://nixos.org/nix/install) --daemon
  % 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  4046  100  4046    0     0  16782      0 --:--:-- --:--:-- --:--:--   98k
downloading Nix 2.5.1 binary tarball for x86_64-linux from 'https://releases.nixos.org/nix/nix-2.5.1/nix-2.5.1-x86_64-linux.tar.xz' to '/tmp/nix-binary-tarball-unpack.KPhkYw21Nn'...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0Warning: Failed to create the file 
Warning: /tmp/nix-binary-tarball-unpack.KPhkYw21Nn/nix-2.5.1-x86_64-linux.tar.x
Warning: z: No such file or directory
  0 27.1M    0  1103    0     0  10753      0  0:44:05 --:--:--  0:44:05 10813
curl: (23) Failure writing output to destination
/dev/fd/63: failed to download 'https://releases.nixos.org/nix/nix-2.5.1/nix-2.5.1-x86_64-linux.tar.xz'

When I have a look at /dev/fd/ I see a bunch of files marked inaccessible:

I guess this has something to do with the failure to download. Am I right? What can I do against it? I am just a 'normal' ubuntu user, this kind of stuff exceeds my ubuntu-knowledge.

UPDATE: Even if I run the whole thing as root the result remains the same:

1598

0 + 0

curl

software-installation

20.04

N0rbert

5/14/23, 5:40 PM

Probably you have to download inside your home folder, where you have enough permissions. Also note that /dev/fb/ and /dev/fd/ are different objects. Which guide do you follow? Do you have sudo permissions on this computer?

Luuk

5/14/23, 6:31 PM

Try adding the option `-s` to curl. Maybe then you will notice this: "Warning: Failed to create the file" and "Failure writing output to destination" .

Sanyifejű

5/14/23, 6:57 PM

@N0rbert, yes, I do have sudo permission, but id does not seem to help. I am trying to follow this : https://nixos.org/download.html. Forgive me for my stupid question, but I am now in pr@server (probably due to a earlier installation which no longer matters).From here how to get to get to pr@home, or home?

Sanyifejű

5/14/23, 7:00 PM

@Luuk sh <(curl -s -L https://nixos.org/nix/install) --daemon Unfortunately makes no difference

N0rbert

5/14/23, 7:08 PM

You can enter `exit` to exit from SSH session. Or simply open new local terminal instance with Ctrl+Alt+T.

Sanyifejű

5/15/23, 8:11 AM

@N0rbert Unfortunately it's permanent. A new terminal also takes me to pr@server. Even after reboot.

Luuk

5/15/23, 11:21 AM

You can try the "Installing from a binary tarball" which is mentioned in this document: [Installing a Binary Distribution](https://nixos.org/manual/nix/stable/installation/installing-binary.html).

Score:2

Ubuntu

Sanyifejű

5/15/23, 4:40 PM

After a very long research I found a useful hint.

Can't write to a hidden path using Curl

Basically snap curl is useless. Uninstall it properly. Get the proper apt curl, and everything works like a charm.

$ sudo snap remove curl
$ sudo apt install curl

0 + 0

Fanta

10/10/22, 2:59 PM

Same here when running `pyenv install` under Ubutnu 22.04.1. Resolved following your advice.

sam

11/28/22, 9:37 AM

this problem still exist in ubuntu 22.04

CrazyPyro

7/10/23, 8:31 PM

Snaps strike again! What a POS...

Score:1

Ubuntu

Tech

4/5/24, 8:17 AM

In my case

$ sudo snap remove curl

didn't worked. So I had to remove it via apt-get like these:

$ sudo apt-get remove curl

Than installed it again.

$ sudo apt install curl

My problems solved.

+ 1

David

4/5/24, 9:12 AM

If snap remove did not work it was not a snap that was installed.

Score:0

Ubuntu

Dev Hassam

2/23/24, 8:28 PM

I faced the same error and below I shared how to fix.

First notice either you're logged-in as root@your-server-ip user or some other user@ip like debian@your-server-ip account.

In my case, I was logged-in as debian@vps-1a7c9 and try to run command using sudo and without sudo but got error curl: (23) Failure writing output to destination

How to Fix: run command sudo su to login as root this will change the current user to root user and terminals will look like root@your-server-ip.

Even this user debian@your-server-ip is an administrator account, but terminal return curl error, and after changing it to root@ all errors gone and commands worked. Means you're required to login as root.

+ 1

karel

2/25/24, 5:15 PM

The question says: `UPDATE: Even if I run the whole thing as root the result remains the same` It seems like you haven't read it.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: curl: (23) Failure writing output to destination

TH: curl: (23) ล้มเหลวในการเขียนเอาต์พุตไปยังปลายทาง

RO: curl: (23) Eșec la scrierea ieșirii la destinație

RU: curl: (23) Ошибка записи вывода в место назначения

VI: curl: (23) Lỗi ghi đầu ra tới đích

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.