>> Deploying with verbosity=0 solved my problem. >> Workaround is probably a better term than solved. ;-)
>> Something is happening in that self.log( call at line 112 that make it crash on Heroku. Unsure what it is and unsure the issue is on Django side. >> Providing the code (and reasonable context from surrounding statements) around line 112 would be a big help if you want to troubleshoot further. Logging settings would be helpful as well. >> At least this resolves my problem and there is some reference if someone else encounter this issue on Heroku too... >> Do you encounter this issue on your local dev machine, or are you publishing/developing directly on Heroku? Is it possible that you are hitting some sort of upper limit in your Heroku instance such as memory usage, logging rate, or file creation rate? Perhaps you are bursting past the standard resource allocations and the system is denying requested resources to your Django process (since you mentioned thousands of lines in your output)? Does Heroku have any sort of OS level logging for the container where your instance is running? That may provide some clues as to why your script seems to be failing at random points in the file creation process. -James -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CA%2Be%2BciXxv%2BGMKb%3DgWXevi7-dTVngWeexSsqKsT3Nf9LOMi%3DXtA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
