Tag Archives: software update

Update tiles

Synology DSM 4.2-3211 Released

Update tilesSynology released an update to DSM 4.2 back on April 18th which I got around to installing this weekend. Overall it is a pretty minor update but only took about 10 minutes oer NAS to install From the release notes:

  1. Fixed an issue where users could not connect to the DiskStation via FTP over SSL.
  2. Fixed an issue which kept the DiskStation from connecting to SNMP (Simple Network Management Protocol) UPS devices.
  3. Fixed an issue where domain users could not obtain an emergency code for 2-step verification.
  4. Improved the compatibility of file sharing via SMB/CIFS with Mac computers.
  5. Improved the stability of generating Disk Usage Reports.
  6. Improved the stability of iSCSI LUN.
  7. Improved the compatibility when backing up data between different versions of DSM.
  8. Improved stability when syncing files between two DiskStations with Shared Folder Sync.
  9. Improved the stability when backing up data to another DiskStation with Time Backup.
  10. Other issue fixes and enhancements.

Items 4, 6 and 8 could potentially help me in these areas although I never really had any problems so far. I had some Mac sharing problems but they want away and I figured it was a network or transient issue. I do sometimes get errors with shared folder sync but when I’ve bothered to track them down they all be files changed or deleted during the sync, The next sync has always worked just fine.

Audio Station, Cloud Station , Photo Station and Video Station packages also received minor updates. My CloudStation clients were automatically updated once the package on the Synology NAS was upgraded, which was nice.

WordPress Logo

WordPress 3.2 Released

The upgrades keep right on coming for The OS Quest website. WordPress 3.2 was released today and I jump right in and updated this site. At this point there’s been so many changes I won’t know where to start if something stops working. The stated focus of this update was to streamline speed-up WordPress. Check out the previous link to see all the changes.Or view the Trac database to see all 402 closed tickets.

Some key changes are:

  • Dropped support for PHP 4. PHP 5.2.4 is now the minimum requirement.
  • Support for IE 6 was dropped (I hope no one regrets this change).
  • Dropped support for MySQL 4. MySQL 5.0.15 or greater is required.

I upgraded all my sites through SVN but was notified and prompted to upgrade through the dashboard. It was necessary to upgrade the database once the files were upgraded. The database upgrade prompt came at the first site access after the upgrade so be sure the visit the admin dashboard after upgrading. The SVN upgrade command is:

svn sw http://core.svn.wordpress.org/tags/3.2/ .

The above command assumes it’s executed from the WordPress installation directory.

Tile for Quick Bits Software Update

Yet Another Update: iOS4 for my iPod Touch

Tile for Quick Bits Software UpdateApple started releasing iOS4 today so I went ahead and updated my iPod Touch, which is the third gen 64GB model.

Since getting my iPad I use the Touch mostly as a music player so I haven’t really given the new OS a workout.

A “check for update” on my iPad doesn’t show iOS4 as available for it yet. Just as well. Since the iPad is more of a daily user for me I’ll hold off and wait for reports on the experiences of others.

Screenshot showing WHS Power Pack 3

Windows Home Server Power Pack 3

Screenshot showing WHS Power Pack 3Windows Home Server Power Pack 3 was released Tuesday and I’ve applied the upgrade. While I didn’t have any serious problems it didn’t go exactly as planned. Just problems enough to cause some momentary heart palpitations.

As with any upgrade I make sure my backups are all in order before continuing then I do a pre-upgrade reboot to make sure there’s no errant or corrupted programs in memory. After the reboot I let things settle down and it’s about an hour before I fire up the WHS console go into Settings => General and click the “Update” button to get the update. There were a couple updates that came down along with Power Pack 3. The installs went fine and when the installs finished I clicked the button to restart immediately. That’s when things went off the script. The restart never occurred.

So after waiting about 20 minutes just to make sure it wasn’t still applying the patch I reconnected through the console. No problems connecting and no messages in the logs about starting a reboot. So I restarted again using the WHS console. This time it restarted on it’s own. But it never responded to ping and never became accessible over the network (never = about 20 minutes). Hooking up a monitor and keyboard showed a “service failed to start message” that I could clear with the mouse, but the keyboard didn’t work and the logon screen didn’t accept mouse clicks.

So I held in the power button until the server turned off. This time when I powered it on the start-up was successful and the WHS was available online. Now the problem was the lack of the expected message telling me I needed to upgrade the connector on my Windows 7 PC. The connector seemed to work fine and the console started, but it hadn’t been upgraded. The file in the Home Server Connector Software directory (in the “Software” share) had been upgraded so I ran the install from there.  It uninstalled the current connector and installed the new version without a problem.

