Back Midas Rome Roody Rootana
  Root Display GUI  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
Entry  02 Mar 2008, Exaos Lee, Bug Report, ROODY kills analyzer too!! 
    Reply  03 Mar 2008, Randolf Pohl, Bug Report, ROODY kills analyzer too!! crash-analyzer.txtcrash-roody.txtroody-tarball-dir.txt
       Reply  04 Mar 2008, Exaos Lee, Bug Report, Revision 221 works! But not remotely.  
          Reply  07 Mar 2008, Randolf Pohl, Bug Report, Revision 221 works! But not remotely.  
             Reply  07 Mar 2008, Stefan Ritt, Bug Report, Revision 221 works! But not remotely.  
    Reply  17 May 2009, Randolf Pohl, Bug Fix, [PATCH] ROODY kills analyzer too!! 
       Reply  23 Jul 2009, Exaos Lee, Bug Fix, [PATCH] ROODY kills analyzer too!! 
Message ID: 139     Entry time: 07 Mar 2008     In reply to: 138
Author: Stefan Ritt 
Topic: Bug Report 
Subject: Revision 221 works! But not remotely.  

Randolf Pohl wrote:
Just an idea: Are all necessary ports open on the receiving machine? Maybe the analyzer is just collateral damage, in reality roody commits suicide because the firewall is nasty to him?


The connection between ROODY and the analyzer works only on a single port, but if anybody wants to connect via the underlying MIDAS layer there is a two-way communication: 1) "odbedit -h <host>" connects to host <host> on port 1175 and 2) mserver on <host> connects back to odbedit on an arbitrary port. For 2), one has to excempt the client program (in this case odbedit) from the firewall for all ports on the remote client and the server program port 1175 on the <host> machine. But I'm not sure if this is your problem right now.
ELOG V3.1.4-2e1708b5