Bomb Threat At The Intel Arizona Site

From azcentral.com, “Chandler police: Bomb threat made at Chandler Intel campus

Authorities are investigating a call received on Monday morning of a bomb threat at a building that is under construction at the Intel Corporation’s Ocotillo campus in Chandler.

The building was evacuated after the call was received at about 5:30 a.m. and that police and authorities at Intel are in the process of searching the building, Chandler police spokesman Seth Tyler said. The rest of the facility is still running, police said.

Tyler said authorities searching near the building “haven’t found anything” and that Intel has “been doing a lot of the search on their own.”

Update: Chandler police: No bomb found on Chandler Intel campus:

Authorities found no explosives after a bomb threat on Monday morning at a building under construction at the Intel Corporation’s Ocotillo Campus in Chandler.

The building was evacuated after a call was received at about 5:30 a.m. Police and authorities at Intel finished searching the building using bomb-sniffing canine units at about 2:30 p.m., Chandler police spokesman Seth Tyler said. The rest of the facility is still running, police said.

Tyler said authorities searching near the building did not find anything and that Intel had done a lot of the search on their own.

Construction workers working on the building were sent home around 10 a.m.

Where Is The Village At Rio Rancho?

The Village at Rio Rancho goes here someday
The Village at Rio Rancho goes here someday

According to a Albuquerque Business First Article “Unser corridor bursting with retail, office activity” the Village at Rio Rancho was support to start “This Summer”. Since the article was written in May 2012 that would make it last summer. Currently all we have is a lot of cleared desert that will turn into atmospheric dust come this spring. The City of Rio Rancho only mentions this special tax deal from 2009.

Meanwhile down the road in Albuquerque “Construction starts on new Westside ABQ plaza“.

Introducing Always Very Busy

Sometimes I go out and buy a lot of food to cook only to find the kitchen a mess and decide to go out and eat instead. This is how this blog has become. I have recently made some changes to clean up and focus the content, in the hopes of actually writing more.

The first thing I did was to delete about 30% of the content. I removed all posts about politics (there’s plenty of more qualified people writing about politics). I reduced the number of categories and re-categorized posts.

greginthedesert.net is supposed to be about Me, Greg, in the desert. So I have started a new blog called alwaysverybusy.net to write about tech and gadgets and other stuff that keeps me always very busy. I’m also considering another spin off site where I can focus on photography.

I’m still in the process of moving and removing posts. I still have the problem of Google not indexing this site so more work is to be done.

The Whitewater Baldy Complex Fire

IMG_0416

Image from Gila Forest on Flickr.

The Gila Fire is now the Whitewater Baldy Complex fire, named after the Whitewater and Baldy fires merged. It’s currently 15% contained and has burned 217,988 acres. It’s the largest fire in the US and the largest in New Mexico state history.

It was almost a year ago that I was posting about the Wallow fire in Arizona, which burned more than twice what the Whitewater Baldy Complex fire has burned. The Wallow fire produced a lot of smoked that end up in Albuquerque. So far Albuquerque has been spared most of the smoke from the Whitewater Baldy Complex fire.

Hard Water In The Southwest And Faucet Repair

Remodeling For Geeks points out the problems with faucets in the southwest. Although he is in Arizona, New Mexico has the same problem. The water is hard: It has a high level of dissolved minerals and everything that the water runs through eventually gets coated with the minerals (mostly calcium). The water has high levels of minerals because of the ground it comes from.

These minerals act like abrasives on seals and the moving parts of faucets, so they leak. They all leak. I don’t care what the ads or salesman tell you, sooner or later your faucets will leak. So when you are spending money on a faucet you should make sure that repair kits are available. Really. If the place you are buying it from does not have repair kits in the same section as the faucets, run away! Unlike a lot of products, faucet manufacturers have pretty explcit instructions for repair. Plus faucets are not like electric outlets where the only decisions are amperage and color. They are different and do not share parts.

Google Mowing With Goats

Google is mowing their large areas of vegetation with goats. This is a great idea, something I may investigate when I get the grass growing in the back yard.

