Re^5: Net::OpenSSH connection failing with 'muxserver

AIX truss may accept some option to make it also dump syscall arguments (as those passed to bind). Otherwise a debugger could be used to inspect them, but this is quite more difficult.

Calling SSH with the verbose flag may also give some useful information:

$ssh=Net::OpenSSH->new($host, master_opts => '-vvv',...)
[download]

Finally, witch version of OpenSSH are you using?

Comment on Re^5: Net::OpenSSH connection failing with 'muxserver_listen bind(): Not owner' Download Code

Replies are listed 'Best First'.
Re^6: Net::OpenSSH connection failing with 'muxserver_listen bind(): Not owner' by Only1KW (Sexton) on Sep 02, 2011 at 13:56 UTC
I don't see any option for truss that would dump the arguments. Verbose doesn't offer any new help: `debug1: Authentication succeeded (keyboard-interactive). debug1: setting up multiplex master socket muxserver_listen bind(): Not owner` [download] `~> ssh -V OpenSSH_5.1p1, OpenSSL 0.9.8j 07 Jan 2009` [download]	[reply] [d/l] [select]
Re^7: Net::OpenSSH connection failing with 'muxserver_listen bind(): Not owner' by salva (Canon) on Sep 02, 2011 at 15:35 UTC
The only thing that comes to my head is that the multiplexing socket path could surpass the 108 chars of the sockaddr_un struture passed to bind. You could try running ssh from the command line enabling the multiplexing feature with different paths, for instance: `ssh -x2M -S /tmp/mux localhost ls` [download] If that works, you could try with the exact same command executed by Net::OpenSSH. You will be able to see after enabling debug mode on your script: `$Net::OpenSSH::debug=-1;` [download] Besides that, the other thing that can be done is running ssh under the debugger in order to see what is being passed to bind. I would do it myself, but have been unable to find any place offering free AIX accounts on the internet.	[reply] [d/l] [select]