16

I browsed MSE front page a minute ago, and was greeted with the following error message:

It was not possible to perform this tag search at this time due to an unexpected error.

Screenshot:

I did not search for any tags...

Can the message please be changed to something more meaningful?

|improve this question
  • 5
    You do realize you broke the tag engine and with that summoned @MarcGravell on a saturday ... bad things will happen to you ... – rene Apr 29 '17 at 15:52
  • 1
    shouldiblamecaching.com – DavidPostill Apr 29 '17 at 16:45
  • 1
    Me too, on a per-site meta. – Monica Cellio♦ Apr 30 '17 at 22:35
  • 2
    I've been getting this a fair bit since yesterday... on a bunch of sites, main and meta – Cai May 1 '17 at 10:22
  • 1
    Got this recently on ruSO. I'm going to translate it, but afraid of lost it due to text changing if your request will be accepted :) – αλεχολυτ May 1 '17 at 10:36
  • @DavidPostill caching? I don't think so. I've been noticing the same thing for about 3-4 days now, then it comes back to being ok after a minute or so. This being for any tags on StackOverflow.com Edit: matter of fact, I just saw it again a minute or so ago. – Funk Forty Niner May 2 '17 at 0:13
  • 3
    @ShadowWizard: Why is this a feature request? Seems to be more of a bug, as per another post I saw while Googling this error: Random errors on various sites when viewing main page – Funk Forty Niner May 2 '17 at 0:19
  • This is happening fairly frequently for the past few days for me as well but in my case it is actually a tag search. When i go to questions/tagged/php i receive this notice at least 2 times a day. When i reload it works fine – Hanky Panky May 2 '17 at 5:20
  • 1
    @Fred-ii- David was using a meta meme, didn't mean it seriously. As for feature request, it's because I ask to change the message to be more meaningful, not to fix the bug causing it, which might indeed deserve a separate bug report if happening frequently. (For me it happened just once so far, but from comments here looks like it's more frequent) – ShaWiz May 2 '17 at 8:30
  • 1
    @ShadowWizard Hehe, got it. I posted a related on question on Stack's meta also. Others are experiencing it as well. – Funk Forty Niner May 2 '17 at 9:54
  • 3
    From the software's perspective, a search over all tags is still a tag search :) but yes, we should improve that message - from the user's perspective, it really wasn't a "tag search"; as for what happened: apparently the tag engine got unhappy; we've restarted the nodes, and it is on my list to look at further – Marc Gravell♦ May 2 '17 at 15:37
  • @MarcGravell I take it that your comment "as for what happened: apparently the tag engine got unhappy; we've restarted the nodes" is relevant to this Stack meta question I posted earlier..., yes? Plus, a few comments I left in the comments thread. – Funk Forty Niner May 2 '17 at 17:27
9

The short summary of this one is "because internet"; it turns out some annoying folks were doing annoying things specifically to be annoying, and a side-effect was disproportionate performance impact to a particular sub-system (the "tag engine"). I sincerely doubt that it was accidental or simply "oops my innocent crawler had an impact on your site? I simply didn't know...", based on the pattern of behaviour and the particular hoops they jumped through to hide their tracks. Anyway, as far as annoying bots go: that's what we call "a day with a 'y' in"; it was low-key enough not to set off any too urgent alarm bells, but it made it onto our radar, as has now been squished.

|improve this answer
  • Thanks, what about the message itself? Will you change it in case such thing will happen again? – ShaWiz May 2 '17 at 19:08
  • 5
    @ShadowWizard yes, I'll try to look at that ASAP, but frankly I hope that you just don't see that message... – Marc Gravell♦ May 2 '17 at 19:09

You must log in to answer this question.

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