The below is part of the output when receiving an error attempting to install the Perl DBD::mysql module using the CPAN shell. I rarely use the Perl CPAN shell since most of the packages are available on CentOS, my typical Linux distribution choice for servers, using the yum package manager. In this case I was working on installing Monarch on a server at work to assist with Nagios file management. Monarch allows you to backup the entire Nagios configuration files with the click of a button. Monarch will also provide a visual view of any Nagios build errors, Nagios configuration files (including users, user groups, services, check commands, etc.,), and more. So when attempting to build the Perl DBD:mysql module via the CPAN shell I received some errors which I initially did not understand because they did not explain the specific issue however I eventually located the problem which ended up being easy to resolve. Below I describe the error in detail as well as information on how to resolve.
In the process of installing Monarch, which is a Nagios file manager, earlier I ran into a couple errors for modules I thought I had already installed. Then I realized the issue must be because during the process of installing modules Perl wanted to upgrade from 5.8 to 5.10 on CentOS. I went ahead and upgraded Perl however I left 5.8.8 intact since CentOS seems to rely on Perl 5.8.8 in many ways. Anyhow the full error I received is below as noted from the Apache error logs. You can easily resolve the below error by following the directions below.
I am working on getting Monarch installed on a server to manage Nagios file. Part of the setup includes installing a bunch of items using Perl’s CPAN. One of the packages I needed to install was called “XML::LibXML::Common” but it failed with an error. The error was overcome on CentOS by installing libxml2-devel using yum. Below are details regarding the error, the yum command to resolve the issue, and the end of a successful install of the initial package.
If you are new to WinDbg (The Windows Debugger) like I am then you might struggle with some of the initial configuration items. I would suggest you do your best to get through the initial configuration issues so you can troubleshoot your Crash Dump files to analyze the issues on your computer. So far I am really happy with Windows 7 Ultimate 64-Bit though I have had multiple BSOD’s (Blue Screens of Death) which are frustrating. I am now doing what I can to get down to the bottom of each of the crashes so I can do whatever it takes to minimize any crashes and continue using Windows 7. Follow the directions below to configure the path to Symbols needed by the Windows Debugger (WinDbg).