error

You are currently browsing articles tagged error.

At around 3am Sydney time, You­Tube went down:

Google’s mon­keys are still slav­ing away at it as I write this. And it looks like it’s just affect­ing Aus­tralia:

For future ref­er­ence, if you’ve got a box out­side Aus­tralia with ssh access, you can always quickly set up a proxy like so:

ssh -D 1337 username@example.com

This sets up a SOCKS proxy on loc­al­host (your own com­puter) at port 1337 (sub­sti­tute port num­ber to taste) — then simply point your browser at it. With this, I veri­fied that the You­Tube out­age at the very least didn’t affect the United States, by ssh-ing into nointrigue​.com, which is hos­ted in the US.

Related post from a while ago: Sil­ver­hawks: Get­ting around con­tent restric­tions. (Using -D with ssh is easi­er than the meth­od with Privoxy men­tioned in that post, though.)

Happy Aus­tralia Day.

Tags: , , ,

I thought the sky almost fell down just then when I went to my gallery2 install­a­tion (/​gallery) and saw that it had a data­base error. “Noooo!!! I’ll have to spend hours rein­stalling and upload­ing again!” The error in ques­tion was

An error has occurred while inter­act­ing with the data­base.

If you get this error, don’t pan­ic. For me, it turned out that one of the data­base tables was cor­rup­ted and needed repair­ing. Log in to phpMy­Ad­min or to the mysql con­sole and check wheth­er any of the tables are lis­ted as cor­rupt. In my case, it turned out to be g2_CacheMap.

I snooped around some for­ums, and in the threads that had responses (a lot of for­ums have ques­tions left unanswered unfor­tu­nately), it seems like the blame lies with your host hav­ing a bad mysql setup or bad hard drives that cor­rupt at ran­dom. Shame on you, Blue­host.

Tags: , , , ,

img_1803.jpg

A joke about hav­ing lots and lots of tiny let­ters after your name? Or just someone incom­pet­ent who expec­ted mod­ern print­ing tech­no­logy to magic­ally know what you’re try­ing to print?

Tags: , ,