Build error on CentOS 5.10

[Dennis Zheleznyak]

Hi all,

I'm trying to build rpms of the latest slurm version on centos 5.10, but I
encounter the following error every single time:

+ /var/tmp/slurm-14.03.8-1/usr/bin/sjobexitmod --roff
/var/tmp/rpm-tmp.79119: /var/tmp/slurm-14.03.8-1/usr/bin/sjobexitmod:
/usr/bin/perl: bad interpreter: Permission denied
error: Bad exit status from /var/tmp/rpm-tmp.79119 (%install)

I tried creating an hello world script to run by perl, to check that it
works and it has.

The command I'm using to build slurm is:
rpmbuild -tb -D 'with_cflags CFLAGS="-O0 -g3"' slurm-14.03.8.tar.bz2

Thank you,
Dennis.

[Christopher Samuel]

Post by Dennis Zheleznyak
+ /var/tmp/slurm-14.03.8-1/usr/bin/sjobexitmod --roff
/usr/bin/perl: bad interpreter: Permission denied
error: Bad exit status from /var/tmp/rpm-tmp.79119 (%install)

What do the following commands say?

file /usr/bin/perl
ls -l /usr/bin/perl
getfacl /usr/bin/perl

Do you have SE Linux enabled?

cheers,
Chris

[Dennis Zheleznyak]

Hi Chris,

* file /usr/bin/perl*
/usr/bin/perl: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for
GNU/Linux 2.6.9, dynamically linked (uses shared libs), stripped

*ls -l /usr/bin/perl*
-rwxr-xr-x 2 root root 19208 Nov 7 2013 /usr/bin/perl

*getfacl /usr/bin/perl*
getfacl: Removing leading '/' from absolute path names
# file: usr/bin/perl
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

*getenforce*
Disabled

Thank you,
Dennis.

Post by Christopher Samuel

Post by Dennis Zheleznyak
+ /var/tmp/slurm-14.03.8-1/usr/bin/sjobexitmod --roff
/usr/bin/perl: bad interpreter: Permission denied
error: Bad exit status from /var/tmp/rpm-tmp.79119 (%install)

What do the following commands say?
file /usr/bin/perl
ls -l /usr/bin/perl
getfacl /usr/bin/perl
Do you have SE Linux enabled?
cheers,
Chris
--
Christopher Samuel Senior Systems Administrator
VLSCI - Victorian Life Sciences Computation Initiative
http://www.vlsci.org.au/ http://twitter.com/vlsci

[Chris Samuel]

Post by Dennis Zheleznyak
Hi Chris,

Hiya,

Those all look fine, but I've just noticed you're building RPMs there and
that's something we don't do with Slurm so I'm afraid I'm not sure I can help
there, sorry! :-(

All the best,
Chris

[Dennis Zheleznyak]

Thank you for trying :)

Post by Chris Samuel

Post by Dennis Zheleznyak
Hi Chris,

Hiya,
Those all look fine, but I've just noticed you're building RPMs there and
that's something we don't do with Slurm so I'm afraid I'm not sure I can help
there, sorry! :-(
All the best,
Chris
--
Christopher Samuel Senior Systems Administrator
VLSCI - Victorian Life Sciences Computation Initiative
http://www.vlsci.org.au/ http://twitter.com/vlsci

[Michael Jennings]

Post by Dennis Zheleznyak
+ /var/tmp/slurm-14.03.8-1/usr/bin/sjobexitmod --roff
/usr/bin/perl: bad interpreter: Permission denied
error: Bad exit status from /var/tmp/rpm-tmp.79119 (%install)

Is your /var/tmp mounted "noexec" by any chance?

Michael

[Christopher Samuel]

Post by Michael Jennings
Is your /var/tmp mounted "noexec" by any chance?

I wondered that but I don't think that'll give the errors that Dennis is
seeing, he's seeing -EACCES for /usr/bin/perl, not for something in
/var/tmp. :-(

[Michael Jennings]

On Thu, Oct 2, 2014 at 4:37 PM, Christopher Samuel

Post by Christopher Samuel

Post by Michael Jennings
Is your /var/tmp mounted "noexec" by any chance?

I wondered that but I don't think that'll give the errors that Dennis is
seeing, he's seeing -EACCES for /usr/bin/perl, not for something in
/var/tmp. :-(

It's trying to run a script in /var/tmp that has #!/usr/bin/perl in
it. So I suspect /usr is mounted noexec.

Michael

[Christopher Samuel]

Post by Michael Jennings
It's trying to run a script in /var/tmp that has #!/usr/bin/perl in
it. So I suspect /usr is mounted noexec.

Hmm, that would make life, umm, interesting. :-)

Dennis, what does "cat /proc/mounts" on this machine say?

cheers!
Chris

[Michael Jennings]

On Thu, Oct 2, 2014 at 5:13 PM, Christopher Samuel

Post by Christopher Samuel

Post by Michael Jennings
It's trying to run a script in /var/tmp that has #!/usr/bin/perl in
it. So I suspect /usr is mounted noexec.

Hmm, that would make life, umm, interesting. :-)

Yes, indeed! :-)

That's the only way I've been able to reproduce that error, though
(apart from what you already covered) -- either noexec on the
filesystem the interpreter is on, or execute permissions on a parent
directory being missing -- and both would be fairly odd for
/usr/bin/perl! :-)

Michael