This is probably just a side-effect of login servers being taxed with the rush of folks logging in again. I experienced the error this morning after logging out in the inn -- it was resolved in about 30 min. Chill out folks!