How can I change the stdlog cutover size on a secondary server?

Document ID : KB000050791
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

You can change the stdlog cutover size on both the primary and secondary Service Desk servers. The procedure to do depends on the server type. To make a persistent change to the stdlog cutover size on the secondary server, pdm_configure must be run after making the relevant changes to the NX.env_nt.tpl file.

Solution:

When you make a change to the stdlog cutover size on a primary server, the change is not propagated to the secondary servers. The secondary servers must each be changed individually. As well, for the changes to take effect and remain in place on a secondary server, pdm_configure must be run; on the primary server, this is not necessary.

To change the stdlog cutover size on a secondary server so that it persists after a shutdown and restart of Service Desk services, follow these steps:

  1. Edit the file named NX.env_nt.tpl that exists in the $NX_ROOT directory.

  2. Add or change the setting for @NX_LOGFILE_LIMIT in this file to the desired number of bytes. For example, to set the value to 10,000,000 bytes, use this statement:

    @NX_LOGFILE_LIMIT=10000000

  3. Make the same change to the NX.env file that exists in the same directory.

  4. Run pdm_configure.

    Note that Service Desk shuts down and restarts when pdm_configure is run. This step #4 is not necessary when changing the cutover size for the primary server.

Alternatively, to make an immediate temporary change to the stdlog cutover size on either primary or secondary server, use the pdm_logfile command in a Command Prompt window. For example, to change the cutover size from 3,000,000 bytes to 10,000,000 bytes, issue:

   pdm_logfile -a 10000000

To confirm the stdlog cutover size, issue the following command at a command line prompt:

   pdm_logfile -L