I have spend a day already trawling the internet, uninstalling, reinstalling etc... so really hope someone can help this lost fellow out... Never had this issue with previous versions.

I am trying to run Maya 2016 in Centos 6.5
Everything installed fine but this is what happens when starting:

If I:
$ su
# Maya
it runs fine...

$ sudo Maya
command not found

but I get this when I try to run as non root user like I would normally:

$ maya

/usr/autodesk/maya2016//bin/maya.bin: /opt/Autodesk/Adlm/R11/lib64/libcrypto.so.10: no version information available (required by /usr/lib64/libssh2.so.1)
/usr/autodesk/maya2016//bin/maya.bin: relocation error: /usr/lib64/libssh2.so.1: symbol EVP_rc4, version libcrypto.so.10 not defined in file libcrypto.so.10 with link time reference

The problem here seems to lie in the libssh libcrypto version being used. Would you agree?

some install instructions (http://goo.gl/u30Gmx):

RHEL 6 and CentOS 6 provide a compatibility package for libssl.so.6 and libcyrpto.so.6. Install this package before installing Maya.

yum install openssl098e-0.9.8e
The Maya installer checks to see if there are existing system library versions, and if so, automatically creates the symbolic links in the Maya lib directory. In some cases, for example if you are running Maya from a network server, this process cannot be done automatically.

If the system versions of the library exist, use them.

su
cd /usr/autodesk/maya2016-x64/lib
ln –s /usr/lib64/libssl.so.10 libssl.so.6
ln –s /lib64/libcrypto.so.10 libcrypto.so.6

So I have done:
$sudo yum update
$sudo yum install openssh libssl.so.6
$sudo yum install openssl098e-0.9.8e
$su
$cd /usr/autodesk/maya2016-x64/lib
$ln –s /usr/lib64/libssl.so.10 libssl.so.6
$ln –s /lib64/libcrypto.so.10 libcrypto.so.6

$ ls /usr/autodesk/maya2016/lib/libssl.so.6 -al
lrwxrwxrwx 1 root root 23 Jun 10 04:06 /usr/autodesk/maya2016/lib/libssl.so.6 -> /usr/lib64/libssl.so.10

ls /usr/autodesk/maya2016/lib/libcrypto.so.6 -al
lrwxrwxrwx 1 root root 26 Jun 10 04:06 /usr/autodesk/maya2016/lib/libcrypto.so.6 -> /usr/lib64/libcrypto.so.10


I guess the question, is why does it work in su and not normal user?

Thanks for any pointers

LW

Maybe you need to run ldconfig as root??? This looks like a specific question for centos forum here.

Hmmm, more info:

I just got this info from doing a:

$yum repolist
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

/usr/lib64/libssh2.so.1: symbol EVP_rc4, version libcrypto.so.10 not defined in file libcrypto.so.10 with link time reference

Please install a package which provides this module, or
verify that the module is installed correctly.

It's possible that the above module doesn't match the
current version of Python, which is:
2.6.6 (r266:84292, Jul 23 2015, 15:22:56)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-11)]

Maybe libssh2 is an old version.. - actually "no version info", from the original post, seems to say it is isn't recognising the current version (ie it is too new!)

How would I determine that? Or how would I go about that?

Thoughts?

on cent 6.5 yum will be basically useless
6.5 has been UNSUPPORTED for a year
6.6 has been unsupported for 3 months



the repos for 6.5 were moved to the historical archives ( last year!! )
there really is nothing to install on 6.5

it is unsupported

please upgrade to the ONLY supported version in the older 6 series CentOS 6.7
or to the current version
CentOS 7.1


i take it you do not know that cent -- like RedHat is very conservative and use rather OLD ( but patched) versions of the software

the major versions of all the software in cent6 were LOCKED back in 2011
and WILL NEVER CHANGE!!!
they will still be the SAME old versions in 2018 when when cent6 support ends ( 2021 for redhat )

the very new 2016 preview of maya might never run on software from 2011



did you manually set up "sudo "

Cent DOSE NOT !!! use "sudo" by default
cent uses
"su " and " su - "
to use "sudo" you have to set it up

