Re: inspectdb traceback

12:41:31 >>> Django version 1.6.11.7, using settings 'aixregistry_nxt.settings' >>> Starting development server at http://0.0.0.0:8000/ >>> Quit the server with CONTROL-C. >>> >>> >>> >>> >>> root@lpgaixmgmtlx0

Re: inspectdb traceback

ixregistry_nxt.settings' > Starting development server at http://0.0.0.0:8000/ > Quit the server with CONTROL-C. > > > > > root@lpgaixmgmtlx01:/root/django/aixregistry_nxt>./manage.py inspectdb > Traceback (most recent call last): > File "./manage.py

Re: inspectdb traceback

ettings 'aixregistry_nxt.settings' >> Starting development server at http://0.0.0.0:8000/ >> Quit the server with CONTROL-C. >> >> >> >> >> root@lpgaixmgmtlx01:/root/django/aixregistry_nxt>./manage.py inspectdb >> Traceback (most recent call l

inspectdb traceback

01, 2019 - 12:41:31 Django version 1.6.11.7, using settings 'aixregistry_nxt.settings' Starting development server at http://0.0.0.0:8000/ Quit the server with CONTROL-C. root@lpgaixmgmtlx01:/root/django/aixregistry_nxt>./manage.py inspectdb Traceback (most recent call last): F

inspectdb Traceback occurring immediately after interruption

run inspectdb I attempted to interrupt it with ^C but that failed so I sent a SIGTERM. Now, when I try to run python manage.py inspectdb I immediately get a Traceback: $ python manage.py inspectdb Traceback (most recent call last): File "manage.py", line 11, in ? execute_manager(s