When installing the acidbase package on Ubuntu Linux there are numerous popups that require answers. Some of those variables are covered in this article however there is one that when searching debconf selections for it isn’t listed with acidbase so it can be harder to locate. Below I display the popup in question and describe how to setup a debconf variable to get around it.
Last night I upgraded the BIOS on my Dell Studio XPS 13 from A11 to A14. The BIOS upgrade appeared to work without issue however when the computer rebooted with the new BIOS version I received a boot error and then once I skipped the error I received a popup message within Windows 7 as well. The problem ended up being something really silly which is explained below but I wanted to note in case someone else ran into the same issue.
During the build of a Linux development server earlier I performed a “yum update” to update all of the packages after installing CentOS 5.4. I got busy with other tasks and left the server at work without checking to verify that the update had worked properly. Now after dinner I started to get back to work on the server by installing some new packages via yum and received a yum warning message which I describe in greater detail below along with how to resolve the warning.
I received the below error when attempting to run a setup.py script to finish installing a certain application. The application was being installed on a 64-bit CentOS Linux system and during the initial part of the install I had attempted to use 32-bit python which ended up causing a bunch of errors. After I believed that all of the errors were corrected I still received an i386 error message. Since I am not very familiar with Python setup scripts it took me a couple minutes to figure out what needed to be done.
We have various scripts on a server that process files that are uploaded to a specific directory so we needed a way to monitor these directories and verify that all files are being processed. Once they are processed on our server they are moved to different directory so the file count should never get over a certain amount of files. The below script assumes that you have NRPE installed on the server so you can reference the bash script locally. Follow the directions below with some monitor modifications and you can monitor directories for the number of files with Nagios very easily.