Re: Re: Re: Re: Remote Kernel
- To: mathgroup at smc.vnet.net
- Subject: [mg73169] Re: [mg73139] Re: [mg73110] Re: [mg73075] Re: [mg73026] Remote Kernel
- From: "T.Sariyski" <tsariysk at craft-tech.com>
- Date: Tue, 6 Feb 2007 02:59:00 -0500 (EST)
- References: <200701301124.GAA12853@smc.vnet.net> <200702010831.DAA10807@smc.vnet.net> <200702030948.EAA06211@smc.vnet.net> <200702041241.HAA17801@smc.vnet.net>
I still get the same "Low-level MathLink error": Mathematica could not establish a connection to the kernel. Kernel: craft99. Low-level MathLink error: The linkname was missing or not in the proper form. Here are the Kernel Configuration Options: Advanced Options: -LinkMode Listen -LinkProtocol TCPIP -LinkOptions MLDontInteract -LinkName "3500" -LinkHost 192.168.187.99 Shell command to launch kernel: ssh tsariysk at 192.168.187.99 ' "math" -mathlink -LinkMode Connect -LinkProtocol TCPIP -LinkName "3500" -LinkHost 192.168.187.99' I did make sure that SSH_AUTH_SOCK environmental variable is visible for both windows and cygwin: I ssh tsariysk at 192.168.187.99 without password from Windows Command Prompt as well as from Cygwin shell. I expect that Mathematica also acknowledges of SSH_AUTH_SOCK but I do not know how to verify it. Is there a debug mode for MathLink or other tools that make troubleshooting more transparent? Thanks, Ted Steve Wilson wrote: > On Feb 3, 2007, at 2:48 AM, T.Sariyski wrote: > > >> I still get an obscure "Low-level MathLink error: The linkname was >> missing or not in the proper form." error when try to connect to a >> remote kernel (client is WinXP/i386, server is SuSe10.1/x86_64, >> same LAN, no firewalls, no passwords). >> >> Arguments to MLOpen >> >> -LinkMode Listen -LinkProtocol TCPIP -LinkOptions MLDontInteract >> -LinkName "3500" -LinkHost 192.168.187.99 >> >> string to launch kernel : >> >> ssh tsariysk at 192.168.187.99 '"math" -mathlink -LinkMode Connect >> -LinkProtocol TCP -LinkName "3500" -LinkHost 192.168.187.99' >> >> > > > Ted, your setup is mixing two different link protocols. You are > mixing TCP and TCPIP. The TCP link protocol is a deprecated protocol > and should not be used. In any case it will certainly not work with > TCPIP. Change the string to launch the kernel to: > > ssh tsariysk at 192.168.187.99 '"math" -mathlink -LinkMode Connect > -LinkProtocol TCPIP -LinkName "3500" -LinkHost 192.168.187.99' > > Assuming there are no other problems on the network this change > should fix your problem. > > > Sincerely, > > > Steve Wilson > Wolfram Research, Inc. > >
- References:
- Re: Remote Kernel does nothing
- From: Arturas Acus <acus@itpa.lt>
- Re: Re: Remote Kernel does nothing
- From: "T.Sariyski" <tsariysk@craft-tech.com>
- Re: Re: Re: Remote Kernel does nothing
- From: Steve Wilson <stevew@wolfram.com>
- Re: Remote Kernel does nothing