I'm deploying my Python app on GAE using the command line interface, which has always worked without problems. Since yesterday, one of the modules is getting stuck on "Scanning 500 files" and in the end throws following error:
Another transaction by user jong.vincent is already in progress for app: s~replimeapp, version: uno. That user can undo the transaction with "appcfg rollback".
However when I rollback updates for this app, the error is still thrown on the next deployment. No clue what I can do to resolve this. There is another module which refers to the same files, which has no problem deploying. No clue what I can do to get rid of this. Help please!
Changed the name of the module and then it worked. Very strange, but at least the problem is solved.
Related
I'm trying to deploy the latest changes to my django app, and I keep getting 502 errors. When I look at the logs, I only have this error in the Django logs: Error: %s <type 'exceptions.NameError'>. There's nothing in the Nginx error logs, and the access logs only show the 502 error. It runs fine in development, and it uses the same pip packages as development. How do I debug this?
Edit: This is actually an updated deployment. I had deployed it before without an issue, but something in my latest changes causes it to fail. I just need to know what that change was, but I can't find anything in the logs that would explain it.
I'm using Nginx, Django 1.8, Passenger, and Python 3.4. The server's running Ubuntu 14.04.
Sorry for the vague question, but I don't even know why this is happening.
Edit 2: It looks like there's actually something in the Nginx error log now. It's still vague, but at least it says something now. For the record, it's UnboundLocalError: local variable 'results' referenced before assignment in passenger_wsgi.py. I'm still clueless about why that's popping up now, but at least it's something to work with. Never mind. It's there, but that's just a result of the actual error, not the cause of it. However, the reason I asked this question is because I couldn't find anything in the logs, and now I've actually found something. So, for those of you looking for error logs:
Check your Nginx config files (nginx.conf, config files in sites-available) for the line error_log and check that.
If you're using Passenger and Django, check your passenger_wsgi.py to see if you've included logging. If so, check where it outputs.
It looks like my issue is out of the scope of this question, but I'd still like to leave it up in case anyone else has trouble finding log files.
I've been successfully able to run syncdb's on my django project for the past weeks, but something must have happened and I'm not sure what.
I always get this error:
No module named google.appengine.ext.django.backends.rdbms.base
I'm not sure why it's just kind of started. Shortly after getting this error, I tried updating my project on app engine and was prompted to download a new app engine launcher SDK, which I have done, but this error still exists. Not sure if maybe something is wrong with my PYTHONPATH?
From your description, this sounds like it could possibly be an issue, not intended behaviour. It sounds crazy, but perhaps something changed with the default Django installation. I suggest you attach a basic reproducing app to a new issue thread in the Public Issue Tracker
You may need to authorize your IP address. If that doesn't work, try using the standard MySQL driver instead of the Google App Engine one as described in our docs.
I am currently experiencing an issue in my GAE app with sending requests to non-default modules. Every request throws an error in the logs saying:
Request attempted to contact a stopped backend.
When I try to access the module directly through the browser, I get:
The requested URL / was not found on this server.
I attempted to stop and start the "backend" modules a few times to no avail. I also tried changing the default version for the module to a previous working version, but the requests from my front-end are still hitting the "new", non-default version. When I try to access a previous version of the module through the browser, it does work however.
One final symptom: I am able to upload my non-default modules fine, but cannot upload my default front-end module. The process continually says "Checking if deployment succeeded...Will check again in 60 seconds.", even after rolling back the update.
I Googled the error from the logs and found almost literally nothing. Anyone have any idea what's going on here, or how to fix it?
Fixed by shutting down all instances (on all modules/versions just to be safe).
I just moved from Heroku to PythonAnyWhere.com and im trying to get my python app work over there.
So i am trying to access the url but i get an error message. When i check the error logs i see this:
https://www.dropbox.com/s/fl16xbatsxbru36/Screen%20Shot%202015-03-27%20at%2023.25.54.png?dl=0
Since i am new to PythonAnyWhere i am having a REALLY hard time trying to understand if this is a code error from my python code (which i doubt since the same code works on Heroku). So does anyone know what problem could be here?
I'm using Openshift with Django/Python 3. As of yesterday, I've been unable to update my server. When I push a change, the push is successful. Using SCP to view the files on the server, the updated files are present. Using rhc git-pull downloads the correct files as well. However, the templates are the only thing that actually get changed on the app by the push. No changes to python files cause an effect on the app.
When I try to use 'rhc tail', I get the following error:
OSError: [Errno 98] Address already in use
Searching this error leads me to believe there are multiple server processes running for my app. I'm not sure how to run suggested diagnostics, as I don't control the server. Any ideas? Restarting the app does not fix it. Running rhc stop appears to successfully stop the app, yet my website works unhindered. (I've never tried stopping before, but assume it's supposed to kill the website.)
I found this post this afternoon by somebody having the same problem. It looks like Openshift changed some things on us. I didn't get the memo :(.
Read here:
Openshift March Blog post
#MSDOS, it is similar to your answer but I wanted to post the generic answer that is probably affecting most people.
For me, I just had to rename app.py (my old wsgi entry point) to wsgi.py and everything worked as it should. :) Now I have to figure what they changed to the cron jobs :(
Solved by executing 'rhc app force-stop', then 'rhc app start'. I don't know what caused the problem, but force-stopping it killed the website, and it worked with the new code after starting it again.
I think I solved the problem.
I was using an old django repository, based on https://github.com/openshift/openshift-community-cartridge-python-3.3/blob/master/template/app.py (the link is dead, I mentioned here just for information).
In these old community cartridges, there was a app.py file that started CherryPy or httpd, but now the official django repository doesn't have app.py anymore. (check https://github.com/openshift/django-example)
The app.py doesn't exist anymore because httpd service was added automatically. That's why we were having OSError: [Errno 98] Address already in use.
Removing the app.py from my repository solved the problem.
I was receiving error 500 because my Django application was having errors, not my Python cartridge. That's why I wasn't understanding what was happening. I did a find . -name *.log* in my cartridge and read all logs.
Now my app is working. Good luck!