Mosh fails on downloading non existing Linux 64-bit static mosh-server binary #1963
Comments
mpepping
added
the
bug
|
I can confirm the same behavior trying to connect to an unraid instance using the |
mpepping
changed the title
|
Thanks for reaching out guys and apologies for the slow reply. I will review and do a quick fix for this. In the meantime, you can download it manually from Blink (using |
I was actually very interested on this use case as I even saw it on Reddit, but never got to try it on uRaid. Would you mind telling me if the binary works there? Thanks! |
✅ I can confirm the binary you posted above does work on ❌ The Using the below commands and eventually saving them as a user script (running at first start of the array) made mosh working like charm wget -O /usr/bin/mosh-server https://github.com/blinksh/mosh-static-multiarch/releases/latest/download/mosh-server-1.4.0-linux-amd64
chmod a+x /usr/bin/mosh-server |
Hi, |
We are working on a fix for this that should be out soon, but in the meantime you can install on your own in the server by just doing what @verypacific suggested: |
|
Fixed. Will be out on 17.2.2 |
|
Just updated to 17.2.2 but unfortunately the mosh static is not working. Running the Maybe the logging below helps. blink> mosh --install-static --verbose n1
socket_callback_connected: Socket connection callback: 1 (0)
ssh_known_hosts_read_entries: Failed to open the known_hosts file '/etc/ssh/ssh_known_hosts': No such file or directory
ssh_packet_userauth_failure: Access denied for 'none'. Authentication that can continue: publickey
ssh_agent_get_ident_count: Answer type: 12, expected answer: 12
bootstrapMoshServer: Trying bootstrap with sequence: [Blink.UseMoshOnPath, Blink.InstallStaticMosh], experimental: BKMoshExperimentalIP(rawValue: 0), family: nil, args: new -s -c 256 -l LANG=en_US.UTF-8 -p 60060
bootstrapMoshServer: Trying Blink.UseMoshOnPath
bootstrapMoshServer: Connecting to ~/.local/blink/mosh-server new -s -c 256 -l LANG=en_US.UTF-8 -p 60060
ssh_packet_global_request: Invalid SSH_MSG_GLOBAL_REQUEST packet
bootstrapMoshServer: Command output: bash: line 1: /root/.local/blink/mosh-server: No such file or directory
bootstrapMoshServer: Bootstrap failed with NoMoshServerArgs
bootstrapMoshServer: Trying Blink.InstallStaticMosh
platformAndArchitecture: uname output: ["Linux", "x86_64", ""]
getMoshServerBinary: linux amd64
installMoshServerBinary: on .local/blink/mosh-server
sftp_canonicalize_path: SFTP server: No such file
sftp_xstat: SFTP server: No such file
installMoshServerBinary: Path not found: .local/blink. Creating it...
sftp_xstat: SFTP server: No such file
installMoshServerBinary: File uploaded at .local/blink/mosh-server-1.4.0-linux-amd64. Moving to .local/blink/mosh-server
installMoshServerBinary: chmod +x /root/.local/blink/mosh-server
bootstrapMoshServer: Connecting to /root/.local/blink/mosh-server new -s -c 256 -l LANG=en_US.UTF-8 -p 60060
bootstrapMoshServer: Command output: /root/.local/blink/mosh-server: line 1: Not: command not found
bootstrapMoshServer: Bootstrap failed with NoMoshServerArgs
NoMoshServerArgs - Did not find mosh server startup message. (Have you installed mosh on your server?)
Use mosh1 for the deprecated (previous) mosh version. |
|
Just for reference below is what a successful attempt to use the The only difference I noticed is that there is an actual binary upload progress bar seen after I got asked to download the binary to the server. blink> mosh --install-static --verbose upi4
socket_callback_connected: Socket connection callback: 1 (0)
ssh_known_hosts_read_entries: Failed to open the known_hosts file '/etc/ssh/ssh_known_hosts': No such file or directory
ssh_packet_userauth_failure: Access denied for 'none'. Authentication that can continue: publickey,password
ssh_agent_get_ident_count: Answer type: 12, expected answer: 12
bootstrapMoshServer: Trying bootstrap with sequence: [Blink.UseMoshOnPath, Blink.InstallStaticMosh], experimental: BKMoshExperimentalIP(rawValue: 0), family: nil, args: new -s -c 256 -l LANG=en_US.UTF-8 -p 60040 -- byobu
bootstrapMoshServer: Trying Blink.UseMoshOnPath
bootstrapMoshServer: Connecting to ~/.local/blink/mosh-server new -s -c 256 -l LANG=en_US.UTF-8 -p 60040 -- byobu
ssh_packet_global_request: Invalid SSH_MSG_GLOBAL_REQUEST packet
bootstrapMoshServer: Command output: zsh:1: no such file or directory: /home/ubuntu/.local/blink/mosh-server
bootstrapMoshServer: Bootstrap failed with NoMoshServerArgs
bootstrapMoshServer: Trying Blink.InstallStaticMosh
platformAndArchitecture: uname output: ["Linux", "aarch64", ""]
getMoshServerBinary: linux arm64
installMoshServerBinary: on .local/blink/mosh-server
sftp_canonicalize_path: SFTP server: No such file
sftp_xstat: SFTP server: No such file
installMoshServerBinary: Path not found: .local/blink. Creating it...
sftp_xstat: SFTP server: No such file
installMoshServerBinary: File uploaded at .local/blink/mosh-server-1.4.0-linux-arm64. Moving to .local/blink/mosh-server
installMoshServerBinary: chmod +x /home/ubuntu/.local/blink/mosh-server
bootstrapMoshServer: Connecting to /home/ubuntu/.local/blink/mosh-server new -s -c 256 -l LANG=en_US.UTF-8 -p 60040 -- byobu
bootstrapMoshServer: Command output:
MOSH CONNECT 60040 REDACTED
mosh-server (mosh 1.4.0) [build mosh 1.4.0]
Copyright 2012 Keith Winstein <mosh-devel@mit.edu>
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
[mosh-server detached, pid = 527155]
startMoshServer: Remote Mosh server bootstrapped with params MoshServerParams(key: "REDACTED", udpPort: "60040", remoteIP: "REDACTED") |
|
@verypacific thanks for taking a look at this so quickly. I think I may have made a rookie mistake and forgot to delete the "invalid" binaries you may already have in .blink folder. Would you mind doing so? The flow is to download the binary if there is none (but in your case there is, although invalid) and do a checksum. Then we upload the binary to the server. But if you already have a file there, we skip the checksum and upload directly. I did it that way so people could also "automatically upload" binaries they may have from their side. |
|
Same here; after the "Mosh server not found" dialog and the download attempt, |
|
Hi @carloscabanero I was thinking the same too so I completely removed the The log I posted above for unraid already shows the process of a fresh download with no file present. The upload progress bar is practically not present as the small pop-up notification is only shown for a split of a second (whereas on Ubuntu an actual upload to the server is happening) Unfortunately it still results in the |
|
Apologies for the delay getting back on this @verypacific & @mpepping. We have 17.3.0 coming up and it is taking most of the time. I fixed the issue of an erroneous download being kept in the file system, but unfortunately, I haven't been able to reproduce your issue. I have tried many different distros (Ubuntu, Fedora, etc...), and they are all working fine. The flow is really easy, but the thing is that except for the original message that has already been fixed, I don't see now from the logs what is the new location Blink is trying to download from that is causing the "Not Found" error message. Can you send me the specific new line: Also, it cannot happen that on the same run Blink downloads a file with "Not Found" and uploads that trash to the server. We perform a checksum validation and that would have failed. On a subsequent run though it would be uploaded - and that's what your logs show -, and is what I realized we were not doing properly and should be fixed for 17.3.0. |
Hmm, the line is:
Blink v17.2.2.868 |
Checklist
Configuration
Describe the bug
The
mosh --install-static --verbose myhostcommand to a 64bit linux host tries to download themosh-server-1.4.0-linux-x86_64static binary. This throws a 404. The actual binary name on the Github release page ismosh-server-1.4.0-linux-amd64.The text was updated successfully, but these errors were encountered: