So, I’m boppin’ along on my Ruby on Rails website, just screwin’ around with a few migrations, trying to decide how I want things to work. Stuff looks good, so I go to check in. But, in the meantime, my partner on the site as done an update, so I pull down the newest stuff. I then go re-run my migrations and tests (just to be sure), and get an error:
ERROR 1130 (00000): Host 'd-48-91-542-192.hsd1.mn.comcast.net' is not allowed to connect to this MySQL server
“Odd,” I say to myself, “Why can’t I connect to my localhost database? And how is it figuring out my external IP address?” And that’s when it dawns on me.
I was firing at production.
Good times.
A quick check confirms my suspicion: the last update screwed up some configuration, which set my environment to “production”.
If it weren’t for my hyper-paranoid configuration of MySQL, this would have been Very Bad Times.
Just in case being our own coding horror wasn’t bad enough, we are apparently our own SysAdmin horrors, too.
Related posts: