500 Server Error

53 views
Skip to first unread message

Yaniv

unread,
May 27, 2009, 10:57:34 AM5/27/09
to codereview-discuss
I am new to Rietveld.
I just created an appengine rietveld server. When I tried "make
update" there was some problem, I got the following error:

Error 400: --- begin server output ---
Creating a composite index failed: This index:
entity_type: "Issue"
ancestor: false
Property {
name: "modified"
direction: 2
}

is not necessary, since single-property indices are built in. Please
remove it from your index file and upgrade to the latest version of
the SDK, if you haven't already.
--- end server output ---
Your app was updated, but there was an error updating your indexes.
Please retry later with appcfg.py update_indexes.


I deleted the index.yaml file and ran the server locally to create
this file automatically, then I tried "make upload" again and it
worked, but I keep getting "500 Http Server Error" when I try to open
an issue. Also, when I am signed-out I can see the servers front page
but when I am signed in I get "500 Http Server Error" on the front
page as well.

Any ideas?

Thanks,
Yaniv

Andi Albrecht

unread,
May 27, 2009, 2:07:34 PM5/27/09
to coderevie...@googlegroups.com
Looks like not all required entries in index.yaml were generated when
you've ran the dev server.

The traceback from the log viewer would be helpful to narrow down the
500 you see. I think it's about a missing index...

Try to upload again with the original index.yaml where the entry
mentioned in the 400 is removed.

Andi

2009/5/27, Yaniv <shu...@gmail.com>:

Andi Albrecht

unread,
May 28, 2009, 3:16:41 AM5/28/09
to codereview-discuss
Fixed in r419.

I was able to reproduce this issue and had a 500 after uploading on a
fresh instance with a modified index.yaml. But it was most likely
caused by an index that was not ready to serve at this point. After a
few minutes (in fact a cup of coffee) everything was fine.

Andi

On May 27, 8:07 pm, Andi Albrecht <albrecht.a...@googlemail.com>
wrote:

Yaniv Shuba

unread,
May 28, 2009, 3:28:55 AM5/28/09
to coderevie...@googlegroups.com
That works now (after the fix). Thanks.
Reply all
Reply to author
Forward
0 new messages