Follow

Init.cfg Parameters

QUESTION

What is Init.cfg used for and what are valid parameters?

 

ANSWER

The init.cfg file is used by KNM for settings that are needed before the database with the configuration is loaded. It controls which port KNM starts the web server on and in which mode KNM starts in (Standard, Distributed server or Distributed gateway).  The init.cfg file is located in the KNM root directory. 

========================

WEBSERVER_PORT = 8080 - Web server port number, this is the port number the web server will listen on for incoming connections from a browser. Can be changed while KNM is running: Yes

WEBSERVER_LANGUAGE = ENG - The language used in the web interface, currently only English (ENG) is available. Can be changed while KNM is running: No

WEBSERVER_BIND=x.x.x.x - If the KNM host machine have more than one network card KNM will bind to the first found card. To change this behavior the WEBSERVER_BIND= parameter can specify the address of the card KNM should bind to. Can be changed while KNM is running: Yes, if WEBSERVER_PORT also is changed, otherwise no.

WEBSERVER_CERT=name_of_cert - The web server can use SSL to encrypt information, this parameter specifies the certificate name, default blank. Use the SSL configuration utility to select and configure SSL options. Can be changed while KNM is running: Yes, if WEBSERVER_PORT also is changed, otherwise no.

WEBSERVER_SSL=0 - Enables web server SSL mode, default disabled (0), enabled (1). Can be changed while KNM is running: Yes, if WEBSERVER_PORT also is changed, otherwise no.

SSH2_TIMEOUT=25000 - SSH client timeout time in milliseconds, default value 25000 (25 seconds).Can be changed while KNM is running: Yes

SSH2_TRACELEVEL=0 - Trace level can be used to debug the ssh2 connection, default set to (0), valid range 0 to 4 (max output). Can be changed while KNM is running: Yes

OBJECT_IP_CACHE=1 - INM resolves all object host names into IP addresses, this feature can be turned of if there is problems with the local DNS , default enabled (1) , optionally disabled (0). Can be changed while KNM is running: Yes

DELAY_TEST_START=0 - This parameter can be used to delay the start of agent tests when INM is starting up, values in seconds, default 0. It can be useful for reducing machine boot time stress by delaying the start of INM agent tests. Can be changed while KNM is running: No

OPERATOR_SESSION_TIMEOUT=20 - To set the operator session timeout value, in minutes. If no timeout is wanted, set value to -1. Can be changed while KNM is running: Yes

SNMP_TIMEOUT=10000 - To set the timeout used by all SNMP functions (monitors, actions etc), in milliseconds, (default 10 seconds). Can be changed while KNM is running: Yes

ENABLE_CRASHFILE=true - If KNM should hang in a deadlocked state a crash function can be enabled in the init.cfg file. When enabled KNM will crash and produce a crash dump when a file called “crash.now” is created in the KNM root directory. When crashing KNM will produce a crash dump that can be used to analyze why the deadlock occurred by a KNM developer. Can be changed while KNM is running: Yes

LOG_LEVEL=2 - The log level can be controlled by this init.cfg paramter. If log level is set to 2 (default 1) KNM will start logging detailed information to a debug_log.txt file in the \logs directory. Can be useful when debugging mail and SMS sending behavior for example. The logging will continue until the paramter is removed from init.cfg. Can be changed while KNM is running: Yes

HOSTNAME_OVERRIDE=myhost.domain.local - When sending notifications to operators a link to the monitor/object is included in the notification e-mail. The link starts with the host name of the KNM host machine. This paramter can be used to override that name. Can be changed while KNM is running: Yes

DISTTEST_MODE=server - This parameter tells KNM to start the distributed subsystem in either “server” or “gateway” mode. This parameter is dependent on the DISTTEST_ENABLE parameter. Can be changed while KNM is running: No

DISTTEST_ENABLE=1 - This parameter tells KNM to start the distributed subsystem. This parameter is dependent on the DISTTEST_MODE parameter. The parameter can be set to 1 to enable or 0 to disable. Can be changed while KNM is running: No

WMI_PKT_PRIVACY=1 - This parameter tells KNM to use Packet Privacy as the authentication level for WMI queries. The parameter can be set to 1 to enable or 0 to disable (Default authentication level is used if set to 0). Can be changed while KNM is running: No

===========================

APPLIES TO

Kaseya Network Monitor, KNM 4+

Was this article helpful?
2 out of 2 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.