By default, the Engine database supports a maximum of 40 000 simultaneous binaries. When this limit is reached, the Engine sends a system alert to the administrator account. No new binaries are incorporated into the Engine until any of the existing binaries is removed from the system.
The Engine automatically removes a binary from its database when the maximum inactivity period of the binary has elapsed and there is no event related to the binary in the database. By default, the maximum inactivity period of a binary is one month (30 days to be precise).
The Engine does not keep track of any information related to a non-recorded binary, such as executions or connections. Therefore, it is important for the administrator to keep the total number of binaries under control. If necessary, an administrator can increase the maximum number of binaries in an Engine and modify their maximum inactivity period. Beware that modifying the default values may have an impact on the performance of the whole system.
Modifying the limits on binaries
To modify the maximum number of binaries and their maximum inactivity period:
Log in to the CLI of the appliance hosting the Engine.
Edit the configuration file of the Engine:
sudo vi /var/nexthink/engine/01/etc/nxengine.xml
Inside the <limit> tag, add the following lines to increase the maximum number of binaries to 60 000 and decrease the maximum inactivity period of binaries to 20 days, for instance:
To save the file and exit, type in:
Restart the Engine:
sudo systemctl restart nxengine@1
Note that the maximum number of binaries has a hard limit of 100 000 binaries and that the maximum inactivity period of binaries is expressed in seconds:
20 days * 24 hours/day * 60 min/hour * 60 s/min = 1 728 000 s
The operations described in this article should only be performed by a Nexthink Engineer or a Nexthink Certified Partner.
If you need help or assistance, please contact your Nexthink Certified Partner.