Wrong VRLservice on x64 releases of Vray 2.0?

[Reaversword]

Hi, Tonight I've been installing Vray 2.0 for Maya in Linux_x64, and after download the 2012 release, I realized that VRLservice version that download contains is x86 version.

Missed about, I've downloaded others Maya versions of Vray 2.0, and all of them haves VRLservice_x86 versions. So finally, I've installed it, and of course, the only thing I've obtained has been an error in Vray (111), in web browser was impossible to enter in http://localhost:30304.


I was sure that VRLservice_x64 did exist, but quite doubtful about my own memories, so finally I've downloaded some Vray 1.5 linux_64 maya versions and yes, finally there was the VRLservice_x64. Once uninstalled x86 that comes with Vray 2.0, and installed this "new-old" one, all working perfect.

I don't know if its the correct, but right now is how I could get Vray 2.0 for Maya linux_64 working.


Maybe you want update/modify the linux_x64 official releases of Vray 2.o for Maya.

[t.petrov]

Hello,

Unfortunately we can't ship the 64bit version of VRLservice, because it is not stable and we don't know exactly why.
For now we are shipping only 32bit version, which is known to work fine on 64bit linuxes.

Do you have any problems running the 32bit version?

p.s. the installer has 64bit kernel modules for the dongle, so it should work.

[Reaversword]

Yes, how I said, error 111, impossible to enter in http://localhost:30304. Maybe is because I'm running it on Ubuntu, Debian based.

I think that because till I know, there is no problem for install Autodesk Backburner (Only 32 bits) in Fedora/Red Hat, but is no possible to install in Ubuntu (at least, I am not capable to do it). Still so, I could install VRLservice_x86, withing errors, but then was when I encountered the 111 license error, so...

There is any problem if I use VRLservice_x64 from Vray 1.5 version? (Till now all appears work fine).

[veselin.georgiev]

Yes, how I said, error 111, impossible to enter in http://localhost:30304. Maybe is because I'm running it on Ubuntu, Debian based.

I think that because till I know, there is no problem for install Autodesk Backburner (Only 32 bits) in Fedora/Red Hat, but is no possible to install in Ubuntu (at least, I am not capable to do it). Still so, I could install VRLservice_x86, withing errors, but then was when I encountered the 111 license error, so...

Hello,

the 111 error is probably caused by something else; that the license service is 32-bit has never been a problem in our experience. For example, do you start the license service manually, or you did you opt for automatic startup as a service? In the latter case, can you confirm the presence of the service among the running processes by running

ps aux

in a terminal and searching for "vrlservice.exe" in the output? Also, if vrlservice.exe is not present there, can you try to run the service manually and report any error it may be printing out on the screen?

There might be some problems related to your particular Ubuntu installation (it may be lacking some 32-bit libraries provided by the OS for running specific 32-bit applications). Can you enter the following command in a terminal and report its output:

ldd /usr/ChaosGroup/VRLService/linux_x86/bin/vrlservice.exe

(you might need to replace the default path with the correct path to vrlservice.exe).

There is any problem if I use VRLservice_x64 from Vray 1.5 version? (Till now all appears work fine).

This might not work, and even if it does, we don't support this specific scenario.

[Reaversword]

Hi Vesellin, the output, with the x64 version of VRLservice would be:

x_64 version

linux-vdso.so.1 => (0x00007fff4d82d000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f9e7f632000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f9e7f414000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9e7f18e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9e7edfa000)
/lib64/ld-linux-x86-64.so.2 (0x00007f9e7f86d000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f9e7ebf6000)

Im gonna install the x86 one, and I post it to you

x_86 version:

linux-gate.so.1 => (0xf77a1000)
libgcc_s.so.1 => /usr/lib32/libgcc_s.so.1 (0xf7760000)
libpthread.so.0 => /lib32/libpthread.so.0 (0xf7747000)
libm.so.6 => /lib32/libm.so.6 (0xf7721000)
libc.so.6 => /lib32/libc.so.6 (0xf75c4000)
/lib/ld-linux.so.2 (0xf77a2000)
libdl.so.2 => /lib32/libdl.so.2 (0xf75c0000)

By the way, appears I can to have installed two VRLservices without problem.

When I try to execute the x86 version, message says... er, maybe the translation sound really bad, but: "rape of segment", I don't know if translation gonna be all correct you need, but I can't do more. Finally, here an image:



For if its useful, I never register the service, always launch form a terminal, and when I finish, Control-C & exit.

Respect you don't support this specific scenario, I'd be enchanted to be using the Vray 2.0 VRLservice, but what can I do for now?. If we don't find a solution, I must keep using x64 version of Vray 1.5 if I want use the render engine!.

A greeting, Veselin.

[veselin.georgiev]

Hello,

it seems that a crash occurs when you launch the license server. This is a known issue, but it happens quite seldom, and our usual suggestion in that case is to try the most up-to-date WIBU drivers from the website of the dongle manufacturer: http://www.wibu.com/downloads-user-software.html (go to WibuKey runtime for Linux and download the .DEB packages — you need the 32-bit ones).
Let me know if that works for you.
Don't worry, we won't leave you without a working license server! If the aforementioned driver update doesn't fix the crash, we have yet another possible solution, but it's slightly more complicated, so let's try the driver update first.

[Reaversword]

Impossible install 32-bit deb WibuKey: "Error: Wrong Architecture (i386)"

[veselin.georgiev]

Hello Reaversword,

You were right - my bad. You got to use the 64-bit ones, but I see now that Wibu does not offer any newer drivers (opposed to the ones we currently ship).
So we're on plan B - getting you a different, x64-based build. I'll prepare it tomorrow and I'll keep you posted on how to proceed for downloading it.

[Reaversword]

Perfect Veselin, tomorrow we try it with the new ones.

[Zdravko]

Could you please send us an e-mail to: support@chaosgroup.com about that issue so we could provide you with the License server for Linux installation?

[Reaversword]

Done Zdravko!.

[Reaversword]

I received it and it works, but what kind of failures/unstabilities Can I expect?

Appears it must recalculate whatever it needs to calculate every time I launch OpenCl render, when usually, Vray 2.0 do this the only first time we launch openGl render, right?

[vlado]

I received it and it works, but what kind of failures/unstabilities Can I expect?

Appears it must recalculate whatever it needs to calculate every time I launch OpenCl render, when usually, Vray 2.0 do this the only first time we launch openGl render, right?

Yes, we noticed that this happens on some systems, and we will look into it. I think newer OpenCL drivers have their own caching too, so that should fix the problem.

Best regards,
Vlado

[Reaversword]

Ok Vlado, I'll take a look at the drivers issue.


Updated from 270.XX to 280.13, now Rt has stopped of work, neither cpu nor gpu (?!). And Gnome keeps going at third workspace when I push Maya render button when Vray render engine its active.

Nevermind!, too much things of the render engine trying to work well at time, steppy by steppy Chaos, stereoscopy, maya for windows, for linux, new features of Max for implementing in Maya, VRLservices x64 for linux...


Take it easy.