Wesley's Tool-Box

Number of visitors coming from search engines indicate how much information of current interest exist on the website.

Looking back about three years, the search visitors peaked around the end of 2011 and went into a steady decline. Excluding the long-running web comic "The Toon-Box", the site had a new blog post every few months since the current framework went up in 2005 until a product review was posted in August 2011 and stopped altogether. It seems that, with the lack of any new stuff, the visitors naturally dwindled.

By the way, "The Toon-Box" series went into hiatus in July 2009 before returning in December 2013, but it didn't have any tags or indexes, so it was largely invisible to the search engines. To fix this problem, tags were introduced upon its return. I'm planning to add tags to the old comics as time allows.

But the truly interesting thing was the 2-month server downtime between February and March of 2013 caused by the iMac failure. Because the site went away for so long, the search engines probably de-indexed the pages, leading to a significantly reduced number of search visitors for several months following the restoration.

The visitor numbers would once again pick up in November 2013. This was shortly after I posted several pages of detailed review on iPhone 5S a month before. Now the daily number of search visitors is back to the old level again. I guess the search engines finally realized that the site is back in business.

The website went through a bit of overhaul. I've implemented a working tagging plug-in, so that the posts can now be organized by tags. The tag cloud on the lower right side of the website shows popular ones. Currently, posts from 2012 onwards are tagged, a total of 167 out of 1382 (12.1%).

Also, some Twitter plug-ins were put in, as well. The sidebar features a simplified Twitter feed from my @namuori timeline, while each blog posts now feature a "Tweet This" button that you can click to... tweet the article on your twitter timeline.

I've reported about the server losing connection after a bit of idling time yesterday, and the culprit was the power management settings. Surprisingly, my Mac mini was set to go into power saving mode just ten minutes after idling. I'm not sure what kept it up before, but it certainly isn't kept awake now. So I set the setting to never go fall asleep. Now the connection doesn't drop.

I thought this was the end of troubles, but it turns out that the server now takes a long time to respond after several minutes of idling. Once it responds, subsequent pages load just fine. I haven't found out why this was the case, but I know it's not a DNS lookup issue because there's no delay while there is network activity on the Mac.

So I devised a way to work around this issue by automatically causing a small network activity every minute. After opening Terminal:

crontab -e

[Press "i"]

00-59 * * * * /sbin/ping -c 1 -n google.com > /dev/null/

[Press "Esc" button]
[Press "!wq"]

And that's it. Once this is done, the system starts doing a ping once every minute silently. So far, it's working nicely and the website loads fine regardless of idling time.

There have been some network issues in the last few days. The major culprit turned out to be the 100Mbps Ethernet hub I've been using for more than five years (NEXT-8305SH). It doesn't "switch" the network connection over the ports properly anymore.

That has now been replaced with a ipTIME H5005 Gigabit Ethernet hub. I don't think the internet connection is that fast yet, but it's better to futureproof things. However, I've been noticing that the connection to the server is lost after some idling time after the new hub has been put into place. I'm not sure what's causing this and am trying to find out now.

I've been wary of installing new OS upgrades on the server because it can easily mess up the custom configuration I set up. In fact, that was primarily the reason why my old iMac that ran my websites (including this one) until early this year ran Snow Leopard (OS X 10.6) for 3 and a half years until it broke down. I passed upgrading to Lion (10.7) or Mountain Lion (10.8 ) all that time. I ultimately moved to Mountain Lion only because the new Mac mini that replaced the iMac required it.

This time was different. I had simplified the server configuration and kept track of the modifications. Basically, it was down to a couple of configuration files for built-in Apache server, and a separate MySQL installation. Downloading Mavericks (10.9) from the Mac App Store was what took most of the time. It was released as a free upgrade from anything that ran Snow Leopard and up, so there was a huge demand. Once the download was complete, I ran the installer, and it took about half an hour to complete.

I noticed that the websites were broken after the installation, as expected. However, checking the changes revealed that I only needed to fix the main Apache server configuration file. A couple of minutes of fiddling with the file later, the websites came back working properly. This was easily the fastest and the most trouble-free transition to the new major OS X version ever.

As a bonus, Apple had decided to make iWork upgrades to the just-released latest version for free, regardless of whether it was bought on DVD or on Mac App Store. My old copy of iWork '09 installed from the disc got properly upgraded, and the apps now show up in purchases list. Free OS and office suite upgrade, and smooth server transition. Apple has spoiled me.