Ticket 16831 - seff fails with: /usr/bin/perl: symbol lookup error: /usr/lib64/slurm/cli_filter_lua.so: undefined symbol: data_init
Summary: seff fails with: /usr/bin/perl: symbol lookup error: /usr/lib64/slurm/cli_fil...
Status: RESOLVED DUPLICATE of ticket 16503
Alias: None
Product: Slurm
Classification: Unclassified
Component: User Commands (show other tickets)
Version: 23.02.2
Hardware: Linux Linux
: 4 - Minor Issue
Assignee: Carlos Tripiana Montes
QA Contact:
URL:
Depends on:
Blocks:
 
Reported: 2023-05-25 23:14 MDT by Chris Samuel (NERSC)
Modified: 2023-05-29 10:33 MDT (History)
2 users (show)

See Also:
Site: NERSC
Slinky Site: ---
Alineos Sites: ---
Atos/Eviden Sites: ---
Confidential Site: ---
Coreweave sites: ---
Cray Sites: ---
DS9 clusters: ---
Google sites: ---
HPCnow Sites: ---
HPE Sites: ---
IBM Sites: ---
NOAA SIte: ---
NoveTech Sites: ---
Nvidia HWinf-CS Sites: ---
OCF Sites: ---
Recursion Pharma Sites: ---
SFW Sites: ---
SNIC sites: ---
Tzag Elita Sites: ---
Linux Distro: ---
Machine Name:
CLE Version:
Version Fixed:
Target Release: ---
DevPrio: ---
Emory-Cloud Sites: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this ticket.
Description Chris Samuel (NERSC) 2023-05-25 23:14:36 MDT 
Hi there,

I noticed that `seff` now fails with:

/usr/bin/perl: symbol lookup error: /usr/lib64/slurm/cli_filter_lua.so: undefined symbol: data_init

It looks like it's loading the Perl Slurm module that triggers that:

csamuel@alvarez:login01:~> perl -MSlurm -e 'print "hello\n"'
perl: symbol lookup error: /usr/lib64/slurm/cli_filter_lua.so: undefined symbol: data_init

If I'm interpreting this right it's just because it doesn't load libslurmfull.so?

csamuel@alvarez:login01:~> LD_PRELOAD=/usr/lib64/slurm/libslurmfull.so perl -MSlurm -e 'print "hello\n"'
hello


All the best,
Chris
Comment 1 Tim Wickberg 2023-05-29 10:33:55 MDT 
Marking as a duplicate of bug 16503 which addressed the symbol issues with the Perl API.

*** This ticket has been marked as a duplicate of ticket 16503 ***