|« The 2013 Chuck Yerkes Award goes to...||Its been another 4 months, time for a new eyeglass prescription »|
So, the announcement of FreeBSD 9.2 came out on Monday [September 30th], which I missed because I was focused on my UNMC thing. But, once it appeared, I knew that I was going to want to upgrade to it sooner than later.
From its highlights, the main items that caught my attention were:
But, I did start this upgrade on October 4th....where for an unknown reason, I launched the
freebsd-update process on cbox, the busier of the two headless servers. I suspect I went with doing the upgrade on my headless servers, because they are entirely running on SSD and would likely see the benefit of lz4 compression. And, perhaps I did cbox, because it was the system that could most gain from lz4.
It took a couple iterations through
freebsd-update, before I got an upgrade scenario that could proceed. And, it took a long time given the high load that is cbox.
That is cbox is an Atom D2700 (2.13GHz, dual core) processor. And, cacti (especially with the inefficient, processor/memory intensive percona monitoring scripts -- might help if only scrpt server support worked, and wasn't just a left over from what it was based on.) being the main source of load. That is usually in the 11.xx area, except during certain other events (like, since 3.5, when
cf-agent fires...cbox is set to run at a lower frequency than my other systems.) or when the majority of logs get rotated and bzip'd. And, there's also some impact when zen connects to
rsyncd each day for
backuppc. But, these spikes weren't that significant. Though the high load would cause
cf-agent runs to take orders of magnitude longer than other systems, including its 'twin' dbox.
Also ran into a problem (again?) where a lot of the differences that
freebsd-update needed resolved were differences in revision tags....some as silly as '9.2' vs '9.1', others had new time stamps or usernames, but seldom any changes to the contents of the file. Which I then discovered a problem from having some of these files under
cfengine would revert these files back to having '9.1' revision strings, which confused the
freebsd-update. I ended up updating all the files in
cfengine to have the 9.2 versioning, though I thought about just removing/replacing it with something else entirely, though wasn't sure the impact that would have on current/future
Though it did seem to cause problem with the other two upgrades, where it would say that some of these files were now removed and asked if I wanted to remove these. Which doesn't make sense, since it didn't say that with the first upgrade. It was probably just angry that these files already claimed to be from FreeBSD 9.2.
It also didn't like that I use
sendmail, therefore my sendmail configs are specific to my configuration, or that I use
printercap is the one auto-generated by cups, etc.
But, once it got to where it would let me run my first "
freebsd-update install". I ran it, rebooted, ran it again, rebooted, updated stuff (though it didn't complain as much, perhaps because some of the troublesome kernel mod ports had corrected the problem of installing into
/boot/kernel, or perhaps enough stayed the same between 9.1 and 9.2, that things didn't freak out like before. And, this includes the virtualbox kernel mod, when I did the upgrade on zen, and later mew. But, I re-installed these ports and lsof. I did a quick check of other services, and then upgraded the 'zroot' zpool to have feature flags (which now means it no longer has a version, apparently instead of jumping the numbers to distinguish from Sun/Oracle it has eliminated having version numbers (for beyond 28) and having flags for the features added since. Wonder if the flags capture all has changed since 28, since I thought there have been other improvements internal that aren't described by version numbers. Namely, I seem to recall that there have been improvements in recoverability....namely it had been suggested, when I was trying to recover a corrupt 'zroot' on
mew, to try finding a v5000 ZFS live CD. Which I don't think I ever found, and gave up anyways when I concluded the level of corruption was too great for any hope of recovery and that I needed to resort to a netbackup restore, before the last successful full get's expired. Though being that it was nearly 90 days old, the other two month fulls didn't exist due to system instability that eventually caused the corrupted zpool (eventually found to be a known bad revision of the Cougar Point chipset and a bad DIMM...things seem to finally be stable from using a SiI3132 SATA controller instead of the on board, and getting that bad DIMM replaced....was weird that it was a Dell Optiplex 990, purchased new over a year after the problem had been identified and a newer revision of the chipset was released. I did eventually convince Dell support to send me a new motherboard and replace the DIMM. The latter was good, since I had to use DIMMs from another Dell that had been upgraded, so I had less memory for a while. But, while at first I did use the onboard SATA again, eventually I started having problems that would result in losing a disk from the mirrored zpool, to eventually causing a reboot where they would both be present again [though gmirror would need manual intervention]....and moving back to the SiI3132 has finally gotten things stable again. Though the harddrives in mew are SATA-III, so it would've been desirable to have stayed on the SATA-III onboard ports, where it was these ports that were the main source of problems in the prior defective version. Perhaps the fact that the prior version had a heatsink and the new version didn't, wasn't because they didn't need it to try to compensate for the problems caused by over-driving the silicon for the SATA-III portion. But, an oversight with the newer revision motherboard. The problem did tend to occur in the early morning hours on the weekend, when not only is there a lot of daily disk activity, but there is also a lot of weekly disk activity, etc. Oh well.)
So, after upgrading the zpool, and reinstalling the boot block/code. I then rebooted the system again. I had already identified the zfs filesystems where I had 'compression=on', so had written a script to change all these to 'compression=lz4'. Which I now ran.
And, then I turned my attention to doing dbox.
Later when I looked back at cbox, I noticed that the load average was now around 9.xx....not sure what I did later that caused it drop further to 6.x-8.x....since I thought I had trimmed back on what was being monitored, particularly items using the percona monitoring scripts. Some day I'll get around to redoing box and orac as something else (either FreeBSD or newer Ubuntu.) perhaps when I get back to working on extending my cfengine system to cover all my current ubuntu systems.
I suppose its also possible that some port update along the way has improved things on cbox.
I also noticed that the CPU utilization has dropped....
Don't recall there being any big gotchas with dbox, though I have found now that named doesn't work after a reboot (which has become a major problem since the UPS its on is in need of new batteries...) Doing an '
rndc reload' will get it going again. Need to do some research on why this is happening now. Might affect cbox, but it has been rebooted since the upgrade. Also there might be a difference between graceful reboots and not.
So, I then continued to do zen, which also wasn't as bad as the upgrade from 9.0 to 9.1 was. Though somewhere along the way I noticed that my mouse was disconnecting and reconnecting, and it was getting worse and worse. And, was also affecting my keyboard.
But, first was how to work in an upgrade of mew, my FreeBSD workstation at work.
Eventually, I decided that I would risk it and do the upgrade remotely from home. I kicked off the initial run of the upgrade, with intent to look at the results when I got home. Though I forgot about it until Sunday, where I had to do it again fresh. But, after I did the first reboot, it occurred to me that maybe doing it on October 27th (the day before my 45th birthday) wasn't necessarily the best idea. Given that there was a special operation scheduled for early Monday morning, which I intended to do by remoting into my FreeBSD workstation. Which if something went wrong...I might be in trouble.
So, I did a quick check to see that I could remote into my other desktop systems (Ubuntu and Mac OS X), should that be necessary. I was able to get to Ubuntu, but not the Mac. I probably shouldn't have upgarded to Mavericks....namely it has broken my firewall...and IceFloor hasn't been updated for Mavericks yet. At least the failure is that my exceptions are missing....
As it was, mew upgraded fine.
As with cbox, I did zpool upgrades on all the others and switched 'compression=on' to 'compression=lz4' everywhere. mew is the only system of 'mine' that doesn't have SSD, of course...its not completely 'mine', otherwise it woud
Pages: 1· 2
Latest Poopli Updaters -- http://lkc.me/poop
|<< <||> >>|
backuppc cpap freebsd orac linux «air purifier» appletv usb «powersource 400» «doctor who» ups «instant streaming» «watch instantly» eyeglasses progressive raid tardis tv «hd movie» cfengine3 «sans digital» virtualbox raid1 10.04lts replaytv voip tivo ebay «tivo hd» netflix lhaven «windows 7» zen «windows xp» woot b2evolution dvd «chicago tardis» dsl cox twitter boinc upgrade box quicken mdadm «amazon prime» amazon.com prescription ubuntu