Jeremiah's blog

user warning: Table './drinking_drpl2/watchdog' is marked as crashed and last (automatic?) repair failed query: INSERT INTO watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (0, 'flickr', 'Could not connect to Flickr, Error: Forbidden', 'a:0:{}', 4, '', 'http://rothwerx.com/blog/2', 'http://rothwerx.com/blog/2', '195.154.162.218', 1503088996) in /home1/drinking/public_html/rothwerx/modules/dblog/dblog.module on line 146.

mdadm's rules of order

My GIS-using client recently had a power failure at their office, and their GIS fileserver failed to fully boot when it regained power. This system had a 5-disk RAID5, and according to /proc/mdstat, all the drives were marked as spare and the md was not active.

So I tried to reassemble, but it said it tried to assemble 3 drives and 1 spare, which was not enough to start the array. Naturally I had checked SMART to see if anything was reporting failed there, and nothing was. I know drive manufacturers can fudge their SMART results, but I still figure it's a pretty decent indicator.

Version Control for System Administrators

It's not uncommon for me to set up a local git repo for a project I'm working on. I understand the benefits of using version control for software projects. But for some reason, working a central VCS into my day-to-day workflow with multiple servers just eluded me.

I've had a http://projectlocker.com account, and I just signed up with http://beanstalkapp.com. My needs aren't great, I just want to keep the occasional script and/or configuration file in a central location. You know, the "cloud". You could create new repos for each parent directory you want to store in version control, but you're limited if you're just using free accounts on these VCS hosts.

I don't want to have to download the whole tree of configs and scripts every time I want something. But all the VCS tutorials would have you do just that, because that's what makes sense for a software project.

Secure Google searches from Chrome

Google has an SSL encrypted version of their search engine in beta, and it's nearly as speedy as the unencrypted standard search. Even for inane things like my Google searches, I'd rather it be secure, so I changed my default search in Google Chrome to use the https version.

On my Mac, I choose Preferences from the Chrome menu and in the Basics tab, click the Manage button next to Default Search. Click on the + button at the bottom of the window that opens, and you're ready. Name and Keyword can be anything; I used Google Secure for both.

Then for the URL, enter (all one line, of course):

https://www.google.com/search?{google:RLZ}{google:acceptedSuggestion}{google:originalQueryForSuggestion}sourceid=chrome&ie={inputEncoding}&q=%s

Click Ok, click Make Default, and you're done. Now when you type something in the URL/search bar, your search will be encrypted.