 |
 |
Hi Gregory, Could you send the complete xrootd log corresponding to the crashed server? Also, did you recompile or use the binary that came with the rpm. If you recompiled, please do a "configure --build=debug" prior to compilation so that we can get the actual statement numbers and variables in the trace. Thanks. Andy On Tue, 12 Apr 2005, Gregory Schott wrote: > > > On Tue, 12 Apr 2005, Peter Elmer wrote: > > >>> (With my Babar hat on): note that you shouldn't be deploying this > >>> development version at FZK on the systems used by BaBar. This version > >>> is under test, not for production use. > >>> > >>> BTW, if you are still worried about the DNS problems, did you see my > >>> mail about this the other day? (i.e. Jos checked and fixed the /etc/hosts > >>> files, so could you check again that you still have the DNS problem/crash?) > >> > >> Yes, I saw that. There are now no problem on the server for which the > >> hosts were changed. It seems Jos forgot 3 of the servers so for the moment > >> I am runnig an old version there. (The latest dvlp version 20050328-0656 > >> also do not work with the DNS problem: I understood from your announcement > >> that the DNS problem was fixed there.) > > > > Ok, this is useful to know in any case. Andy added code that tries to > > detect and avoid crashing for odd DNS configurations (plus he added some > > printout to help debugging). When you say that it doesn't work, what do you > > mean? Does it crash? Does it just exit and refuse to run? Could you send the > > traceback and/or logfile so Andy could take a look at it? > > What crashes is xrootd on the dataserver. It crashes the same way as it > did in the previous version: > > (gdb) backtrace > #0 0xb7407198 in strcmp () from /lib/tls/libc.so.6 > #1 0x08079d31 in XrdNet::Trim () > #2 0x0806d2b1 in XrdLink::Alloc () > #3 0x080790b1 in XrdInet::Accept () > #4 0x0806f6d7 in main () > > -- Gregory >