search

evsar3 / sshfs-win-manager

A GUI for SSHFS-Win (https://github.com/billziss-gh/sshfs-win)
MIT License
1.14k stars 85 forks source link

No error message #18

Closed chopin57otu closed 4 years ago

chopin57otu commented 4 years ago

Hello,

my connection is not working for some reason. When I click the plug button the button shows some progress and then turn back to disconnected icon. The issue is I don't receive any error message, so I don't know what's wrong.

I'm using private key. I can initiate SSH connection with the same configuration.

evsar3 commented 4 years ago

Hello,

Is your private key protected by password?

chopin57otu commented 4 years ago

Hello,

Is your private key protected by password?

No.

BTW error message from SiriKali (might be caused by the same issue): image

evsar3 commented 4 years ago

Never seen anything like this... for now I hope someone that experienced such scenario give us some feedback on a possible workarround.

mhogomchungu commented 4 years ago

When SiriKali main window has focus, press "CTRL+D" to get debug window and try to connect again to see what command SiriKali is invoking and use it on the terminal to see what error is reported when its failing.

In SiriKali, you are getting that because one part of SiriKali keeps reading sshfs-win output(std error and stdout) waiting to see something in it to recognize as error or success but sshfs-win exits without producing the data SiriKali is expecting.

Another part of SiriKali notices the backend is gone and reported what you are seeing.

The problem from SiriKali perspective are either:

  1. sshfs-win exists normally without producing expected error messages.
  2. sshfs-win is crashing and exists without producing anything.
chopin57otu commented 4 years ago

Hello and thank you for your response

SiriKali debug output:

...
Backend took 4 seconds to unlock a volume
***************************
Exit Code: 1
Exit Status: 0
-------
StdOut: 
-------
StdError: 
-------------

SiriKali::Error Backend Disappeared For Some Reason (It Probably Crashed).
-------
Command: "C:\Program Files\SSHFS-Win\\bin\sshfs.exe" -f "ubuntu@****" "U:"  -o rw,fsname=sshfs@"ubuntu@****",subtype=sshfs,idmap=user,StrictHostKeyChecking=no,IdentityFile=C:/Users/****/.ssh/****.ppk,volname="ubuntu@****"
-------

command line:

C:\Program Files\SSHFS-Win\bin>sshfs -f "ubuntu@****" "U:"  -o rw,fsname=sshfs@"ubuntu@****",subtype=sshfs,idmap=user,StrictHostKeyChecking=no,IdentityFile=C:/Users/****/.ssh/****.ppk,volname="ubuntu@****"

C:\Program Files\SSHFS-Win\bin>

Shall I move this issue to sshfs-win ?

mhogomchungu commented 4 years ago

Yes, I think you should. On error, sshfs should print the occured error before exiting.

mhogomchungu commented 4 years ago

This option may be the source of the problem IdentityFile=C:/Users/****/.ssh/****.ppk.

Is there a space character hidden in those stars?

chopin57otu commented 4 years ago

No, my username is in format C:\Users\john.doe\.ssh.

mhogomchungu commented 4 years ago

The problem is caused by a bug in winfsp[1] and a temporary fix is for this line[2] to be changed to make sure volname does not exceed 32 characters.

Released version of SiriKali[3] solved the issue by making sure volname variable does not exceed 32 characters.

[1] https://github.com/billziss-gh/winfsp/issues/311 [2] https://github.com/evsar3/sshfs-win-manager/blob/154016e8d456bf5d54d6a45fff86562c4235319b/src/renderer/ProcessHandlerWin.js#L20 [3] https://github.com/mhogomchungu/sirikali/releases/tag/1.4.4

evsar3 commented 4 years ago

Hello @mhogomchungu

Great work on throbleshooting this!

Thank you.