Recently we decided to move our license server (3.0 protocol ver. 7) that was running on an old Windows 7 64-bit and transition it to License Server 4.3.1 running in a VM Ubuntu 16.04.2 64-bit install, Got the service running as well as WIBU-KEY network server and monitor with the dongle/s passthrough to the VM, all detected fine but we started to notice a few issues that resorted in us reverting back to our old server.
1) When we distributed rendering our nodes would fail to pickup a render node license even though it says there were licenses free.
2) We noticed that licenses were no longer freeing up as quickly but now taking exactly 100 seconds.
3) We had to restart the server a few times because licenses were not always freeing up and it said licenses were being taken by machines that had long since stopped rendering or the VRAY panel has been closed yet the last access time kept resetting to 0 as if they were still in use.
We would like to continue running the license server in linux on a VM and retire the old hardware but we really need to fix these issues firstly. Any ideas what could be the issue?
I’ve asked our colleagues who are dealing with the V-Ray licensing issues to assist, so they will post here shortly.
Please check:
1. Are the dongle drivers the latest version - for Linux - https://www.wibu.com/downloads-user-software/file/download/3630.html
2. Does the same issue appear on the Ubuntu if you use the old licence server? - https://download.chaosgroup.com/downloads/282/licenseserver-standalone-30503-adv
3. Is the firewall on the Ubunu machine allowing TCP port 30304 for in/out communication?
Please also note that WIBU-KEY network server and monitor are not necessary for the dongle (although you might use them for monitoring) just the drivers should be present and a normal pass-through of the USB.
Can you also tell what hypervisor are you running the VM on?
1. Yes using 6.40 DEB
2. Good question I will try this out when I get a moment
3. I believe so as we can access UbuntuIP:30304 elsewhere on the network and view current usage, also speaking off when we submit jobs to DR and refresh page sometimes it seems to lose connection to the dongles and show an error message for a few seconds where it would normally have the two buttons to view vray licenses / render node licenses (on 4.3.1 with Ubuntu)
Didn’t know that we only need the WIBU-KEY driver, I will uninstall the network server and monitor and just try with the driver too. (Is there a standalone driver? Only found wkrt-lin_6.40.2402.500_amd64.deb)
We are using ESXI 6.0.2.
Just realized we didn’t install Axprotector which looks to be required, just installed it now. (axprotector_9.55.2405.502_amd64.deb)
Also the WIBU-KEY network server and monitor installed automatically with the 6.40 driver I think.
We are going to test the old license server you linked for a few hours, we uninstalled 4.3.1 and have 3.0503 installed, how do we go about starting the license server as a service deamon? It was more straight forward with 4.3.1, currently we are initializing via Terminal “sudo ./vrlservice” But would rather have it autostart which it currently isn’t doing.
Please note that when installing V-Ray and the license server it’s best to do it without sudo and let the installer prompt for permissions, otherwise folder permissions are often set incorrectly (to install without GUI you can use -gui=0)
That being said - to register license server 3.05 you can use the /usr/ChaosGroup/VRLService/linux_x64/bin/registerLicenseServerAsService script
Good to know thank you, Since running 3.05 on the linux vm licenses are freeing up quickly again for us but now for some reason wibu-key keeps dropping one of our two dongles and then it reconnects.
Unfortunately there are sometimes problems with the license server, installed on VMs - and also dongle licensing is not officially supported on VMs.
A workaround might be to transfer all licenses on 1 dongle if the first dongle is always stable and the second one - not. Same applies if the issue occurs when there is more than one dongle.
That work around will be ideal as we no longer require multiple dongles. What is the procedure?
Could you please crate a ticket in our system for this request by sending an email to support@chaosgroup.com
My colleagues will explain you the procedure in details, but at the beginning we will need .wbc files generated for the both dongles you have.
Thank you.
