SCCM 2012 R2 Log files for Linux and Unix Machines - Troubleshooting

SCCM 2012 R2 Log files for Linux and Unix Machines - Troubleshooting

Client for Linux and UNIX

For System Center 2012 Configuration Manager SP1 and later:

The Configuration Manager client for Linux and UNIX records information in the following log files.

Tip
Beginning with client for Linux and UNIX from cumulative update 1, you can use CMTrace to view the log files for the client for Linux and UNIX.

Note
When you use the initial release of the client for Linux and UNIX and reference the documentation in this section, replace the following references for each file or process: Replace omiserver.bin with nwserver.bin Replace omi with nanowbem

Log name	Details
scxcm.log	This is the log file for the core service of the Configuration Manager client for Linux and UNIX (ccmexec.bin). This log file contains information about the installation and ongoing operations of ccmexec.bin. By default, this log file is created in the following location: /var/opt/microsoft/scxcm.log To change the location of the log file, edit /opt/microsoft/configmgr/etc/scxcm.conf and change the PATH field. You do not need to restart the client computer or service for the change to take effect. You can set the log level to one of four different settings: ERROR: Indicates problems that require attention. WARNING: Indicates possible problems for the client operations. INFO: More detailed logging that indicates the status of various events on the client. TRACE: Verbose logging that is typically used to diagnose problems. To change the log level, edit /opt/microsoft/configmgr/etc/scxcm.conf and change each instance of the tag MODULE to the desired log level.
scxcmprovider.log	This is the log file for the CIM service of the Configuration Manager client for Linux and UNIX (omiserver.bin). This log file contains information about the ongoing operations of nwserver.bin. By default, this log is created in the following location: /var/opt/microsoft/configmgr/scxcmprovider.log To change the location of the log file, edit /opt/microsoft/omi/etc/scxcmprovider.conf and change the PATH field. You do not need to restart the client computer or service for the change to take effect. You can set the log level to one of three different settings: ERROR: Indicates problems that require attention. WARNING: Indicates possible problems for the client operations. INFO: More detailed logging that indicates the status of various events on the client. To change the log level, edit /opt/microsoft/omi/etc/scxcmprovider.conf and change each instance of the tag MODULE to the desired log level.

Under normal operating conditions the ERROR log level should be used. The ERROR level of logging creates the smallest log file. As the log level is increased from ERROR to WARNING to INFO to TRACE, each step results in a larger log file as more data is written to the log file.

Manage Log Files for the Client for Linux and UNIX Client

The client for Linux and UNIX does not limit the maximum size of the client log files, nor does the client automatically copy the contents of its .LOGfiles to another file such as a .LO_ file. If you want to control the maximum size of log files, implement a process to manage the log files independent from the Configuration Manager client for Linux and UNIX.

For example, you can use the standard Linux and UNIX command logrotate to manage the size and rotation of the clients log files. The Configuration Manager client for Linux and UNIX provides an interface that enables logrotate to signal the client as to when the log rotation completes, allowing the client to resume logging to the log file.

For information about logrotate, see the documentation for the Linux and UNIX distributions that you use.