I also had to manually upgrade the connector on my other PCs as none gave the expected upgrade needed message. All the upgrades went fine once I manually started the installation.

Once everything seemed to be fine I did another reboot just to be sure it started OK and it did. I went back into software update and found there were two more updates (one for search, one for the remote console) which required yet another reboot which was successful.

In going through the logs I noticed that during the first group of patches (which is when PP3 was applied) KB917013 was removed. This was a Microsoft search related update. There’s really no way for me to know if the failure to restart, or the lock-up on the restart was due to WHS Power Pack 3 or one of the other patched. In any event, there have been several successful restarts since then without a problem.

The screen shot at the top of this article shows the version information for Power Pack 3 – 6.0.2423.0. For the connector, since I’m on Windows 7, I checked the version by going into Control Panel => Programs to check the version as shown in the screen shot below.

WHS Connector showing Power Pack 3 version

WHS Connector showing Power Pack 3 version

Windows Home Server Power Pack 3 brings the following new features:

  • Windows 7 Library Integration – When the connector is installed on a Windows 7 computer the WHS share folders can be accessed through the Windows 7 libraries. I’d already manually added these folders to the libraries so this wasn’t much of a change.
  • When WHS backup is enabled the Windows 7 action center will no longer display a warning that Windows Backup is not used. This warning could already be turned off so the update just makes it automatic.
  • Some minor Windows 7 compatibility updates such as displaying Windows 7 as the OS in the Computers & Backup tab. While I never had problems with Windows 7 waking from sleep to do the WHS backup some did and this should no longer be a problem. I also didn’t have any problems running the WHS console under Windows 7 but now it’s officially supported.
  • Windows Search 4 is included and includes the standard line that it’s bigger, better and faster. EFS encrypted files are now supported.
  • Better media center integration and support. While I store my video library on the server and watch videos from it, I’m not a media center user although it does seem like something I should look into.

So, all-in-all, despite the speed bumps the Windows Home Server Power Pack 3 upgrade went fine. None of the new features are earth-shattering so I’ll see over time whether the better Windows 7 integration and improved search are noticeable in my everyday work. The complete release documentation is available from Microsoft.

WordPress Updates & Converting to SVN

WordPress 2.8 came out awhile ago and there was immediate talk of WordPress 2.8.1 to fix some issues. So I was in no rush to do any update despite liking to stay up to date. WordPress 2.8.1 was released so I decided to bring all my sites up to WordPress 2.8.1 and to update the theme or convert to svn as appropriate. I had tested using svn to maintain WordPress awhile back but this site and a couple had yet to be converted. It was time to convert them now that there’s a WordPress upgrade.

The steps I followed were pretty straight-forward and allowed me to update all my sites quickly with minimal outages.

  1. Validate my previous night’s backup of the databases and file system.
  2. Update plugins to make sure they work with WordPress 2.8.1
  3. Create a new directory called newsite.
  4. Use the subversion command
    svn co http://core.svn.wordpress.org/tags/2.8.1 .
    to install the latest WordPress into this subdirectory.
  5. Here’s where I departed from the WordPress.org instructions for converting a “traditional” WordPress install to svn. Instead of looking for custom files and copying them and plugins individually I used the following copy command with my old website directory as the current directory:
    cp –p –r –i –u . ../newsite
    –p says permissions should be copied
    –r will copy subdirectories (recursive)
    –i is interactive and will prompt for any file overwrites
    –u says to update only only newer or missing files will be copied. The –u should prevent overwriting any files installed via svn and the –i switch should prompt me before any are overwritten in case I’m wrong. I use the dot ‘.’ to indicate the current directory in order to get hidden files too. If I was to use ‘*’ the hidden files wouldn’t be copied. This made sure I didn’t miss any files while not overwriting any WordPress 2.8.1 files.
  6. After the copy I issued a svn update (svn up) just to make sure nothing was overwritten and nothing was.
  7. I then updated the theme files in the newsite directory if I needed to update the theme for the site.
  8. I added the following directive to my wp-config.php file (in newsite) to allow plugin updates without having to edit file.php. This is new with WordPress 2.8. See my article on enabling automatic plugin updates for more information.
    define('FS_METHOD', 'direct');
  9. When it came time to update the live site I enabled the maintenance mode plugin and issued the following two commands. The first backs up the sites directory structure and the second moves the newsite directory to the location of the live site. (My live site is in the public directory)
    mv public public-old
    mv newsite public
  10. Run the WordPress upgrade (http://www.sitename.com/wp-admin/upgrade.php) to upgrade the database.
  11. At this point I’m done except for the testing and turn off the maintenance mode plugin. The actual site outage was only a couple of minutes during steps 9 and 10.

This made it easy to update my live sites along with test and sites in development without any problems and in record time.