Print

Print



  Hi,

  As Pete said, the libNetx.so client lib is not build (yet) on Windows.
  Enabling this is on our todo list, but it was not given the highest
  priority, as nobody asked for it so far.
  We do not expect particular problems with netx on Windows, but it needs
  to be tried and tested. To my knowledge, nobody has tried to build on
  Win32GDK.   
  I will try to make at least the basic tests soon, so that interested
  people can start testing.
  
  Gerri

  ps: 
      1. giving explicitly the port number in the url should not be 
         necessary if you add the following line to /etc/services

rootd           1094/tcp                        # ROOT daemon

      2. to avoid loading explicitely libThread.so before libNetx.so
         create the 'rootmap' executing 'gmake map' after 'gmake'.
         (This is something introduced recently to avoid an
          'explicitlink' with all the libraries as basically done
          before). 

    
On Sun, 27 Feb 2005, Fabrizio Furano wrote:

> Hi all,
> 
>   I recently spoke with Gerri about that. He said that the stuff 
> compiled, from what I can remember, and that it needed a test as deep as 
> we are used to do for unixes. I really don't know why netx is missing in 
> the standard windows distribution, but this may be a reason. Maybe Gerri 
> or Fons have tha answer for this and about how long will it take to 
> validate TXNetFile under Win32.
> 
> Fabrizio
> 
> Peter Elmer wrote:
> >   Hi Andy,
> > 
> > On Sat, Feb 26, 2005 at 06:14:08PM -0800, Andrew Hanushevsky wrote:
> > 
> >>Whatever you are doing is triggering root to use root protocol not xroot
> >>protocol. Now, your xroot server has not been configured to also run root
> >>protocol. So, when you get there it doesn't know what to do with you and
> >>simply closes the connection. I suspect that using uid/pswd authentication
> >>(which is not currently supported in xroot) is causing it to step down a
> >>notch and try root protocol.
> > 
> > 
> >   As you'll probably see from the subsequent postings, we determined that
> > TXNetFile is not being built by default in the Windows builds of ROOT and 
> > thus the protocol "root://..." will try to use the old TNetFile. Gerri or
> > Fabrizio will have to say where we are with TXNetFile on Windows.
> > 
> >                                    Pete
> > 
> > 
> > 
> >>On Sat, 26 Feb 2005, Peter Elmer wrote:
> >>
> >>>  Hi Matt,
> >>>
> >>>On Sat, Feb 26, 2005 at 11:17:42AM -0800, Langston, Matthew David wrote:
> >>>
> >>>>I know this configuration works because I am able to read ROOT files
> >>>>(histograms, trees, etc.) using our Java xrootd client. However, when
> >>>>I try to use the ROOT 4.02.00 command line I get this error from ROOT:
> >>>>
> >>>>root [0] myfile myfile = TFile::Open("root://glast01.slac.stanford.edu//nfs/farm/g/glast/u07/mcenery/systests/GlastRelease/v6r2p1/VerticalGamma100MeV/linux/VerticalGamma100MeV_Histos.root");
> >>>
> >>><...>
> >>>
> >>>>Error in <TWinNTSystem::SendRaw>: cannot send buffer
> >>>>Info in <TAuthenticate::Authenticate>: attempted methods SSH/UidGid are not supported by remote server version
> >>>>Info in <TAuthenticate::Authenticate>: failure: list of attempted methods: UsrPwd SSH UidGid
> >>>>Error in <TPSocket::Authenticate>: authentication failed for [log in to unmask]
> >>>>Error in <TNetFile::TNetFile>: can't open connection to rootd on host glast01.slac.stanford.edu at port 1094
> >>>>Error in <TNetFile::Create>: authentication attempt unsuccessful
> >>>>root [1]
> >>>
> >>>   I don't have any experience with using the TXNetFile client on Windows.
> >>>There were some outstanding issues, but I don't recall if they've been dealt
> >>>with yet. Maybe Gerri or Fabrizio can comment.
> >>>
> >>>  One thing that is clear above is that you are not getting the right client
> >>>from the root plugin manager (i.e. you got the old TNetFile instead of the
> >>>new TXNetFile). We should probably figure out why that is happening first.
> >>>From etc/system.rootrc I would expect "root://" to default to TXNetFile
> >>>for all platforms. I don't see any platform ifdef's there, so something else
> >>>must be going wrong.
> >>>
> >>>  I guess the java client is the one that Tony has mentioned in his CHEP
> >>>talk?
> >>>
> >>>                                   Pete
> >>>
> >>>
> >>>
> >>>>And this is what I get in the xrootd log file:
> >>>>
> >>>>glast@glast01 $ tail -f /tmp/xrootd/xrdlog
> >>>>050226 10:44:11 3310 XrdLink: ?:45@ntvpn2-008 disconnected after 0:00:00 (matching protocol not found)
> >>>>050226 10:44:12 3310 XrdLink: ?:45@ntvpn2-008 disconnected after 0:00:00 (matching protocol not found)
> >>>>
> >>>>In the ROOT stack trace, I see that it is trying to login as "[log in to unmask]". OK, so I try telling ROOT to use anonymous credentials using this:
> >>>>
> >>>>root [1] TAuthenticate::SetGlobalUser("anonymous");
> >>>>
> >>>>However, I get the same "authentication attempt unsuccessful" error, except that now the ROOT stack trace reports that "[log in to unmask]" is not authorized.
> >>>>
> >>>>What am I doing wrong? Is it a ROOT configuration problem (perhaps something needs to go into .rootrc), is it an xrootd configuration problem? What does the "matching protocol not found" mean in the xrootd log file? What protocol is it talking about - perhaps an authentication protocol that I need to configure?
> >>>>
> >>>>As I mentioned, our Java client is able to read ROOT files from our simple xrootd server without problems. Our Java client sends "anonymous" for the username and "langston@trinity" for the password. This is what I get from the xrootd log file when connecting using our Java client:
> >>>>
> >>>>glast@glast01 $ tail -f /tmp/xrootd/xrdlog
> >>>>050226 11:08:30 3310 XrootdXeq: User logged in as anonymou.12345:45@ntvpn2-008
> >>>>050226 11:08:38 3310 XrdLink: Unable to receive from anonymou.12345:45@ntvpn2-008; connection reset by peer
> >>>>050226 11:08:38 3310 XrdLink: anonymou.12345:45@ntvpn2-008 disconnected after 0:00:11 (link read error)
> >>>>
> >>>>Even though there is a "connection reset by peer" and a "link read error" message, the Java client is still able to read histograms and trees just fine.
> >>>>
> >>>>Any help on getting the ROOT command line to be able to read files from our xrootd server would be appreciated.
> >>>>
> >>>>Warmest regards, Matt
> >>>>
> >>>
> > 
> > 
> > 
> > -------------------------------------------------------------------------
> > Peter Elmer     E-mail: [log in to unmask]      Phone: +41 (22) 767-4644
> > Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland
> > -------------------------------------------------------------------------
>