Hey thanks for that info. I think I will take your advise and just reinstall using cent 7.1 then replicate it over all the blades.

Sudo has been working for all versions of Maya previously (2014 and 2015).

Project for the weekend I think...

Thanks again John and Rinndalir,

LW

> and did you run maya install as root? it could be maya set permissions on files incorrectly. perhaps install as "normal user" in your home directory if possible.

/usr/autodesk/maya2016//bin/maya.bin: /opt/Autodesk/Adlm/R11/lib64/libcrypto.so.10: no version information available (required by /usr/lib64/libssh2.so.1)
/usr/autodesk/maya2016//bin/maya.bin: relocation error: /usr/lib64/libssh2.so.1: symbol EVP_rc4, version libcrypto.so.10 not defined in file libcrypto.so.10 with link time reference

i was going to say you might not have the right version installed or at all, apparently your aware of that

still: if it works as root then either your BASH ENV differs or (crypto or maya) file permissions, almost 99 that's going to be why

p.s. permissions on soft-links do not count the same way as normal permissions (see man pages), and programs which try to change them using ln(1) are broken programs: it doesn't work that way

> /opt/Autodesk/Adlm/R11/lib64/libcrypto.so.10 no version information

i bet it's an unreadable soft link

1st thing you should tell us is whether as normal user you could open it with hexedit(1) to verify it even exists ...

Ha! I got it. Thanks for all the help guys.

Someone somewhere on some site used the command: ldd [executable file] to show the libs being used

so as sudo then normal user I did:

$ sudo ldd /usr/autodesk/maya2016/bin/maya.bin
libssl.so.10 => /lib64/libssl.so.10 (0x00007fb46f94c000)
libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007fb46f565000)

$ ldd /usr/autodesk/maya2016/bin/maya.bin
libssl.so.10 => /opt/Autodesk/Adlm/R11/lib64/libssl.so.10 (0x00007f5417dff000)
libcrypto.so.10 => /opt/Autodesk/Adlm/R11/lib64/libcrypto.so.10 (0x00007f5417a0f000)

Knowing sudo works and normal user doesn't, I just relinked to the ones sudo is using:

$ cd /opt/Autodesk/Adlm/R11/lib64
$ sudo mv libcrypto.so.10 libcrypto.so.10.old
$ sudo mv libssl.so.10 libssl.so.10.old
$ sudo ln -s /lib64/libcrypto.so.1.0.1e libcrypto.so.10
$ sudo ln -s /lib64/libssl.so.1.0.1e libssl.so.10

Note here that I tracked ssl and crypto back to their original files rather than just using the symlink

As an example of how I did this, I could see the file I wanted to link to is /lib64/libcrypto.so.10 but an 'ls -al' showed it is actually just a symlink to the original (actual) file which is /lib64/libcrypto.so.1.0.1e

ls /lib64/libcrypt* -al
-rwxr-xr-x. 1 root root 40816 Mar 6 2015 /lib64/libcrypt-2.17.so
-rwxr-xr-x. 1 root root 1440448 Jun 24 2014 /lib64/libcrypto.so.0.9.8e
lrwxrwxrwx. 1 root root 19 Oct 27 07:33 /lib64/libcrypto.so.10 -> libcrypto.so.1.0.1e
-rwxr-xr-x. 1 root root 2012880 Jun 30 00:48 /lib64/libcrypto.so.1.0.1e
lrwxrwxrwx. 1 root root 19 Oct 27 07:44 /lib64/libcrypto.so.6 -> libcrypto.so.0.9.8e
lrwxrwxrwx. 1 root root 22 Oct 24 15:55 /lib64/libcryptsetup.so.4 -> libcryptsetup.so.4.6.0
-rwxr-xr-x. 1 root root 162512 Mar 6 2015 /lib64/libcryptsetup.so.4.6.0
lrwxrwxrwx. 1 root root 25 Oct 26 09:42 /lib64/libcrypt.so -> ../../lib64/libcrypt.so.1
lrwxrwxrwx. 1 root root 16 Oct 24 15:52 /lib64/libcrypt.so.1 -> libcrypt-2.17.so

so I linked directly to that and that solved it!