LMTOOLS – adskflex SHUTDOWN request

I received a call from a large firm recently. Things have been pretty good and all their license servers have been working fine…. except for one. The service that provides the licenses for Autodesk software keeps shutting down. The only “solution” was the restart the service via LMTOOLS. When he called me, I told him that the next time he does this, send me the log file BEFORE restarting the service. And this he did:

19:22:04 (adskflex) OUT: “54600ACD_2008_0F” jwong@us-ny-384
19:31:35 (lmgrd) SHUTDOWN request from sgonzalez at node us-ny-576
19:31:35 (lmgrd) lmgrd will now shut down all the vendor daemons
19:31:35 (lmgrd) Shutting down adskflex pid=2768 because of signal 15
19:31:35 (adskflex) Shutdown requested from SYSTEM@us-license1 IP=
19:31:35 (lmgrd) Shut down FLEXnet adskflex license server system on machine us-license1
19:31:35 (lmgrd) EXITING DUE TO SIGNAL 15
19:31:35 (adskflex) daemon shutdown requested – shutting down
19:31:35 (adskflex) IN: “64300ACD_F” fchen@us-ny-375  (SHUTDOWN)

Blame sgonzalez sitting on machine us-ny-576 since he trigged the shutdown request! Make sure that he doesn’t have any LMTOOLS instances that’s running since that can trigger the shutdown request. For the client, we went to his machine and found that he had a rogue service running, and, as expected, it was LMTOOLS he installed for another piece of software.

Ahhhhh, debug log – is there anything you can’t do?



2 thoughts on “LMTOOLS – adskflex SHUTDOWN request

  1. Pedro Röseler July 15, 2011 / 10:04 am


    Thanks for sharing this information. We have exactly the same problem in our company…
    When you say “Make sure that he doesn’t have any LMTOOLS instances that’s running since that can trigger the shutdown request”, do you mean that the client machine that caused the forced shutdown might have a license server installed in its machine as well, and conflicts with official license server?
    Thanks in advance for your time!

    Pedro Röseler

    • thejame July 15, 2011 / 4:09 pm

      Hi Pedro,

      LMTOOLS is ‘aware’ of other instances running on the network. If there is an instance running, there’s a big chance that that instance will request to shut the other LMTOOLS down. Best thing to do is go to that IP address and remove the rogue LMTOOLS / FlexLM instance. Of course, this is different than running multiple FlexLM services, which IS possible. Hope that helps!


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s