At our Mountain View headquarters, we have some fields that we need to mow occasionally to clear weeds and brush to reduce fire hazard. This spring we decided to take a low-carbon approach: Instead of using noisy mowers that run on gasoline and pollute the air, we’ve rented some goats from California Grazing to do the job for us (we’re not “kidding”). A herder brings about 200 goats and they spend roughly a week with us at Google, eating the grass and fertilizing at the same time. The goats are herded with the help of Jen, a border collie. It costs us about the same as mowing, and goats are a lot cuter to watch than lawn mowers.

The Pain Of Forced Switching To A New Web Hosting Provider

In case you haven’t noticed, there’s been a few changes and other screwey things happening on this site. On 9 March 2009 I received a email from my then hosting provider MacHighway.

Unfortunately, we’ve needed to suspend your blog, greginthedesert.net. Your site is regularly using between 30 – 99% of the CPU on that server. It appears that your site is getting around 161k hits per month. The good news is that Technorati estimates that a blog getting 100k his a month is worth $75k/year. The bad news is that it’s far exceeds the fair use policy of our shared hosting environment. Your sites’ needs have outgrown what a shared hosting provider can offer.

Additionally, your site calls on a tremendous amount of resources with all of the dynamic information that the site needs to load in order just to display the front page. This is exacerbating the problem and should definitely be trimmed down.

I totally understand how this was a problem and I can see how I made it worse with some of the stuff I was using to generate my blog since I have been experimenting with plug-in’s and templates. I replied to the support ticket and said I had a number of ideas on how to reduce the CPU usage of my blog and that I wasn’t coming close to my bandwidth or disk usage quotas. They were having none of it and said move my blog elsewhere.

It also would have been nice if they could have given me some heads up about the excessive CPU usage. I guess they didn’t want me as their customer. It’s too bad since the few other issues I had with MacHighway were well taken care of.

I started to look for a non-shared hosting provider. Dedicated hosting is expensive, the cheapest I found was nearly $100 a month. Even though the MacHighway support guy suggested my blog should be worth $75,000, I make tens of dollars a year on advertising, not hundreds. There is no way I can afford dedicated hosting. Also, the 161,000 hits a month I get are only translating to about 9,000 real people a month. I also can only see where 58K hits a month are coming from including robots, image leachers, etc.

After a searching around for a few days including local services providers I ended up going with another shared hosting provider: Dream Host. In fact, there’s a number of things I like about them but that’s a blog post for another day.

MacHighway temporarily enabled my blog so I could export my data. I copied all the WordPress directories to my hard drive, exported the database and exported a WXR file. Just in case the database dump failed to import.

After getting my domain redirected to the new servers at DreamHost and WordPress installed, I attempted to import the database. The raw sql file is 230MB and compressed it’s 22MB, far more than the 7MB limit that the phpmyadmin allows. I had to become familiar with the command line to do the import. After contacting DreamHost support because a few things weren’t properly configured on my account I attempted to try the command line import sequence. The import failed on line two, where the sql file’s phpmyadmin version was 2.11.9.4 and DreamHost’s version is 2.11.9.3. I commented that line out and tried the import again, next fail was at line 7.

I contacted DreamHost support to see what they would say about the situation. They tried importing and found several lines which failed. The support person suggested that I continue to comment out lines which fail. I thought that was a bad idea since many of those line look like important parts of the database creation process and I didn’t know how long this editing-upload-fail-repeat process would continue.

Database import wasn’t going to work. I started working on importing the WXR file. My import file was 10.6 MB, bigger than than the 7MB limit imposed by wordpress for import files. I compressed it, which I read elsewhere could overcome the import size limitation. Even though it brought the file under 7MB, it could not get it to sucessfully import. I had two results with the importing of the WXR file, sometime the site would just hang sometime it would give me a 408 page.

I went through and removed the 14,000 plus but that didn’t change the results. I broke the WXR file into several small files and was able to have successful imports. I went through a process of having one half of the cut up file succeeded importing and the other half fail. It has become clear that there is some part at the beginning of the WXR that is corrupt or some other problem that is confusing the import process.

There are still abut 400 posts left to import, but the majority of the important ones are there and I will continue to go through the process of breaking up the remainder of the WXR file until I find the problem entry. Although I learned a lot about WordPress and phpmyadmin and SQL databases, I’m looking forward to getting this whole ordeal behind me and return to blogging.