InsaneJournal Announcements

We're Back

InsaneJournal Announcements

We're Back

Previous Entry Add to Memories Tell a Friend Next Entry
After the longest outage in InsaneJournal history we are back 100%. No data was lost. I will post a larger update later explaining what happened. For now I simply apologize for the issues.

In the future if you want to keep up with what is going on during outages such as this check out the InsaneJournal twitter at http://www.twitter.com/insanejournal

Edit: The random missing page errors should be gone now. Sorry about that

Edit: AOL is currently blocking InsaneJournal mail. We are working with AOL to have this matter resolved asap

Edit: It appears that all notifications and emails are working normally again.
  • Try doing a hard refresh of your friend's page. Hold down your shift key and hit f5. The site had to change it's IP address, so I imagine it's just your cache trying to load the pages from the previous address.
    • haha, jinx?
    • Yes, I know--that's the only way I can get to this page, which was definitely not restoring from cache. That's not working for my flist, though, or I'd not have asked. As I say, not annoyed, and willing to wait while it sorts itself; just trying to get a sense of at what point to identify a problem, rather than A) complain when it's not time yet or B) wait indefinitely.

      *wonders whether hitting post will work this time*
      • I've found that I've had to hit shift and f5 sometimes half a dozen times before a page loads for me. Whereas other pages load fine. I found that my f-list was hard to load too, but now after having accessed it a few times through the incessant shift+f5, it seems to load properly now. Go figure.
        • There was one of the webservers in the load balanced pool that had the important part of the code commented out (I was trying to get an error message up but abandoned it after I realized that I didn't have time) and I forgot to uncomment it before I brought the site back online.
      • I foudn the problem and fixed it. ONe of the webservers wasn't configured right (was trying to get an error page up but never had the time to finish doing it)
        • Excellent. It is loading better, and again, you rock.
Powered by InsaneJournal