23

Going to anyone's profile on MSE, SO or Super User (didn't try others) results in an error page.

Screenshot of the problem

16
  • 2
    Reproduced on Physics, Astronomy, and Worldbuilding, as well as their meta sites.
    – HDE 226868
    May 2 '17 at 16:42
  • 1
    Every site from what I can work out
    – CalvT
    May 2 '17 at 16:45
  • 1
    Also, the mobile app is down (both Android and iOS)
    – CalvT
    May 2 '17 at 16:45
  • 1
    Reproduced on, like, fifteen of the sites I've got an account on (I don't remember which, but they were picked roughly randomly)
    – Nic
    May 2 '17 at 16:46
  • I just got this on RPG on one user, but not on the next one. However, trying it again just now with the same two users to see if there's a correlation with the different behaviour, I'm getting it with both (and all the rest, too), so I can probably blame the brief differences on caching. May 2 '17 at 16:46
  • This is occurring to me on Raspberry Pi StackExchange, on the main site and the meta site. May 2 '17 at 16:47
  • 1
    It's fixed now. May 2 '17 at 16:49
  • 1
    Seems to be fixed now.
    – J F
    May 2 '17 at 16:49
  • 3
    Voting to close as "no repro" since the pages are back now
    – Ferrybig
    May 2 '17 at 16:50
  • @Ferrybig: Let's wait to see how long they work for. It could be unstable. May 2 '17 at 16:51
  • 8
    We broke it, we're fixing it, someone will post an answer soon.
    – Haney StaffMod
    May 2 '17 at 17:00
  • @Haney: lol, good, and thanks (in that order) #commaspliceignored May 2 '17 at 17:02
  • 3
    @Ferrybig: No sense closing as no repro if it was fixed, only if it was nullified by unrelated events. May 2 '17 at 19:45
  • 2
    Agree with @Nathan, the no-repro is over used here way too much. It's meant for OLD bugs that were never fixed, and can't be reproduced any more hence can't be fixed any more. May 3 '17 at 8:34
  • 1
    @closevoters why close it? If this is closed, couldn’t we close every solved bug report as no reproduce? Nov 29 '19 at 6:30
18

Thanks for bringing this up. We made a change to our SQL server configuration that caused our logins to fail, which meant the data driving our sites was inaccessible (thus the errors). We've fixed that error and things should now be working properly. Sorry for the inconvenience!

A quote from Greg Bray, Site Reliability Engineer:

The ny-sql01 server was recently replaced, and we just tried adding it to the read only routing list using a new feature in opserver. We thought that feature failed, but it seems to have worked and uncovered a missing login/permissions issue (connections were failing to connect). The fix was to remove the new server from the read only routing list until we can figure out why the connections were failing.

2
  • 1
    Thanks for the update. May 2 '17 at 17:15
  • 1
    @BoundaryImposition but of course! :)
    – Haney StaffMod
    May 2 '17 at 17:16
-6

Yes, the Stack Exchange API started having issues around 16:40 UTC (4:40pm). Reported issues include:

  • Inability to load user profiles
  • Pages not loading in the iOS/Android apps

Features that still work include:

  • Posting questions/answers from the desktop/mobile sites
  • Global inbox notifications
  • Push notifications on iOS devices

Edit: Issues seem to have been temporary. As of 16:51 UTC (4:51pm), the site appears to be functioning normally.

2
  • 1
    Do you know how to fix it?
    – wizzwizz4
    May 2 '17 at 16:47
  • 1
    can't you just reproduce the SO Code? Class a{public a(){a anA = new a();}} ? May 2 '17 at 16:48

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .