FlexNet Update FAQ
PGI release 2019 version 19.1 and newer for x86-based platforms contain updated (v188.8.131.52) FlexNet Publisher license management software. PGI for OpenPOWER does not use FlexNet and is not affected by this update.
IMPORTANT: Users with PGI 2018 (18.x) or older need to update their license daemons for x86-based platforms to support 19.1 or newer. The new license daemons are backward-compatible with older PGI releases.
- As a PGI user or license administrator, what do I need to do?
- Where can I get new daemons and utilities?
- How do I determine which local versions of lmgrd, pgroupd, lmutil or lmborrow I'm using?
- How do I determine which versions of lmgrd and pgroupd are running on my network license server?
- Can I run new pgroupd with older daemons from other vendors?
- Can I run new pgroupd with older lmgrd versions?
As a PGI user or license administrator, what do I need to do?
We recommend you shutdown any currently running license services (daemons) and replace (see below) the FlexNet daemons and utilities with version 184.108.40.206 or newer. After installing the updated utilities, restart your license service by entering lmgrd.rc start. (Windows and OS X users, please refer your respective sections in the PGI Installation Guide for information on stopping and restarting your license services.) Once the license service is restarted, any client using the license service should benefit from the update. You can verify which version is running by following the steps outlined below.
Where can I get new daemons and utilities?
Updated FlexNet utilities are included in all PGI 19.1 or newer download packages. After downloading and installing, you should have access to the new license utilities in the bin directory (e.g. $PGI/linux86-64/flexlm). Alternatively, you can download a separate package containing only the license daemons and utilities.
Stop your license services, then copy the daemon package contents into the bin directory and restart your services.
How do I determine which local versions of lmgrd, pgroupd, lmutil or lmborrow I'm using?
In a shell with your PGI environment properly configured, enter the name of the daemon or utility with the ‘-v’ option, which should produce output similar to the following:
$ lmgrd –v lmgrd v220.127.116.11 build 242433 x64_lsb - Copyright (c) 1988-2018 Flexera Software LLC. All Rights Reserved. $ pgroupd -v 13:28:48 (pgroupd) FLEXnet Licensing version v18.104.22.168 build 242433 x64_lsb $ lmutil -v Copyright (c) 1989-2018 Flexera. All Rights Reserved. lmutil v22.214.171.124 build 242433 x64_lsb $ lmborrow -v lmborrow - Copyright (c) 1989-2018 Flexera. All Rights Reserved. lmborrow v126.96.36.199 build 242433 x64_lsb
How do I determine which versions of lmgrd and pgroupd are running on my network license server?
License administrators logged-in to the network license server should use the instructions above for determining local versions of the daemons and utilities. Users on a client system, with LM_LICENSE_FILE or PGROUPD_LICENSE_FILE pointing to your license server, can use the lmutil lmstat command which should produce output similar to below. You can also specify the license server with the ‘-c’ option.
$ lmutil lmstat [-c <port>@<license-server-hostname>.<domain>] lmutil - Copyright (c) 1989-2018 Flexera. All Rights Reserved. Flexible License Manager status on Mon 1/14/2019 14:22 License server status: <port>@<license-server-hostname>.<domain> License file(s) on license.pgi.net: /usr/local/flexlm/license.dat: <license-server-hostname>.<domain>: license server UP (MASTER) v11.16.2 Vendor daemon status (on <license-server-hostname>.<domain>): pgroupd: UP v11.16.2
Can I run new pgroupd with older daemons from other vendors?
Yes. They should work as before.
Can I run new pgroupd with older lmgrd versions?
It should work, but we recommend you update both lmgrd and pgroupd to make sure any security issues are fully addressed.