VisIt - не работает в режиме клиент-сервер

31838 ?        Ss     0:00  |       \_ /usr/local/visit/bin/../current/linux-x86_64/bin/python /usr/local/visit/bin/frontendlauncher.py /usr/local/visit/bin/visit -v 2.9 -vcl -debug 5 -noloopback -sshtunneling -host localhos
31847 ?        S      0:00  |           \_ /usr/local/visit/2.9.1/linux-x86_64/bin/vcl -debug 5 -noloopback -sshtunneling -host localhost -port 28806 -key 2accd4caf640
31848 ?        Z      0:00  |               \_ [vcl] <defunct>

/usr/local/visit/2.9.1/linux-x86_64/bin/vcl -noloopback -sshtunneling -host localhost -port 28806 -key 2acc267d4cbe455af640
VisIt component launcher started.
ParentProcess::Connect: Called with (numRead=1, numWrite=2, argc=9, argv={/usr/local/visit/2.9.1/linux-x86_64/bin/vcl, -noloopback, -sshtunneling, -host, localhost, -port, 28806, -key, 2accbe640})
ParentProcess::Connect: hostName = localhost
ParentProcess::GetHostInfo: Calling gethostbyname("localhost")
ParentProcess::Connect: port = 28806
ParentProcess::Connect: securityKey = 2acc267d4cbe455af640
ParentProcess::Connect: Creating sockets
ParentProcess::Connect: Creating read sockets
ParentProcess::GetClientSocketDescriptor: Set up using port 28806
ParentProcess::GetClientSocketDescriptor: Creating a socket
ParentProcess::GetClientSocketDescriptor: Setting socket options
ParentProcess::GetClientSocketDescriptor: Calling connect
(If you see no messages after this one, VisIt was not
able to connect to the client machine.  Nine times out
of ten, this is a firewall issue on the client machine.
It could also mean that VisIt was unable to resolve the
IP address for the client machine.  You may need to verify the contents of /etc/hosts.)
ParentProcess::GetClientSocketDescriptor: Connected socket
ParentProcess::Connect: Creating write sockets
ParentProcess::GetClientSocketDescriptor: Set up using port 28806
ParentProcess::GetClientSocketDescriptor: Creating a socket
ParentProcess::GetClientSocketDescriptor: Setting socket options
ParentProcess::GetClientSocketDescriptor: Calling connect
(If you see no messages after this one, VisIt was not
able to connect to the client machine.  Nine times out
of ten, this is a firewall issue on the client machine.
It could also mean that VisIt was unable to resolve the
IP address for the client machine.  You may need to verify the contents of /etc/hosts.)
ParentProcess::GetClientSocketDescriptor: Connected socket
ParentProcess::GetClientSocketDescriptor: Set up using port 28806
ParentProcess::GetClientSocketDescriptor: Creating a socket
ParentProcess::GetClientSocketDescriptor: Setting socket options
ParentProcess::GetClientSocketDescriptor: Calling connect
(If you see no messages after this one, VisIt was not
able to connect to the client machine.  Nine times out
of ten, this is a firewall issue on the client machine.
It could also mean that VisIt was unable to resolve the
IP address for the client machine.  You may need to verify the contents of /etc/hosts.)
ParentProcess::GetClientSocketDescriptor: Connected socket
ParentProcess::Connect: Exchanging type representations.
ParentProcess::Connect: done
Xfer::Process: Opcode=4, len=118, type=LaunchRPC
Executing LaunchRPC
LaunchService::LaunchProcess: start
LaunchService::LaunchProcess: LaunchRPC command = visit, args=(-v 2.9 -mdserver -debug 5 -noloopback -host localhost -port 25832 -key 2acc267d4cbe455af640 -sshtunneling )
LaunchService::LaunchProcess: end
Xfer::Update: Sending: opcode=5, name=VisItRPC::RPCReply (from LaunchRPC)
Child 0 needs to be read (desc=11)
Lost connection to child 0