Data Backup and Recovery

SC 3.5.0c Linux install - bad libs?

JIM_SURLOW
8,982 Views

I recently received a copy of 3.5.0c.  Untarred it onto a new CentOS 5.7 and placed it into /usr/local as per the 3.4 documentation (don't know if there is a 3.5 docs anywhere).

Then went to run it and received ...

[root@81377-sanperf scServer3.5.0c]# ./snapcreator --profile setup

Panic: '/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so' is not an ActivePerl library

A quick ldd …

[root@81377-sanperf scServer3.5.0c]# ldd snapcreator

linux-vdso.so.1 =>  (0x00007fff413fd000)

libnsl.so.1 => /lib64/libnsl.so.1 (0x0000003985200000)

libdl.so.2 => /lib64/libdl.so.2 (0x0000003982e00000)

libm.so.6 => /lib64/libm.so.6 (0x0000003983600000)

libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003984a00000)

libutil.so.1 => /lib64/libutil.so.1 (0x0000003985a00000)

libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003983e00000)

libc.so.6 => /lib64/libc.so.6 (0x0000003982a00000)

/lib64/ld-linux-x86-64.so.2 (0x0000003982600000)

Not sure where to go from here

Thanks,

Jim

1 ACCEPTED SOLUTION

JIM_SURLOW
7,086 Views

I found out that the template that I was using for CentOS had a noexec /tmp partition.  snapcreator runs now.

View solution in original post

21 REPLIES 21

EEntressangle
2,041 Views

I just ran into the same issue for scServer4.1.2. Is there another way to fix this issue ? Or do I really have to remove the "noexec" mounting option for /tmp file system ? (Which may not be safe)

Thanks

Regards

Eric

Public