On 10/18/2017 01:41 PM, Abhilash Raj wrote:
Hi,
$ docker-compose rm -f mailman-web $ docker-compose up -d mailman-web
This will basically create a new container for Mailman-web, but, since the state of mailman-web is stored completely in database (database container), I am not sure how to reset *just* mailman-web without dropping mailman-core related tables too (they share the same database but have their own separate tables). The above command will get you a fresh copy of code running.
You can potentially get the list of tables and drop them, or maybe Diango has some way to reset it's state from Django shell (python manage.py <http://manage.py> shell, from inside mailman-web will get you shell). I may have to look it up.
Also, just by looking at the traceback, I am not sure about the exact error. I may have to debug more to arrive at a better conclusion, which I won't able to do until after this weekend.
after a full remove of the DB - I still get this error. I left some of the directories intact but for the most part it's a fresh new install that gets the same error where previous didn't give us as much trouble. Something else must be messed up. logs show very little detail other than originally posted exception. I'll try to dig up some more info...
-- Sr System and DevOps Engineer SoM IRT