I have a Java app deployed on app engine and I use appcfg.py of the
Python SDK to vacuum and update my indexes.
Yesterday I first ran vacuum_indexes and that completed successfully -
i.e. it en-queued tasks to delete my existing indexes.
The next step was probably a mistake on my part - I then ran
update_indexes even though my previous indexes weren't yet deleted.
Needless to say that my update_indexes call errored out. So much so
that now when I look at my app engine console, it shows the status of
all my indexes as "Error".
A day has passed an it still shows the status on my indexes as "Error".
Can someone help my out of my fix?!
Thanks,
Keyur
P.S.: I have posted this on the GAE forums as well but hoping SO users have faced and resolved this issue as well.
I followed what was suggested in the error logs and that worked for me:
Empty the index.yaml file (create a backup first)
Run vacuum_indexes again
Look at your app's admin console and don't go to the next step till all your indexes are deleted.
Specify the indexes you want to be created in index.yaml
Run update_indexes
Look at your app's admin console and it should show that your indexes are now building.
Enjoy the fruits of your labor :)
Cheers,
Keyur
Related
Ive try to send basic Android Build as tutorial says but Im getting this error. PS: I never would made any build before, and every day this message persists. (I`m using the Free account).
build-for-android-device:
[codeNameOne] You have a build in progress within the queue. Only one build may be active at a time
Someone may help me?
Looking at our support logs I think this was an issue that was resolved by a support engineer. The issue was related to an email account containing a + sign in the address specifically name+name#domain.com
Since our system uses emails to identify users this caused some issues and failed to show builds that went thru. So there was a build stuck in queue that never got built...
Restart your IDE, operation system.
You have queue of build right now.
first of all I am sorry on my English.
I have a problem in my Gwt application.
I build Gwt application and I work on application every day
Yesterday I want to still work on my application but is stopped worked and i do not know why and I not get errors
The application compiled and I get the Url to run on browser
I copy the Url to my Firefox browser and not happened nothing.
I put break point in my entry point class and I see the application not arrived to entry point and I do not know why.
I try to open new project to check maybe the problem in eclipse or in Gwt plug in but the new project worked excellent so I understand the problem in specific this project.
I need help
thank you everyone
Okay i have 3 possible suspicions:
You updated your Application, but for some reason some JavaScript stayed inside the Firefox cache. Solution: Go to options and "Clean cache" and always try to press CTRL+F5 instead of just reloading, this will clean the current website's cache saved in your Browser.
Your HDD is full(less likely). You said you work everyday on the app. The caching in dev-mode is very VERY bad(for me it once contained 300GB of cached data). there is a folder called <win_user>/AppData/Local/Temp - delete everything inside if you find a lot of "gwt-<something>" files and check the folder's size. There is nothing valuable inside it(if you didn't place anything inside :D)
P.S. Turns out it was a Firefox Memory-leak that has been fixed in GWT 2.6.0 :)
Your Eclipse messed up some random stuff. As always - Project > Clean...
Then right click on app and let gwt recomile your app(if you have an ant file that uses the gwt-compiler, execute that)
I can't really think of anything else...
The only thing that could be is that YOU changed something, but you said you didn't so...
Hopefully it works,
Laurenz
If I go into Google Webmaster Tools, and click Health->Crawl Errors, I noticed that our site has about 1,045 Not Found errors.
Each of these errors can be fixed manually by:
filtering through the list to find the specified error that has been
needs to be fixed, and clicking on it.
In the resulting dialog clicking the Fetch as Google link,
Clicking Fetch
And finally, clicking submit the index (provided there are enough fetches remaining to do so), and then marking it as fixed.
Since there are about 1,000 errors to fix, doing this manually seems a bit out of the question.
(Note: I didn't have anything to do with it but the site was migrated before the content causing the errors.)
I'm aware that it is possible to retrieve a list of site errors, but that's really only half the battle. I looked over the APIs and didn't really find a way to use the Webmaster Tools API to mark errors as fixed.
Marking errors as "fixed" is perfectly possible with this API call:
https://developers.google.com/webmaster-tools/search-console-api-original/v3/urlcrawlerrorssamples/markAsFixed
So you can easily automate this by e.g. …
fetching the crawl error sample (1000 max.)
checking the given URLs
marking working URLs as fixed via API
Keep in mind: Crawl error information is updated about once a day. So if there are more than 1000 errors and half of them get marked as fixed, new data that was not in the sample before will likely roll in after a day has passed.
I'm not sure what your question is, as I just successfully tested removing all errors (4 in my case) which was possible with just a few clicks. If the errors keep reappearing you might want to take a look at where the invalid URLs are linked from: if it's internal stuff, you should fix those links, and if it's external links you should either add redirects to the updated/moved pages, or ask the external web site(s) to update their links to your site.
To clarify: There are several problems I'm facing here, the most annoying of which is that my app engine logs appear very late in the admin console. I think that they may be related, which is why I'm grouping them together.
I was testing my app after uploading to Google App Engine about two hours ago, and I was tweaking the code and re-deploying. I use the Eclipse plugin and it says deployed successfully. I did not change the version number at first, and apparently all my changes were not being reflected on the server at all. I found out because my logs showed the old build number.
At this point in time, my logs were being updated real-time, and I could see logs from requests that took place seconds ago.
Anyway, I figured that I needed to change version numbers, so I did that and re-deployed, and made the new version default. After this my logs remained empty, even though I was testing my app continuously. And none of the logs of any of the versions showed the latest requests.
I checked my logs about half an hour back, and now it shows me the logs for the requests I was making then. Any requests I made at that point in time didn't show either - apparently I'll have to wait another hour for them to show.
Am I doing something wrong, or is there something about the App Engine mechanism I don't understand?
This sounds odd, I know. And I couldn't find anything about it on Google.
Problem 1: Described above.
Problem 2: Do I need to change version numbers anytime I make even a tiny change?
Problem 3: When I make changes to a servlet while testing on the local dev server, it takes approximately 3-4 minutes to reflect those changes when I test the app, even if I stop and restart the server. JSP changes reflect immediately.
I see the same behavior: On the initial deployment of an app, log messages seemed to appear real-time, but after a couple of days and lots of deployments, I see delays of up to 30 minutes. Known issue, apparently: http://code.google.com/p/googleappengine/issues/detail?id=3338.
Not required. After deployment, changed code without changes to the version number is immediately available on AppEngine.
Item 3 sounds like a browser caching issue. Does a forced reload (ctrl-shift-r on firefox) refresh your stale servlet pages?
I am using hibernate in my java dynamic project and since last week I am getting one exception called "No row with the given identifier exist[#entity(0)]. I found same problem asked earlier and I did same as suggested but problem persisted. I tried using "not-found=ignore" case as well but it doesn't work. Even the project is working fine # Production but here # development is quite disturbing. Please help me.
Maybe this can help explain it.
Just a suggestion: whenever I get an error message of any kind, I immediately cut & paste it into a Google search to see what comes back. It's highly unlikely that I'm the first person to encounter a problem.