Monday, February 26, 2007

Pinoy Big Brother 2


Media_http2bpblogspot_kcaqj


Forget the housemates! Mariel Rodriguez makes this reality TV show "watchable". Half past midnight since the new season launched and the server is already borked! Good thing I got to grab this pic of Mariel before it went down (it seems to be failing intermittently...but what can you expect from an M$ OS anyway?)

Here's the error I see:

Could not load file or assembly 'BizModules.UltraPhotoGallery' or one of its dependencies. There is not enough space on the disk. (Exception from HRESULT: 0x80070070)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'BizModules.UltraPhotoGallery' or one of its dependencies. There is not enough space on the disk. (Exception from HRESULT: 0x80070070)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

An assembly load trace and a very long stack trace follows. To cap that is this:

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

Cheers!

Sunday, February 25, 2007

IP-hijacking and then some

Almost a month of downtime. The servers were fine, but our IP addresses were not. Somehow, a system bug from one of the hosting companies caused our plan to include 14 other IP addresses, and we only maintained 6 as far as I am concerned.

So the hosting company eventually understood what was happening and started asking the right questions. The bug is that the system allowed network administrators to assign to new clients, the IP addresses that have already been assigned to a current client.

We spent crazy hours figuring out what happened. Since the domains were not loading our sites, and instead were redirecting to some domains we don’t own (real bad sites btw), we checked if .htaccess was modified and tested if it was working at all. I also did double checks on virtual host configurations and they all looked clean.

I started thinking that it was a routing issue. We were not using the publicly routable IPs for the virtual hosts; instead, we used internal IPs as mapped to the firewall hardware. A lookup on the domain/s that we were being redirected to reported different IP addresses, which didn’t readily confirm my suspicions, but stressed the possibility of IP-hijacking.

It’s not supposed to be taken in the context of BGP (border gateway protocol), as this is beyond me. Instead, think of your assumption over IP addresses that we’re using, to serve your websites. Sounds clear? I hope it does. I got pretty lost myself and it isn’t after deep digging at the hosting company’s end that their errors became apparent.

So in the light of this realization, I’ve already moved the domains to some other hosting. Way too much work and way uncool.

Google Apps Certified Deployment Specialist

Back in November last year, the Apps Services Partner that I help with Google Apps Support told me that I was required to take the Google Ap...