[Rivet] Fwd: rivet not working on SUSE

[Yallup, David]

Hi,

A while ago I was running some project on a cluster running SUSE, I haven't touched it in a long time however

NAME="openSUSE Leap"
VERSION="42.3"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.3"
PRETTY_NAME="openSUSE Leap 42.3"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.3"
BUG_REPORT_URL="https://bugs.opensuse.org"<https://bugs.opensuse.org>
HOME_URL="https://www.opensuse.org/"<https://www.opensuse.org/>

This was installing Rivet 2.4.3 so quite an old version now, In order to setup Rivet I had the following alias set up (on my normal SL6 os I would just source the rivetenv.sh and yodaenv.sh)

alias setupRivet='source /itp/fast/dyallup/Install/Rivet/local/rivetenv.sh; source /itp/fast/dyallup/Install/Rivet/local/yodaenv.sh; export RIVET_ANALYSIS_PATH=/itp/fast/dyallup/Install/Riv\
et/local/lib64; export RIVET_REF_PATH=/itp/fast/dyallup/Install/Rivet/local/share/Rivet; export RIVET_DATA_PATH=/itp/fast/dyallup/Install/Rivet/local/share/Rivet; export RIVET_INFO_PATH=/it\
p/fast/dyallup/Install/Rivet/local/share/Rivet'


If I try and setup rivet on this machine without exporting the additional environment variables I see the same thing as you, blank output from rivet --list-analyses, when I set my env variables as above it appears to work fine. I think some of these environment variables are now obsolete, but this does appear to work for me at least.

Cheers,
David

On 19/07/18 15:36, Andy Buckley wrote:
Anyone on the Rivet dev list with experience of building and running on SUSE?

This is using the system compiler, I guess, so no danger of e.g. having built plugin libraries in 32 bit and the Rivet core in 64 bit, or similar? Problems like that haven't been seen for quite a while, but I don't have a lot of ideas! Maybe try running the "file" command on some of the Rivet*.so plugin libaries, to make sure they are the right type of file...

Andy

Dr Andy Buckley, Lecturer / Royal Society University Research Fellow
Particle Physics Experiment Group, University of Glasgow





On Jul 19 2018, at 1:14 pm, Francesco Tramontano <francesco.tramontano at cern.ch><mailto:francesco.tramontano at cern.ch> wrote:

Hi Andy, thanks,

the output of the command :

$ rivet -lTRACE --list-analyses
Rivet.AnalysisLoader: TRACE Candidate analysis plugin libs: [ ]


We have also checked that LD_LIBRARY_PATH contains local/lib64 field.

We already tried to set the RIVET_ANALYSIS_PATH but it makes no difference.

Best wishes,
Francesco





On 07/19/2018 01:04 PM, Andy Buckley wrote:
Hi,

Is the RIVET_ANALYSIS_PATH variable set to point at the installed lib
and share/Rivet directories? This shouldn't be necessary for standard
analyses installed as part of the release, but worth checking. You could
also try enabling the "trace" debug output, to see if it is trying to
load the Rivet*.so plugin libraries and failing for some reason: add
-lTRACE to the rivet command line.

Best wishes,
Andy

*Dr Andy Buckley, Lecturer / Royal Society University Research Fellow*
Particle Physics Experiment Group, University of Glasgow


On Jul 19 2018, at 8:41 am, Luca Buonocore <lbuono at na.infn.it><mailto:lbuono at na.infn.it> wrote:



-------- Forwarded Message --------
Subject: rivet not working on SUSE
Date: Thu, 19 Jul 2018 09:36:28 +0200
From: Francesco Tramontano <francesco.tramontano at na.infn.it><mailto:francesco.tramontano at na.infn.it>
<mailto:francesco.tramontano at na.infn.it><mailto:francesco.tramontano at na.infn.it>
To: rivet at projects.hepforge.org<mailto:rivet at projects.hepforge.org> <mailto:rivet at projects.hepforge.org><mailto:rivet at projects.hepforge.org>
CC: Paolo Nason <Paolo.Nason at mib.infn.it><mailto:Paolo.Nason at mib.infn.it>
<mailto:Paolo.Nason at mib.infn.it><mailto:Paolo.Nason at mib.infn.it>, Luca Buonocore <lbuono at na.infn.it><mailto:lbuono at na.infn.it>
<mailto:lbuono at na.infn.it><mailto:lbuono at na.infn.it>



|

Dear authors,

Paolo, Luca and I are having problems to run rivet on a SUSE system.

The compilation using the rivet-bootstrap works flawlessy, but when I do
rivet --list-analyses it returns the command prompt without printing
anything. And in general is unable to find the analyses, although in the
share/Rivet folder all yoda and info files are present.

The same procedure works properly on an Ubuntu system.

Thanks a lot in advance for your assistance.
Best wishes,
Francesco


The operating system is:
NAME="openSUSE Leap"
VERSION="42.3"
ID=opensuse
ID_LIKE="suse"
VERSION_ID="42.3"
PRETTY_NAME="openSUSE Leap 42.3"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:42.3"
BUG_REPORT_URL=*MailScanner has detected a possible fraud attempt from
"bugs.opensuse.org" claiming to be*
<https://bugs.opensuse.org><https://bugs.opensuse.org>"https://bugs.opensuse.org"<https://bugs.opensuse.org>
<https://bugs.opensuse.org><https://bugs.opensuse.org>
HOME_URL=*MailScanner has detected a possible fraud attempt from
"www.opensuse.org<http://www.opensuse.org>" claiming to be*
<https://www.opensuse.org/><https://www.opensuse.org/>"https://www.opensuse.org/"<https://www.opensuse.org/>
<https://www.opensuse.org/><https://www.opensuse.org/>

The compiler version
gcc (SUSE Linux) 4.8.5


And the python version is:
Python 2.7.13


|
_______________________________________________
Rivet mailing list
Rivet at projects.hepforge.org<mailto:Rivet at projects.hepforge.org>
https://www.hepforge.org/lists/listinfo/rivet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20180719/1239b8d2/attachment.html>