Last week I spent a lot of time trying to upgrade the BIOS on a Dell Poweredge 650 server which ended up being a pain not only because the server is so old but because of various other issues I ran into along the way. This weekend I thought I was going to be in for the same issues when I wanted to upgrade the BIOS on a Dell Poweredge 2650 but thankfully I was incorrect. After initially attempting to upgrade using the same floppy disk method I used on the PE650 I decided to try the Redhat executable provided by Dell and ran into an error which is noted below along with what package was installed via the Yum Package Manager that resolved the error.
I recently upgraded crark on a CentOS Linux server from an earlier version to Crark version 3.3a. Initially it looked as if everything worked without problems and the speeds were improved slightly over the previous version of crark I had installed. After the initial testing though I noticed an issue when attempting to run crark from a directory besides the one I had unpacked all of the contents in and received some errors. Below is output showing the crark errors along with what was done to resolve the issue.
Last week I tried a bunch of different methods to try and upgrade a Dell PE650 BIOS. I finally settled on using a floppy disk to upgrade the BIOS however I initially ran into some issues with various floppy drives and floppy disks. One of the issues was an error message I received when attempting to access the floppy disk located within a floppy drive I had just installed on a Windows XP computer. Below I describe the error and how I was able to get past this specific error.
Earlier a client with a fairly complex network setup had a power outage in one of their data centers in Dallas, TX. The power outage caused three servers and a firewall to lose power causing all sorts of other issues on the servers themselves. One of the primary issues was getting the PostgreSQL cluster back in 100% operational.
While troubleshooting another problem this evening I noticed a bunch of avahi-daemon errors in the messages log on a CentOS Linux development server. The error hasn’t caused any issues that I am aware of and may be a simple case of a new warning message or another server on the network sending rogue DNS packets to the CentOS server in question. Below is information displaying the error in the messages log and what steps I took to resolve the problem.