"Error connecting to remote" only for centOS ssh server

[Gray-Ice]

Something went wrong when I'm trying to connect my three difference version CentOS servers, all of them are using the bash shell. I got these errors.

---

Server 1

error

error connecting to remote: invalid packet received from mshell client: raw[which: no mshell-v0.3 in (/usr/lib64/qt-3.3/bin:/home/rexdu/perl5/bin:/usr/local/bin:/usr/bin:/home/rexdu/.mshell)]

---

Server 2 error:

error connecting to remote: invalid packet received from mshell client: raw[/usr/bin/python: Error while finding module specification for 'virtualenvwrapper.hook_loader' (ModuleNotFoundError: No module named 'virtualenvwrapper')]

---

Server3 error

 Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
prompt> error connecting to remote: no init packet received from mshell client

For server1, I want to know:

• Can I install mshell for this server to help wave terminal solve this problem?
• If there is a binary file for me to easier install?Case you know, it's really hard to compile the file, especially on the server.

For server2, I wan to know:

• Can I solve this problem by install virtualenvwrapper? If it will work, which kind of pip should I use, pip or pip3?

I didn't get any problem on Ubuntu. Please help me to solve these problems.

[sawka]

Sorry about not responding to this sooner. I think for the most part I'm super confused as to why you seem to be the only person getting these specific issues. Trying to figure out what could be the issue.

So for server1, when you create the connection, mshell/waveshell is supposed to be installed into ~/.mshell . But yes, in theory you can manually copy it there yourself. There are 4 mshell binaries shipped with Wave. If you look in the Wave.app directory, then go to Contents/Resources/app/bin/mshell you'll see the 4 version -- you probably want mshell-v0.3-linux.amd64. Copy that file into ~/.mshell and rename it to just mshell-v0.3.

For server2, I really don't know why that's happening. Maybe something in your .bashrc or .bash_profile is calling virtualenv? Wave shouldn't be calling any python commands itself.

I'll flag this as a bug for now and noodle on it a bit more. There is a bug for server1 where the "which" command was not supposed to generate an error like that, it should have been handled more gracefully and reported back in a more structured way.

[kukkuk]

Getting similar error connecting to a remote Debian server:

prompt> error connecting to remote: invalid packet received from mshell client: raw[WARNING: Unauthorized access to this system is forbidden and will be prosecuted by law. By accessing this system, you agree that your actions may be monitored if unauthorized usage is suspected.]
prompt> error reading from controlling-pty: read /dev/ptmx: input/output error

[oneirocosm]

@kukkuk I believe your issue comes from a banner which should be solved in v0.7.0. Let me know if this is still a problem though.