ID |
Date |
Author |
Topic |
Subject |
134
|
02 Mar 2008 |
Exaos Lee | Bug Report | ROODY kills analyzer too!! |
I compiled roody svn231 with ROOT 5.18.00 and gcc 4.1 on Debain Linux 4.0 (AMD64).
I tested the roody with the "examples/experiment" in MIDAS svn4124 and
encountered the following error:
Error in <TFile::TFile>: file /last.root does not exist
*** Break *** segmentation violation
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1090525536 (LWP 17985)]
0x00000000004114e6 in root_server_thread (arg=<value optimized out>) at src/mana.c:5333
Current language: auto; currently c++
(gdb) next
[midas.c:2416:bm_validate_client_index,ERROR] Invalid client index 1 in buffer 'SYSMSG'. Client name '', pid 0 should be 17973
0x00002b800b8a5460 in sighandler () from /opt/ROOT/Versions/Current/lib/libCore.so.5.18
(gdb) next
Single stepping until exit from function _Z10sighandleri,
which has no line number information.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x00002b800b8a546e in sighandler () from /opt/ROOT/Versions/Current/lib/libCore.so.5.18
ptrace: 娌℃湁閭d釜杩涚▼.
(gdb) next
Single stepping until exit from function _Z10sighandleri,
which has no line number information.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x00002b800b8a546e in sighandler () from /opt/ROOT/Versions/Current/lib/libCore.so.5.18
ptrace: 娌℃湁閭d釜杩涚▼.
(gdb) next
Single stepping until exit from function _Z10sighandleri,
which has no line number information.
Cannot remove breakpoints because program is no longer writable.
It might be running in another process.
Further execution is probably impossible.
0x00002b800b8a546e in sighandler () from /opt/ROOT/Versions/Current/lib/libCore.so.5.18
The system information is as the following:
$ uname -a
Linux daq-heg 2.6.18-5-amd64 #1 SMP Sat Dec 22 20:43:59 UTC 2007 x86_64 GNU/Linux
$ gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --enable-mpfr --enable-checking=release
x86_64-linux-gnu
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
$ root-config --config
linuxx8664gcc --prefix=/opt/ROOT/Versions/5.18.00-gcc
--datadir=/opt/ROOT/Versions/5.18.00-gcc/share
--docdir=/opt/ROOT/Versions/5.18.00-gcc/doc
--incdir=/opt/ROOT/Versions/5.18.00-gcc/include
--libdir=/opt/ROOT/Versions/5.18.00-gcc/lib
--etcdir=/opt/ROOT/Versions/5.18.00-gcc/etc
--elispdir=/opt/ROOT/Versions/5.18.00-gcc/share/emacs/site-lisp --enable-cern
--with-cern-libdir=/usr/lib --enable-fftw3 --enable-gdml --enable-mathcore
--enable-mathmore --enable-opengl --enable-python --enable-qt --enable-roofit
--enable-ruby --enable-shared --enable-soversion --enable-ssl --enable-xml
--enable-xft --enable-xrootd --enable-g4root
--with-g4-incdir=/opt/GEANT4/Versions/9.0.p01/include
--with-g4-libdir=/opt/GEANT4/Versions/9.0.p01/lib/Linux-g++
Any idea to fix this problem? |
135
|
03 Mar 2008 |
Randolf Pohl | Bug Report | ROODY kills analyzer too!! |
Hi,
I had the very same problem last summer during our beam time. Don't know the revision, but it was the tarball I downloaded around mid-July.
Symptom: The MIDAS (online) analyzer crashed as soon as roody was started. Started, i.e. before any user interaction became even possible. And the crash happened always. 100.0%.
My workaround was: Use roody rev. 220.
No crashes, beam time saved.
I attach 2 outputs I saved at that time.
Oh, yes: I still have the sources and such. Last modified date is July 9 and earlier (see attachment 3). I can send them around if you want to find the revision and bracket the offending commits. (I wish you were using "git". Ever read about git-bisect?)
Cheers,
Randolf
PS: Konstantin, I had promised you to try and pin down the problem after the run. Obviously I forgot, sorry. Please tell me if I can be of any help now. |
137
|
04 Mar 2008 |
Exaos Lee | Bug Report | Revision 221 works! But not remotely. |
I recompiled the roody of revision 221 and found this revision works. But when I run roody remotely, it still keeps killing the analyzer 100%.
Hope somebody can fix it. |
138
|
07 Mar 2008 |
Randolf Pohl | Bug Report | Revision 221 works! But not remotely. |
Hi,
Exaos Lee wrote: | I recompiled the roody of revision 221 and found this revision works. But when I run roody remotely, it still keeps killing the analyzer 100%.
|
We used 220 (not 221) successfully, but only locally.
Now that you say it I think I recall I could not get roody to run remotely. Don't remember the exact reasons, though.
What I did then was to "ssh -X" from the remote machine into the backend and start roody there (Actually a button with a beautiful picture enabled the users to do so).
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?
I don't have my machines set up at the moment. One of the machines stayed in a box at PSI. So I can't really help you, I am sorry. I think it's time for the specialists now. Anybody there???!?!
Good luck,
Randolf |
139
|
07 Mar 2008 |
Stefan Ritt | Bug Report | 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. |
153
|
03 Jun 2014 |
Dan Melconian | Bug Report | Zeroing spectra using XML data source? |
When we connect using TNet, we can zero spectra on the fly (which is
super-useful). Using Xml (which is infinitely faster to load), it says
"ResetAll: http://trinatdaq:9091: not implemented". I guess the Xml way is
reading a text file rather than accessing the root file, so it isn't exactly
trivial to implement this, eh? However, if someone brilliant knows how to do
this, that would really be great as it is really a nice feature when debugging
things. |
154
|
19 Mar 2021 |
Alexey Kalinin | Bug Report | roody failed to start |
roody failed to start with -P flag
running rootana analyzer with -P argument
commenting RecursiveRemove in TNetDirectory(.cxx .h) (rootana) helps.
Any other suggestions?
Alexey. |
155
|
26 Mar 2021 |
Alexey Kalinin | Bug Report | roody failed to start |
Also,
Mine TDirectory fOnlineHistDir (rootana online ) has more then 1000 histograms
with difficult hierarchy. Starting roody -P (TNEtDirectory support) takes 30-60
seconds, when jsroot THttpServer ready to go in a moment.
> roody failed to start with -P flag
> running rootana analyzer with -P argument
> commenting RecursiveRemove in TNetDirectory(.cxx .h) (rootana) helps.
> Any other suggestions?
> Alexey. |
146
|
25 May 2011 |
Jackie Glister | Forum | Refresh problem when drawing groups |
I'm having a Roody refresh problem: when I draw groups in online mode the entire
canvas is refreshed with the most recently selected single histogram, instead of
the group. I used svn to install the most recent version (svn checkout
svn://ladd00.triumf.ca/roody/trunk roody). Any help would be greatly appreciated! |
147
|
23 Feb 2012 |
Exaos Lee | Forum | How to access the SVN repo anonymously? |
I found that the SVN repo is forbidden for anonymous users now. |
148
|
13 May 2012 |
Konstantin Olchanski | Forum | How to access the SVN repo anonymously? |
> I found that the SVN repo is forbidden for anonymous users now.
Please use username "svn", password "svn", per instructions here:
http://www.triumf.info/wiki/DAQwiki/index.php/DaqSvn
K.O. |
149
|
24 May 2012 |
Konstantin Olchanski | Forum | How to access the SVN repo anonymously? |
> I found that the SVN repo is forbidden for anonymous users now.
It is possible that you are referencing the SVN repo using the "svn:" access method. This access method was recently
disabled.
Please switch to the "https:" method (username/password svn/svn) using this command:
cd .../roody
svn switch --relocate svn://ladd00.triumf.ca/roody https://ladd00.triumf.ca/svn/roody
K.O. |
150
|
24 May 2012 |
Konstantin Olchanski | Forum | test |
test of Roody forum email notification. K.O. |
66
|
30 Sep 2004 |
Joe Chuma | Info | more right click features |
Right click on Offline folder opens the file dialog.
Right click on Online folder opens the hostname dialog.
If only one group exists, you will not be asked to choose the group when adding items to a group. |
68
|
08 Oct 2004 |
Joe Chuma | Info | Roody cvs commit |
Command line argument change:
-h (or -H) followed by nothing shows program usage
-hhostname or -hhostname:port connect to analyzer on given host (and port)
-rsavefile restores savefile
Offline items added to a group are new removed from the group if the
file is closed.
Offline item titles are now displayed after the name if different than
the item name.
"Run# number" added to the item title if the filename contains a runnumber. |
82
|
17 Jan 2005 |
Konstantin Olchanski | Info | CVS instructions |
Updated CVS instructions for ROODY:
1) cvs anonymous read-only access:
export CVS_RSH=ssh
cvs -d anoncvs@dasdevpc.triumf.ca:/usr/local/cvsroot checkout roody
(username: anoncvs, password: anoncvs)
2) read-write cvs access (requires user account on dasdevpc.triumf.ca)
export CVS_RSH=ssh
cvs -d USERNAME@dasdevpc.triumf.ca:/usr/local/cvsroot checkout roody
3) build instructions:
cvs ... checkout roody
cd roody/src
make
./roody {file.root,file.hbook,-Hhostname:port}
K.O. |
96
|
19 Apr 2005 |
Konstantin Olchanski | Info | commited: macosx Makefile bits |
The Makefile bits for building roody on MacOSX have been commited, tested on
MacOSX 10.3.9 with an unknown version of ROOT. Caveats: there is no support for
linking the roody shared library (volunteers are welcome!); there are warnings
about a double-include of libz when linking "roody" (ignore them). K.O. |
100
|
05 Jul 2005 |
Qing Gu | Info | Affect of different root versions on Roody |
After changing ROOT version from root_v4.04.00 to root_v4.04.02, the histograms
don't stay highlighted after clicking, but the top "Roody" bar disappears sometimes. |
104
|
07 Dec 2005 |
Stefan Ritt | Info | roody directory reorganization and Makefile changes |
> 1) roody has been converted from libxml2 to mxml
> 2) the files have been shuffled around so the *.cxx, *.cpp files
> are in the roody/src/ directory, the *.h files are in the
> roody/include/ directory, the Makefile is in the top roody/
> directory which is where the roody executable goes while
> roody.so now goes into the roody/lib/ directory. The mxml
> files are in roody/mxml. The *.o files now go into the
> roody/obj/ directory (which is created by the Makefile if
> it doesn't exist).
> 3) the Makefile has been redone and simplified, and the windows
> stuff removed, since the windows version has its own makefile.
> 4) clicking on the Help About menu item now displays a message box
> with the current version. For now, the code must be edited
> manually for each code revision, but it would be nice to automate
> this.
Compilation under Windows now works fine, many thanks.
I had however a problem under windows. Your scheme with the rootsys.h file does
not work under windows, since the ROOTSYS variable usually points to something
like c:\root. If I follow your scheme, I get following in rootsys.h
const char* rootsys = "c:\root";
where the "\r" is interpreted as a carriage return. I did not find a clever way to
convert this to
const char* rootsys = "c:\\root";
in the Makefile, so for windows I just make it empty, like
const char* rootsys = "";
I changed your src/main.cxx to check for an empty rootsys, and if yes just take
the environment variable. I committed that change, I hope it's ok.
There is one small warning left whern running under windows;
C:\roody>bin\roody
Error in <TWinNTSystem::BaseName>: name = 0
Do I have to worry about that?
- Stefan |
116
|
06 Jun 2006 |
Konstantin Olchanski | Info | Roody still using CVS |
To prevent confusion- according to Joe Chuma and Konstantin Olchanski, we are
still using CVS for Roody development. K.O. |