Thank you Jeff! Tried vacuum_indexes again and it worked! Now I can handle this myself.
Following is the error message when I've tried vacuum_indexes first time. I hope this may help you... ---- akisute $ appcfg.py --force vacuum_indexes . Fetching index definitions diff. Deleting selected index definitions. 2009-05-02 12:48:33,476 WARNING appcfg.py:670 An index was not deleted. Most likely this is because it no longer exists. kind: Article properties: - name: is_duplicated - direction: desc name: date_update ---- Thanks again! Masashi Ono On 5月27日, 午前3:25, "Jeff S (Google)" <j...@google.com> wrote: > Hi it looks like the stuck index has been moved into the error state. > You should now be able to vacuum this index. When you mention that the > vacuum index failed, what was the error message? > > Thank you, > > Jeff > > On May 24, 5:54 am,akisute<akisutes...@gmail.com> wrote: > > > Hi, > > I've got a problem while building a new index for my applicaiton. > > index.yaml is correctly uploaded but its status is stacked in > > "Building" for a month. Something must be wrong. > > I've tried vaccuming the index by appcfg.py but failed... I need some > > help. My application ID is "nikkeiphone". > > Thanks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
