X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 11 Mar 2021 01:25 PM by  Robert Ryans
after time, unable to start a second instance idl 8.7.2
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages

Laurence Schuler



New Member


Posts:
New Member


--
21 Oct 2019 02:20 PM
    Normally we are able to run many copies of idl on this particular host. But some times a process will appear to "lock" the licensing system and when a user tries to start a second instance of the idl program it will fail with this error:

    [lschule3@gs6064srome00 ~]$ idl
    (null): [1,7E1,8,0[73000041,D,400703F3]]
    Failed file open. : Failed file open. (code : 1929379905) (cll_internal.cpp : 498) (code : 1929379905) (CLLFloatingLicenseThread.cpp : 473)
    CLLFloatingLicenseInitialize failed to start the license thread.
    (null): [1,7E1,8,0[73000041,D,400703F3]]
    Failed file open. : Failed file open. (code : 1929379905) (cll_internal.cpp : 498) (code : 1929379905) (CLLFloatingLicenseThread.cpp : 473)
    CLLFloatingLicenseInitialize failed to start the license thread.
    Unable to obtain an IDL license.
    [lschule3@gs6064srome00 ~]$

    We are using a network license server and other machines can start multiple idl copies while this is happening, so it doesn't seem to be related to the license server, it seems host specific. Usually closing the running idl and then starting over fixes things.

    I have not tried removing the /tmp/Harris dir as a similar sounding post suggested, is there a way to check the machines license status?

    --Larry

    Daniel Crawford



    New Member


    Posts:1
    New Member


    --
    01 Apr 2020 08:09 AM
    I'm running into this same issue on Linux, and clearing out /usr/local/harris/license/flexera-sv/ and /tmp/Harris does *not* make a difference.

    Robert Ryans



    New Member


    Posts:1
    New Member


    --
    11 Mar 2021 01:25 PM
    I was looking for an answer for the same question - upgrading my compute machines from CentOS7 to Ubuntu 20.04, and suddenly only one IDL user per machine.

    I tracked the problem down to the following.

    - on start, the IDL binary uses the licence library to create some files in /tmp, specifically one called /tmp/fne.[long string of apparently random characters] - this is a zero byte file, owned by the person running IDL. It's not deleted on exit.
    - The next person who tries to run IDL will try to write to the same file name, and fail, despite the file being configured with 0777 permissions.

    On CentOS, 0777 allows any user to open the file with write permissions, but newer distros - which use systems 241 and later, implement a new security protocol added in kernel 4.19 where even with 0777 permissions the file cannot be written to by anyone other than the owner. This is the new fs.protected_regular sysctl.

    See:

    https://www.spinics.net/lists/fedora-devel/msg252452.html
    https://unix.stackexchange.com/questions/503111/group-permissions-for-root-not-working-in-tmp

    Ubuntu defaults to a non-zero (2) value of fs.protected_regular. If one resets it to zero:

    sudo sysctl fs.protected_regular=0

    then anyone can write to a 0777 file, and multiple users can run IDL on the same system once more.

    Obviously this is not great in terms of security but maybe Harris will update the license manager code if enough people complain.

    I've been dealing with IDL for over 20 years. lmgrd is always pain. Hopefully this will help someone else with the same problem.
    You are not authorized to post a reply.