Server Error ("Text Search") on Admin Console

[eshe muta]

We're seeing this:

 

"

Server Error
 
A server error has occurred.
 
Return to Applications screen »
 "

 

Whenever we click on Any index of "Text Search" on Admin Console.

 

100% reproducible.

 

Is this happening to other apps?

 

 

 

 

[Amy Unruh]

Eshe,

What is your app id? (You can email it to me directly if you like).

 

 

 

 

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/nhT0A0eCoT4J.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[dima]

I get this error too. Because of what this error?

On 29 май, 04:13, Amy Unruh <amyu+gro...@google.com> wrote:
> Eshe,
>
> What is your app id? (You can email it to me directly if you like).
>

[Amy Unruh]

While I can't tell for sure, I suspect you are seeing this issue:

http://code.google.com/p/googleappengine/issues/detail?id=7601

related to display of non-ascii content in the search panel of the admin console.  

You can track this issue to see when it is fixed, which should be by the next release (if not sooner).

This issue does not affect your ability to index or query non-ascii content using the search API -- it is only specific to the admin console.

[James Courtney]

I'm seeing this error now (22 months later).  I suspect the cause must be different but I can't browse or search any of our text indexes through admin console (app behavior seems unaffected).  In short, the symptoms seem identical to that posted initially for this thread.

[Vinny P]

On Tue, Apr 1, 2014 at 1:29 PM, James Courtney <james.c...@philanthropal.com> wrote:

I'm seeing this error now (22 months later).  I suspect the cause must be different but I can't browse or search any of our text indexes through admin console (app behavior seems unaffected).  In short, the symptoms seem identical to that posted initially for this thread.

Did this error appear just now, or has it been occurring for a long time?

I realize you said the app behavior seems unaffected, but can you try accessing random records (or most records, if possible) and see if the search operation encounters a snag?

 

 

-----------------

-Vinny P

Technology & Media Advisor

Chicago, IL

App Engine Code Samples: http://www.learntogoogleit.com

[JAMES COURTNEY]

Thanks for getting back to me Vinny.  This has been occurring for at least a couple of weeks and likely longer since I wan't trying to use this area of the admin console previously.  I also realized that I can browse my indexes in a limited way though paging forward a few times often causes the described error to appear.  Any attempt to search using even a one-word query string containing only the characters a-z fails with the described error though.

I've iterated all of our users and searched for each by first + last name and found that all but 3 query properly.  Of those three one is an internal user which we explicitly don't index and the other two simply have initials for their first and last names so a single letter for each which, I assume, the text search engine doesn't index.  No errors were received and all operations completed promptly.

BTW, I realized I probably should have created a post on stack overflow which I did here:

http://stackoverflow.com/questions/22797685/a-server-error-has-occurred-on-text-search-in-admin-console

Best,

Jamey

James Courtney

Co-Founder, CFO, Code Monkey, etc.

PhilanthroPal, Inc.

Office: (650) 300-1652

Mobile: (650) 740-2628

james.c...@philanthropal.com

Be Social. Be Mobile. Be Charitable!

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/hsM0Z3mrm3Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.

To post to this group, send email to google-a...@googlegroups.com.

Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.

[Vinny P]

On Thu, Apr 3, 2014 at 12:10 PM, JAMES COURTNEY <james.c...@philanthropal.com> wrote:

This has been occurring for at least a couple of weeks and likely longer since I wan't trying to use this area of the admin console previously.

The reason I asked how long the error has been taking place is to try and narrow down the list of suspect documents. Since the issue started at an unknown time, it's going to be harder to find the culprit, but hopefully not impossible.

On Thu, Apr 3, 2014 at 12:10 PM, JAMES COURTNEY <james.c...@philanthropal.com> wrote:

I also realized that I can browse my indexes in a limited way though paging forward a few times often causes the described error to appear.

Does the server error always happen on the same page; i.e. you page forward and the error consistently occurs at the nth page? Or does the error occur at seemingly-random pages? 

On Thu, Apr 3, 2014 at 12:10 PM, JAMES COURTNEY <james.c...@philanthropal.com> wrote:

Any attempt to search using even a one-word query string containing only the characters a-z fails with the described error though.

Can you try searching using subsets of the alphabet? For example, search once using the query string "abc", then if that works continue on with "def", "ghi", "jkl", etc? 

 

On Thu, Apr 3, 2014 at 12:10 PM, JAMES COURTNEY <james.c...@philanthropal.com> wrote:

BTW, I realized I probably should have created a post on stack overflow which I did here:

http://stackoverflow.com/questions/22797685/a-server-error-has-occurred-on-text-search-in-admin-console

 

It might also be a good idea to file an issue on the tracker: https://code.google.com/p/googleappengine/issues/entry?template=Production%20issue (use the template marked production).

[JAMES COURTNEY]

Hey Vinny,

So you believe there's one document which is hobbling the system?

So we have three text search indexes and included below is my browsing experience for each:

IDX_APP

- always fails simply when clicking the IDX_APP link from the "Text Search" admin console page

IDX_ORGANIZATION

- fails with the error when paginating results from 240-260.

IDX_USER

- fails with the error when paginating results 40-60.

I was able to iterate the entire alphabet in chunks of three as you suggested without error but also without results.  I believe the error is occurring upon attempt to display specific documents/results as you seem to suspect.

I've filed the production issue too.  Thanks for your continued help with this.

Best,

Jamey

James Courtney

Co-Founder, CFO, Code Monkey, etc.

PhilanthroPal, Inc.

Office: (650) 300-1652

Mobile: (650) 740-2628

james.c...@philanthropal.com

Be Social. Be Mobile. Be Charitable!

[Vinny P]

On Mon, Apr 7, 2014 at 12:59 PM, JAMES COURTNEY <james.c...@philanthropal.com> wrote:

So you believe there's one document which is hobbling the system?

Not necessarily one. Most likely there's an unknown number of documents that are improperly configured. And when I say improperly configured, I mean they could be corrupt, improperly replicated, an error with the underlying storage/machine, encoded with the wrong character set, the list goes on and on. 

The problem is there's just no way to know what the problem is without isolating the exact document(s) causing the issues. Fortunately you seem to have isolated a range of suspect documents that Google can now investigate (the page ranges you stated in your previous email). 

On Mon, Apr 7, 2014 at 12:59 PM, JAMES COURTNEY <james.c...@philanthropal.com> wrote:

IDX_ORGANIZATION

- fails with the error when paginating results from 240-260.

IDX_USER

- fails with the error when paginating results 40-60.

If you are in a rush to fix the problem, I would suggest trying to delete and then rebuild the documents listed within the above ranges. But to be honest, now that you've filed a production issue it's probably easier to just sit tight and see what Google's response to your issue is (they also read this forum, so most likely someone's looking into it already).  

[JAMES COURTNEY]

Many thanks Vinny.  It's frustrating because I can't see the data to see what might be iffy.  It isn't an emergency though so I'll give Google a few days to sort it out.

Best,

Jamey

James Courtney

Co-Founder, CFO, Code Monkey, etc.

PhilanthroPal, Inc.

Office: (650) 300-1652

Mobile: (650) 740-2628

james.c...@philanthropal.com

Be Social. Be Mobile. Be Charitable!