If you see high usage in your LicenseMonitor reports, we know what the situation is: you have duplicate handles in your database.
Immediate fix:
Please remove the duplicates manually with the commands like these:
% ftlm_check_db -deleteduplicates -start "20090901"
% ftlm_check_db -deleteduplicates -start "20090601"
% ftlm_check_db -deleteduplicates -start "20090301"
% ftlm_check_db -deleteduplicates -start "20090101"
Moving back in time, from September, June, march, and so on,
as far back as it makes sense.
If you use MySQL, please also use the option -keepindex.
Then regenerate the reports.
Long term fix:
If you install the latest LM patch (LM-Update-2) available from our web site,
this cleanup is automatically performed.
Explanation of duplicate checkouts:
We have been aware of the possibility of duplicate checkouts for quite some time and we have, first of all, looked for ways to eliminate them altogether. Now we have finally realized that duplicate checkouts will always inevitably occur, so we are now adopting a strategy of:
1. minimize occurrence of duplicates when loading the database
2. automatic cleanup anyway
The duplicates happen because of the way LicenseMonitor detects a checkin,
which is by the absence of a previously known checkout. This detection
is vulnerable to transient failures of lmstat. If lmstat, for any of a thousands of reasons, fails to deliver a complete answer, LicenseMonitor concludes that the checkouts have been checked in. At the next cycle, when lmstat succeeds, many of those checkouts reappear and they will be logged again later on.
Duplicates are easily identified because they have the same checkout time, user, host, feature, handle.