This could be due to the sls.conf file not being read or that the server MAC address is incorrect. Please check the following:
- Confirm that the license file (sls.conf) is placed on the license server in: /usr/local/StarDrop/sls/var/run
- Check that the license file is readable by user ‘nobody’. You can be checked with the command: chmod a+r sls.conf
- After this, please restart the license server with the command: /etc/init.d/StarDrop_sls restart
If you are using the containerised servers, please copy the floating license file sls.conf to the license directory on your server. The default path is:
/opt/stardrop/license/
but you may need to replace /opt if you chose a different path for your installation.
Finally, restart the license server by typing:
systemctl restart stardrop-license
If these steps do not resolve the problem, please send us the contents of the log file /usr/local/StarDrop64/sls/var/log/sls.log (legacy servers) or /opt/stardrop/license log/sls.log , to support@optibrium.com.
It feels like only yesterday that we announced the arrival of StarDrop 8. And here we are again. Though this time, that’s rather the point. Discovery teams need to iterate quickly, moving from hypothesis…
Download the guide and learn what generative chemistry is, where it fits in the discovery workflow, and best practices to avoid common pitfalls.