MuxError: Connect failed: error 3

[GoogleCodeExporter]

What steps will reproduce the problem?
1. load the custom ramdisk to ipad 1
2. attempt to connect ssh
3.

What is the expected output? What do you see instead?
ssh connection

What version of the product are you using? On what operating system?
OS X version : 10.8.2
XCode version : 6.0
Tools revision : run the "hg id" command in the iphone-dataprotection
folder
7ae0e9ebbb57+ tip
Please provide any additional information below.
once i try to connect the ssh i get authentification: Connection closed by 
remote host

and in the terminal with the relay i get 
 File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/SocketServer.py", line 582, in process_request_thread
    self.finish_request(request, client_address)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/SocketServer.py", line 323, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/SocketServer.py", line 639, in __init__
    self.handle()
  File "usbmuxd-python-client/tcprelay.py", line 82, in handle
    dsock = mux.connect(dev, self.server.rport)
  File "/Users/xxxx/iphone-dataprotection/usbmuxd-python-client/usbmux.py", line 235, in connect
    return connector.connect(device, port)
  File "/Users/xx/iphone-dataprotection/usbmuxd-python-client/usbmux.py", line 206, in connect
    raise MuxError("Connect failed: error %d"%ret)
MuxError: Connect failed: error 3
----------------------------------------

Original issue reported on code.google.com by christop...@gmail.com on 6 Dec 2012 at 11:07

[GoogleCodeExporter]

is there any output on the device screen that indicates an error of some sort ? 
does it display the "OK" in ascii ?

Original comment by jean.sig...@gmail.com on 9 Dec 2012 at 3:33

[GoogleCodeExporter]

The device seems to be properly setup. It shows the "ok" as expected.

Original comment by christop...@gmail.com on 9 Dec 2012 at 10:16

[GoogleCodeExporter]

any other suggestions I can try out? I connected the device to a windows 
machine to see if there were any issues and i still have the same MuxError. My 
Mac is running 10.8.2. Could the cause be related?

Once again, everything seems to work - i get all OK's. I only get an error once 
i try to make the SSH connection. I have tried both on an iPhone4 and an iPad1 
- both of which should work.

Original comment by christop...@gmail.com on 14 Dec 2012 at 10:20

[GoogleCodeExporter]

Here is a patch to enable on-screen debug output of the sshd server. If you 
recompile and regenerate the ramdisk hopefully it should provide some pointers 
on what is going wrong.

Original comment by jean.sig...@gmail.com on 15 Dec 2012 at 12:25

• Changed state: Accepted

Attachments:

• ssh_debug.patch

[GoogleCodeExporter]

done....i now see "proc: table is full"....and it just keeps repeating. The 
"OK" message still appears but then is quickly overrun by the "proc: table is 
full" messages.

Original comment by christop...@gmail.com on 18 Dec 2012 at 6:59

[GoogleCodeExporter]

also, the above message occurred prior to me attempting an SSH connection..

Original comment by christop...@gmail.com on 18 Dec 2012 at 7:00

[GoogleCodeExporter]

This issue was updated by revision e53e03430837.

Original comment by jean.sig...@gmail.com on 30 Dec 2012 at 12:52

[GoogleCodeExporter]

Ok, i suspect somehow the sshd binary was not copied to the ramdisk (the 
build_ramdisk.sh is not very well written and its not obvious when something 
fails). I added some code in commit e53e03430837 to check if the sshd binary is 
there before launching it. Btw, which ipsw are you using to create the ramdisk 
? Thanks

Original comment by jean.sig...@gmail.com on 30 Dec 2012 at 12:57

[GoogleCodeExporter]

iPad 5.0 9A334

Original comment by christop...@gmail.com on 3 Jan 2013 at 2:12

[GoogleCodeExporter]

hey, I do see an error now "/sbn/sshd is missing"..what code changes do I need 
to make to get it add...and appreciate all your help thus far!

Original comment by christop...@gmail.com on 3 Jan 2013 at 2:29

[GoogleCodeExporter]

ok, can you post the output of the make_ramdisk_k48ap.sh script. I tried 
creating the ramdisk with the same ipsw and sshd was copied correctly.
To check this you can edit build_ramdisk.sh and add an "exit" statement just 
before the line "hdiutil eject /Volumes/ramdisk". Then run "ls 
/Volumes/ramdisk/sbin" and check if sshd was copied successfully.
Thanks.

Original comment by jean.sig...@gmail.com on 14 Jan 2013 at 3:13

[GoogleCodeExporter]

no, it does not look to be there...attached a screenshot for 
confirmation...looks like i must be doing something wrong but cant see where it 
would be..

Original comment by christop...@gmail.com on 14 Jan 2013 at 9:55

Attachments:

• ramdisk.png

[GoogleCodeExporter]

Jean, i think we can close this out. I am not sure what the problem was but I 
ended up re-cloning the entire package and it seemed to work. 

The only thing i can think of is my work network prevented some downloads as 
this time i built the ramdisk off network and saw the ssh.tar download actually 
being processed. Wasn't sure if that was because i just re-cloned it or not but 
ssh was the issue we were having.

So in a nutshell, always build the ramdisk on an unrestricted network.

Original comment by christop...@gmail.com on 17 Jan 2013 at 5:15

[GoogleCodeExporter]

closing old issues

Original comment by jean.sig...@gmail.com on 11 Feb 2014 at 10:38

• Changed state: Done