Go to main content

Administering Resource Management in Oracle® Solaris 11.4

Exit Print View

Updated: August 2018
 
 

poold Daemon Functionality That Can Be Configured

    You can configure these aspects of the poold daemon's behavior.

  • Monitoring interval

  • Logging level

  • Logging location

These options are specified in the pools configuration. You can also control the logging level from the command line by invoking the poold daemon.

poold Daemon Monitoring Interval

Use the property name system.poold.monitor-interval to specify a value in milliseconds.

poold Daemon Logging Information

    Three categories of information are provided through logging. These categories are identified in the following logs:

  • Configuration

  • Monitoring

  • Optimization

Use the property name system.poold.log-level to specify the logging parameter. If this property is not specified, the default logging level is NOTICE. The parameter levels are hierarchical. Setting a log level of DEBUG will cause the poold daemon to log all defined messages. The INFO level provides a useful balance of information for most administrators.

At the command line, you can use the poold command with the –l option and a parameter to specify the level of logging information generated.

    The following parameters to logging are available:

  • ALERT

  • CRIT

  • DEBUG

  • ERR

  • INFO

  • NOTICE

  • WARNING

The parameter levels map directly onto their syslog equivalents. See Logging Location for more information about using he syslog function.

For more information about how to configure poold daemon logging, see How to Set the poold Daemon Logging Level.

Configuration Information Logging

The following messages can be generated about libpool configuration:

ALERT

Problems accessing the libpool configuration, or some other fundamental, unanticipated failure of the libpool facility. Causes the daemon to exit and requires immediate administrative attention.

CRIT

Problems due to unanticipated failures. Causes the daemon to exit and requires immediate administrative attention.

DEBUG

Messages containing the detailed information that is needed when debugging configuration processing. This information is not generally used by administrators.

ERR

Problems with the user-specified parameters that control operation, such as unresolvable, conflicting utilization objectives for a resource set. Requires administrative intervention to correct the objectives. The poold daemon attempts to take remedial action by ignoring conflicting objectives, but some errors will cause the daemon to exit.

WARNING

Warnings related to the setting of configuration parameters that, while technically correct, might not be suitable for the given execution environment. An example is marking all CPU resources as pinned, which means that the poold daemon cannot move CPU resources between processor sets.

Monitoring Information Logging

The following types of monitoring messages can be generated:

CRIT

Problems due to unanticipated monitoring failures. Causes the daemon to exit and requires immediate administrative attention.

DEBUG

Messages containing the detailed information that is needed when debugging monitoring processing. This information is not generally used by administrators.

ERR

Problems due to unanticipated monitoring error. Could require administrative intervention to correct.

INFO

Messages about resource utilization statistics.

NOTICE

Messages about resource control region transitions.

Optimization Information Logging

The following message optimizations can be logged:

DEBUG

Messages containing the detailed information that is needed when debugging optimization processing. This information is not generally used by administrators.

INFO

Messages about alternate configurations considered could be displayed.

NOTICE

Messages about usable configurations or configurations that will not be implemented due to overriding decision histories could be displayed.

WARNING

Messages could be displayed regarding problems making optimal decisions. Examples could include resource sets that are too narrowly constrained by their minimum and maximum values or by the number of pinned components.

Messages could be displayed about problems performing an optimal reallocation due to unforeseen limitations. Examples could include removing the last processor from a processor set which contains a bound resource consumer.

Logging Location

The system.poold.log-location property is used to specify the location for poold logged output. You can specify a location of SYSLOG for poold output (see the syslog(3C) man page).

If this property is not specified, the default location for poold logged output is /var/log/pool/poold.

When the poold daemon is invoked from the command line, this property is not used. Log entries are written to stderr on the invoking terminal.

Log Management With the logadm Command

If the poold daemon is active, the logadm.conf file includes an entry to manage the default file /var/log/pool/poold. The entry is as follows:

/var/log/pool/poold -N -s 512k

For more information, see the logadm(8) and logadm.conf(5) man pages.