Please note that the log files on your system may be different due to different product version numbers and differences in your license key name.

Base product installation and upgrade logs:

/usr/local/linmin/LinMinBareMetalPreInstall.exp.log

/usr/local/linmin/linmin-bmp-6.0.1-6.exp.log

/usr/local/linmin/lbmpUpgradePub.log

/usr/local/linmin/ocp-install.log

Optional module installation and upgrade logs:

/usr/local/linmin/linmin-wpm-6.0.1-8.exp.log

/usr/local/linmin/LinMin_WPM_installer.log

License key installation and upgrade log:

/usr/local/linmin/{YourCompanyName}_{license_key_details}_lbmp.exp.log

Provisioning Server Status and Error Log:

The script linmin-services.sh generates or updates log and error files in /usr/local/linmin/status/:

•current_status_check (contains results of the most recent execution of the script linmin-services.sh)

•prior_status_check (contains results of the second- most recent execution of the script linmin-services.sh)

•status_ERRORs.{scriptTimeStamp} [...] (file generated each time there is an error condition)

To review the latest results:

cat /usr/local/linmin/status/current_status_check

or:

cd /usr/local/linmin/status/
cat current_status_check

Automatic Provisioning Server Restart Log:

cd /usr/local/linmin/LBMPcronRestart.log

Provisioner PXE Server Log:

The server's log file can be tailed by executing the following command:

tail -f /var/log/opencountry/ocprovision/ocprovision-default-0.log

In this XML file, you will see a series of transactions per provisioning event.

Every time you start or restart LBMP, a new log file gets created, and the previous log files have their file names incremented by 1.  The same happens once you have exceeded the default file size.

Default file size and maximum number of saved logs can be modified by editing the file: /home/tftpboot/config/logging.properties.

Note: the best way to see the full list of provisioning and imaging events is by inspecting the PXE Event Log.

Linux (other than Debian) ISO Media preparation log:

/usr/local/linmin/loadlinux.log

Debian repository preparation log:

/usr/local/linmin/debian-setup.sh-exec.log

/usr/local/linmin/linmin-bmp-debian-setup.log

Windows Server 2008 and Windows 7 ISO media and answer file preparation log:

/home/tftpboot/bin/windows-create-install-instance.log

ESX ISO media and answer file preparation log:

/home/tftpboot/bin/esx-create-install-instance.log

Each time you provision Windows Server 2008 or Windows 7, a log file gets created in the directory where you created a Windows Install Instance. For example, if the Windows Install instance you created is called "w2k8_r2_x64_enteprise", the time-stamped log can be found at:

/home/tftpboot/pub/w2k8_r2_x64_enterprise/w2k8_r2_x64_enterprise_20100330_152239.log

The Application Programming Interface (API) log can be found at:

/usr/local/linmin/lbmp-API.log

The PXE Event Log can be found at:

/usr/local/linmin/linmin-bmp-pxe-event.log

The PXE Event Log contains the MAC addresses you have provisioned or imaged as well as a summary of the actions taken including the Provisioning Role or Role Template used.  Note that this file doesn’t get updated immediately upon a provisioning event, but rather after a minute or so. This is the recommended way of seeing all provisioning events (MAC address, time, action taken, etc.)

2009-01-22 11:52:56 MAC 00:11:09:62:9c:49 pxeboot request

2009-01-22 11:52:56 ... profile:/home/tftpboot/pxelinux.cfg/01-00-11-09-62-9c-49

2009-01-22 11:52:56 ... profile after boot:/home/tftpboot/pxelinux.cfg/01-00-11-09-62-9c-49-after-next-boot

2009-01-22 11:52:56 ... control after boot:/home/tftpboot/controlfiles/001109629c49.cfg-after-next-boot

2009-01-22 11:52:56 psql linminbmp -U postgres -c "select enable_provisioning_flag from profiles where mac_address = '00:11:09:62:9c:49'";

Provisioning Role Template: “Red Hat Enterprise Linux 5.2 x86_64 JBoss Server”

2009-01-22 11:52:56 ... sql select profiles enable_provisioning_flag: enable_provisioning_flag  : -------------------------- :  ignore : (1 row) :  :

To parse the PXE Event Log linmin-bmp-pxe-event.log to identify unique MAC addresses or to identify MAC addresses by event type (provisioning, imaging), execute the following command:

grep 'MAC ' linmin-bmp-pxe-event.log | cut -d' ' -f4 | sort | uniq | wc -l

* replace 'MAC ' with 'PXE control: \/home' for MAC Specific count (slashes matter)

* replace 'MAC ' with 'Independent' for MAC Independent count

* replace 'MAC ' with 'PXE imaging' for all imaging actions count

* replace 'MAC ' with 'Backup' for image backup count

* replace 'MAC ' with 'Restore' for image restore count

When a MAC-Specific Provisioning Role is set to "active" (e.g., Next Boot, Live Ubuntu or Always) or when an Imaging Role is set to either Backup or Restore, an IP address from the Bootp range gets automatically assigned to the Client's MAC address.

The DHCP log shows the history of Bootp range IP address assignments to specific Client MAC addresses used in MAC-Specific Provisioning and Imaging and can be found at:

/usr/local/linmin/dhcpPXEmanagement.log

The GUI Login log can be found at:

/usr/local/linmin/guiLogin.log

The Provisioner PXE Server's log file can be found by executing the following command:

tail -f /var/log/opencountry/ocprovision/ocprovision-default-0.log

In this XML file, you will see a series of transactions per provisioning event, including the MAC-address of the systems you have provisioned.

Every time you start or restart the Provisioner PXE Server, a new log file gets created, and the previous log files have their file names incremented by 1.  The same happens once you have exceeded the default file size.

Default file size and maximum number of saved logs can be modified by editing the file: /home/tftpboot/config/logging.properties