vsoch
commented
4 years ago The error is loud and clear, you don’t have a SECRET_KEY in your settings. Tell me exactly how you generated and where you put the SECRET_KEY?
Closed tejasdixit836 closed 4 years ago
vsoch
commented
4 years ago The error is loud and clear, you don’t have a SECRET_KEY in your settings. Tell me exactly how you generated and where you put the SECRET_KEY?
tejasdixit836
commented
4 years ago i have generated the SECRET KEY from the link u have provided. and placed it in secrets.py
SECRET_KEY="the key" ps: it is not commented out!!
On Fri, Nov 22, 2019 at 12:45 PM Vanessasaurus notifications@github.com wrote:
The error is loud and clear, you don’t have a SECRET_KEY in your settings. Tell me exactly how you generated and where you put the SECRET_KEY?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/singularityhub/sregistry/issues/252?email_source=notifications&email_token=AN27GCJZALVHMYOIBMLLRS3QU6BJ5A5CNFSM4JQLWRC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE4Y5XQ#issuecomment-557420254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN27GCKVD54F3MMVS2JAR5LQU6BJ5ANCNFSM4JQLWRCQ .
tejasdixit836
commented
4 years ago the same config is working perfectly in another server. i am sure i am missing something. bt i am unable to catch it
the secret.py looks like this
SECRET_KEY = 'hvll0%q8b5^(as)p9#yu%blahblah($3o_d'
import ldap from django_auth_ldap.config import LDAPSearch, PosixGroupType
AUTH_LDAP_SERVER_URI = "ldap://ldapseerver"
AUTH_LDAP_USER_SEARCH = LDAPSearch("ou=User Accounts,ou=User Directory,dc=linux,dc=org,dc=com", ldap.SCOPE_SUBTREE, "(sAMAccountName=%(user)s)")
AUTH_LDAP_GROUP_SEARCH = LDAPSearch("ou=General Groups,ou=Group Directory,dc=linux,dc=org,dc=com", ldap.SCOPE_SUBTREE, "(objectClass=group)" )
#
Please suggest
On Fri, Nov 22, 2019 at 2:06 PM tejas dixit tejasdixit836@gmail.com wrote:
i have generated the SECRET KEY from the link u have provided. and placed it in secrets.py
SECRET_KEY="the key" ps: it is not commented out!!
On Fri, Nov 22, 2019 at 12:45 PM Vanessasaurus notifications@github.com wrote:
The error is loud and clear, you don’t have a SECRET_KEY in your settings. Tell me exactly how you generated and where you put the SECRET_KEY?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/singularityhub/sregistry/issues/252?email_source=notifications&email_token=AN27GCJZALVHMYOIBMLLRS3QU6BJ5A5CNFSM4JQLWRC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE4Y5XQ#issuecomment-557420254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN27GCKVD54F3MMVS2JAR5LQU6BJ5ANCNFSM4JQLWRCQ .
vsoch
commented
4 years ago The file needs to be called secrets.py, not secret.py. You would also need to restart containers.
tejasdixit836
commented
4 years ago Sorry my bad its secrets.py Only.
I have mistyped it here. I double checked it now that you pointed out.
On Fri, Nov 22, 2019, 17:01 Vanessasaurus notifications@github.com wrote:
The file needs to be called secrets.py, not secret.py. You would also need to restart containers.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/singularityhub/sregistry/issues/252?email_source=notifications&email_token=AN27GCIIYUB5CTTHKCAM4SLQU67J5A5CNFSM4JQLWRC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE5L5ZA#issuecomment-557498084, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN27GCKYLAF6KRNLTGU3XI3QU67J5ANCNFSM4JQLWRCQ .
vsoch
commented
4 years ago And the other question I asked above - you restarted your containers after making the change?
docker-compose restart uwsgiYou just joined 11 hours ago - you joined explicitly to try out Singularity Registry server? That's... interesting...
tejasdixit836
commented
4 years ago I mean it was not secret.py it was secrets.py originally. I mistyped in email. i deleted the containers and started them fresh. I also erased docker docker-compose and installed fresh. But same error .!!
I am using redhat vm 7.7 version The other machine where I installed was using 7.6
No not newbie. I have never posted a question on social platform before.i had to register to post a question and this is my first question . Still naive to hpc administration as I am new to this job
On Fri, Nov 22, 2019, 21:02 Vanessasaurus notifications@github.com wrote:
And the other question I asked above - you restarted your containers after making the change?
docker-compose restart uwsgi
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/singularityhub/sregistry/issues/252?email_source=notifications&email_token=AN27GCPEOBGFG35OSMEU7H3QU73RRA5CNFSM4JQLWRC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE57TDY#issuecomment-557578639, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN27GCMHLNE37FEIL2FXLXDQU73RRANCNFSM4JQLWRCQ .
vsoch
commented
4 years ago You don't need to remove containers and start from scratch, you just need to restart the containers. Can you please confirm the secrets file is under:
shub/settings/secrets.pyand that you've restarted the containers as follows:
docker-compose restart uwsgiAnd if you shell into the container, you see secrets.py
docker exec -it <container_name> bash
ls shub/settingsAnd that if you start an interactive shell, if what you've set up is actually there, you should be able to start a shell and import it.
python manage.py shell
from shub.settings import SECRET_KEYBeyond that I don't think I can help you. The error message is very clear that the SECRET_KEY isn't defined, and that is where you should start debugging.
tejasdixit836
commented
4 years ago Thank you for quick response
Can you please confirm the secrets file is under:
shub/settings/secrets.py
yes . the file is in same location
and that you've restarted the containers as follows:
docker-compose restart uwsgi
yes.
docker exec -it
bash
ls shub/settings
And that if you start an interactive shell, if what you've set up is actually there, you should be able to start a shell and import it.
python manage.py shell
all ok till here
but,when i do from shub.settings import SECRET_KEY , i see this
ImportError Traceback (most recent call last)
vsoch
commented
4 years ago That suggests you don't have it. You could try further with ipython
from shub.settings.secrets import [TAB]The tab completion will show what is there.
Other than that, I'm not sure how to help you, the error is clear, I'm not sitting in front of your files, if it's telling you it cannot import SECRET_KEY, then something isn't configured correctly and it cannot import it.
vsoch
commented
4 years ago One last thing to try - in your settings/main.py this is where the secrets.py are imported:
try:
from .secrets import *
except ImportError:
passIf you have a syntax (or other) error, it likely is catching and then passing. I would print a statement after the except to see if you have an issue with importing secrets, period.
tejasdixit836
commented
4 years ago thanks a lot for the help ,
so far i tried to find what modules are available for import
In [3]: from shub.settings.secrets import AUTH_LDAP_BIND_DN AUTH_LDAP_USER_SEARCH SECRET_KEY package CONTRIBUTING.md AUTH_LDAP_BIND_PASSWORD ldap doc %%! Dockerfile AUTH_LDAP_GROUP_SEARCH LDAPSearch file AUTHORS.md %%HTML > AUTH_LDAP_SERVER_URI PosixGroupType name CHANGELOG.md LICENSE statement
which suggest SECRET_KEY is found. but when i try to import it throws error.
i did try to print a statement after except in main.py and you are absolutely correct , i see my statement when i run docker-compose up, there is an issue while importing secrets. is this because may be i do not have proper Python setup in my host? while reinstalling python i found that _Ssl and _hashlib were not installed on my host Python(3.6). complains about openssl . and i externally installed openssl still doesnt install _ssl (sure it might be out of scope here , but just trying to find the cause so i can do something about it)
On Sun, Nov 24, 2019 at 12:31 AM Vanessasaurus notifications@github.com wrote:
One last thing to try - in your settings/main.py this is where the secrets.py are imported:
try: from .secrets import *except ImportError: pass
If you have a syntax (or other) error, it likely is catching and then passing. I would print a statement after the except to see if you have an issue with importing secrets, period.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/singularityhub/sregistry/issues/252?email_source=notifications&email_token=AN27GCKG5L6CMIVHNXMCQL3QVF4ZFA5CNFSM4JQLWRC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE73QBA#issuecomment-557824004, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN27GCOF3DXZDX6ZJZH7WW3QVF4ZFANCNFSM4JQLWRCQ .
vsoch
commented
4 years ago Sounds like you figured it out! Good job.
tejasdixit836
commented
4 years ago Sorry for the late reply
Turns out the issue was the docker containers were not able to talk to the internet .
After configuring the json for docker and building the containers again it worked like a charm :)
Thanks a lot for your help.
On Sun, Nov 24, 2019, 13:36 Vanessasaurus notifications@github.com wrote:
Sounds like you figured it out! Good job.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/singularityhub/sregistry/issues/252?email_source=notifications&email_token=AN27GCLGINVPV3A2U36JAOLQVIYY5A5CNFSM4JQLWRC2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFAF6BY#issuecomment-557866759, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN27GCMVSR2TIWVY2XAHWHDQVIYY5ANCNFSM4JQLWRCQ .
vsoch
commented
4 years ago No worries! Closing issue.
I am trying to configure sregistry. I am following your documentation.
so far i have done all the steps and started the docker-compose but i get this error mentioned below.
i have generated secret file used ldap auth for authentication. i have done it on another machine and it works perfectly fine. i am trying to migrate it to production and i am not sure where i have missed. i have tried to copy the same sregistry and also set up new one. but i get same error. probably there is some module i have not downloaded but do not know what it is.
can you have a look at the error and help me?
Thanks
Starting sregistry_db_1 ... Starting sregistry_db_1 ... done Starting sregistry_uwsgi_1 ... done Starting sregistry_nginx_1 ... done Starting sregistry_scheduler_1 ... done Starting sregistry_worker_1 ... done Attaching to sregistry_redis_1, sregistry_db_1, sregistry_uwsgi_1, sregistry_worker_1, sregistry_nginx_1, sregistry_scheduler_1 db_1 | db_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization db_1 | db_1 | 2019-11-22 03:41:40.635 UTC [1] LOG: starting PostgreSQL 12.1 (Debian 12.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit db_1 | 2019-11-22 03:41:40.639 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 db_1 | 2019-11-22 03:41:40.641 UTC [1] LOG: could not create IPv6 socket for address "::": Address family not supported by protocol db_1 | 2019-11-22 03:41:40.650 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" db_1 | 2019-11-22 03:41:40.677 UTC [24] LOG: database system was shut down at 2019-11-21 16:34:46 UTC db_1 | 2019-11-22 03:41:40.682 UTC [1] LOG: database system is ready to accept connections uwsgi_1 | Traceback (most recent call last): uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
uwsgi_1 | self.execute(args, cmd_options)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
uwsgi_1 | self.check()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
uwsgi_1 | include_deployment_checks=include_deployment_checks,
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 377, in _run_checks
uwsgi_1 | return checks.run_checks(kwargs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
uwsgi_1 | new_errors = check(app_configs=app_configs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/templates.py", line 29, in check_string_if_invalid_is_string
uwsgi_1 | for conf in settings.TEMPLATES:
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
uwsgi_1 | self.execute( args, cmd_options)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
uwsgi_1 | self.check()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
uwsgi_1 | include_deployment_checks=include_deployment_checks,
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 377, in _run_checks
uwsgi_1 | return checks.run_checks(kwargs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
uwsgi_1 | new_errors = check(app_configs=app_configs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/templates.py", line 29, in check_string_if_invalid_is_string
uwsgi_1 | for conf in settings.TEMPLATES:
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
uwsgi_1 | self.execute(args, cmd_options)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
uwsgi_1 | self.check()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
uwsgi_1 | include_deployment_checks=include_deployment_checks,
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 377, in _run_checks
uwsgi_1 | return checks.run_checks(kwargs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
uwsgi_1 | new_errors = check(app_configs=app_configs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/templates.py", line 29, in check_string_if_invalid_is_string
uwsgi_1 | for conf in settings.TEMPLATES:
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
uwsgi_1 | self.execute( args, cmd_options)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
uwsgi_1 | self.check()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
uwsgi_1 | include_deployment_checks=include_deployment_checks,
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 377, in _run_checks
uwsgi_1 | return checks.run_checks(kwargs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
uwsgi_1 | new_errors = check(app_configs=app_configs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/templates.py", line 29, in check_string_if_invalid_is_string
uwsgi_1 | for conf in settings.TEMPLATES:
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
worker_1 | Traceback (most recent call last):
worker_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 204, in fetch_command
worker_1 | app_name = commands[subcommand]
worker_1 | KeyError: 'rqworker'
worker_1 |
worker_1 | During handling of the above exception, another exception occurred:
worker_1 |
worker_1 | Traceback (most recent call last):
worker_1 | File "/code/manage.py", line 8, in
worker_1 | execute_from_command_line(sys.argv)
worker_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
worker_1 | utility.execute()
worker_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
worker_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
worker_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 211, in fetch_command
worker_1 | settings.INSTALLED_APPS
worker_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
worker_1 | self._setup(name)
worker_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
worker_1 | self._wrapped = Settings(settings_module)
worker_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
worker_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
worker_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
redis_1 | 1:C 21 Nov 2019 09:37:08.830 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 21 Nov 2019 09:37:08.830 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 21 Nov 2019 09:37:08.830 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 21 Nov 2019 09:37:08.836 # Not listening to IPv6: unsupproted
redis_1 | 1:M 21 Nov 2019 09:37:08.837 Running mode=standalone, port=6379.
redis_1 | 1:M 21 Nov 2019 09:37:08.837 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 21 Nov 2019 09:37:08.837 # Server initialized
redis_1 | 1:M 21 Nov 2019 09:37:08.837 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 21 Nov 2019 09:37:08.837 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 21 Nov 2019 09:37:08.837 Ready to accept connections
redis_1 | 1:signal-handler (1574329071) Received SIGTERM scheduling shutdown...
redis_1 | 1:M 21 Nov 2019 09:37:51.504 # User requested shutdown...
redis_1 | 1:M 21 Nov 2019 09:37:51.504 Saving the final RDB snapshot before exiting.
redis_1 | 1:M 21 Nov 2019 09:37:51.507 DB saved on disk
redis_1 | 1:M 21 Nov 2019 09:37:51.507 # Redis is now ready to exit, bye bye...
redis_1 | 1:C 21 Nov 2019 15:27:16.091 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 21 Nov 2019 15:27:16.091 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 21 Nov 2019 15:27:16.091 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 21 Nov 2019 15:27:16.102 # Not listening to IPv6: unsupproted
redis_1 | 1:M 21 Nov 2019 15:27:16.103 Running mode=standalone, port=6379.
redis_1 | 1:M 21 Nov 2019 15:27:16.103 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 21 Nov 2019 15:27:16.103 # Server initialized
redis_1 | 1:M 21 Nov 2019 15:27:16.103 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 21 Nov 2019 15:27:16.103 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 21 Nov 2019 15:27:16.103 DB loaded from disk: 0.000 seconds
redis_1 | 1:M 21 Nov 2019 15:27:16.103 Ready to accept connections
redis_1 | 1:signal-handler (1574350085) Received SIGTERM scheduling shutdown...
redis_1 | 1:M 21 Nov 2019 15:28:05.441 # User requested shutdown...
redis_1 | 1:M 21 Nov 2019 15:28:05.441 Saving the final RDB snapshot before exiting.
redis_1 | 1:M 21 Nov 2019 15:28:05.444 DB saved on disk
redis_1 | 1:M 21 Nov 2019 15:28:05.444 # Redis is now ready to exit, bye bye...
redis_1 | 1:C 21 Nov 2019 15:29:07.716 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 21 Nov 2019 15:29:07.716 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 21 Nov 2019 15:29:07.716 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 21 Nov 2019 15:29:07.726 # Not listening to IPv6: unsupproted
redis_1 | 1:M 21 Nov 2019 15:29:07.728 Running mode=standalone, port=6379.
redis_1 | 1:M 21 Nov 2019 15:29:07.728 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 21 Nov 2019 15:29:07.728 # Server initialized
redis_1 | 1:M 21 Nov 2019 15:29:07.728 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 21 Nov 2019 15:29:07.728 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 21 Nov 2019 15:29:07.728 DB loaded from disk: 0.000 seconds
redis_1 | 1:M 21 Nov 2019 15:29:07.728 Ready to accept connections
redis_1 | 1:signal-handler (1574350168) Received SIGTERM scheduling shutdown...
redis_1 | 1:M 21 Nov 2019 15:29:28.316 # User requested shutdown...
redis_1 | 1:M 21 Nov 2019 15:29:28.316 Saving the final RDB snapshot before exiting.
redis_1 | 1:M 21 Nov 2019 15:29:28.318 DB saved on disk
redis_1 | 1:M 21 Nov 2019 15:29:28.318 # Redis is now ready to exit, bye bye...
redis_1 | 1:C 21 Nov 2019 15:34:47.827 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 21 Nov 2019 15:34:47.827 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 21 Nov 2019 15:34:47.827 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 21 Nov 2019 15:34:47.831 # Not listening to IPv6: unsupproted
redis_1 | 1:M 21 Nov 2019 15:34:47.834 Running mode=standalone, port=6379.
redis_1 | 1:M 21 Nov 2019 15:34:47.834 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 21 Nov 2019 15:34:47.834 # Server initialized
redis_1 | 1:M 21 Nov 2019 15:34:47.834 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 21 Nov 2019 15:34:47.834 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 21 Nov 2019 15:34:47.834 DB loaded from disk: 0.000 seconds
redis_1 | 1:M 21 Nov 2019 15:34:47.834 Ready to accept connections
redis_1 | 1:signal-handler (1574350608) Received SIGTERM scheduling shutdown...
redis_1 | 1:M 21 Nov 2019 15:36:48.651 # User requested shutdown...
redis_1 | 1:M 21 Nov 2019 15:36:48.651 Saving the final RDB snapshot before exiting.
redis_1 | 1:M 21 Nov 2019 15:36:48.657 DB saved on disk
redis_1 | 1:M 21 Nov 2019 15:36:48.657 # Redis is now ready to exit, bye bye...
redis_1 | 1:C 21 Nov 2019 15:41:45.256 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 21 Nov 2019 15:41:45.256 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 21 Nov 2019 15:41:45.256 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 21 Nov 2019 15:41:45.264 # Not listening to IPv6: unsupproted
redis_1 | 1:M 21 Nov 2019 15:41:45.265 Running mode=standalone, port=6379.
redis_1 | 1:M 21 Nov 2019 15:41:45.265 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 21 Nov 2019 15:41:45.265 # Server initialized
redis_1 | 1:M 21 Nov 2019 15:41:45.265 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 21 Nov 2019 15:41:45.265 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 21 Nov 2019 15:41:45.265 DB loaded from disk: 0.000 seconds
redis_1 | 1:M 21 Nov 2019 15:41:45.265 Ready to accept connections
redis_1 | 1:C 21 Nov 2019 15:43:41.196 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 21 Nov 2019 15:43:41.196 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 21 Nov 2019 15:43:41.196 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 21 Nov 2019 15:43:41.203 # Not listening to IPv6: unsupproted
redis_1 | 1:M 21 Nov 2019 15:43:41.204 Running mode=standalone, port=6379.
redis_1 | 1:M 21 Nov 2019 15:43:41.204 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 21 Nov 2019 15:43:41.204 # Server initialized
redis_1 | 1:M 21 Nov 2019 15:43:41.204 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 21 Nov 2019 15:43:41.204 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 21 Nov 2019 15:43:41.204 DB loaded from disk: 0.000 seconds
redis_1 | 1:M 21 Nov 2019 15:43:41.204 Ready to accept connections
redis_1 | 1:C 21 Nov 2019 16:20:52.169 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 21 Nov 2019 16:20:52.169 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 21 Nov 2019 16:20:52.169 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 21 Nov 2019 16:20:52.180 # Not listening to IPv6: unsupproted
redis_1 | 1:M 21 Nov 2019 16:20:52.181 Running mode=standalone, port=6379.
redis_1 | 1:M 21 Nov 2019 16:20:52.181 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 21 Nov 2019 16:20:52.181 # Server initialized
redis_1 | 1:M 21 Nov 2019 16:20:52.181 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 21 Nov 2019 16:20:52.181 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 21 Nov 2019 16:20:52.181 DB loaded from disk: 0.000 seconds
redis_1 | 1:M 21 Nov 2019 16:20:52.181 Ready to accept connections
redis_1 | 1:signal-handler (1574354086) Received SIGTERM scheduling shutdown...
redis_1 | 1:M 21 Nov 2019 16:34:46.275 # User requested shutdown...
redis_1 | 1:M 21 Nov 2019 16:34:46.275 Saving the final RDB snapshot before exiting.
redis_1 | 1:M 21 Nov 2019 16:34:46.279 DB saved on disk
redis_1 | 1:M 21 Nov 2019 16:34:46.279 # Redis is now ready to exit, bye bye...
redis_1 | 1:C 21 Nov 2019 16:39:44.323 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 21 Nov 2019 16:39:44.323 # Redis version=5.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 21 Nov 2019 16:39:44.323 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 21 Nov 2019 16:39:44.328 # Not listening to IPv6: unsupproted
redis_1 | 1:M 21 Nov 2019 16:39:44.330 Running mode=standalone, port=6379.
redis_1 | 1:M 21 Nov 2019 16:39:44.330 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
redis_1 | 1:M 21 Nov 2019 16:39:44.330 # Server initialized
redis_1 | 1:M 21 Nov 2019 16:39:44.330 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 21 Nov 2019 16:39:44.330 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
redis_1 | 1:M 21 Nov 2019 16:39:44.330 DB loaded from disk: 0.000 seconds
redis_1 | 1:M 21 Nov 2019 16:39:44.330 Ready to accept connections
scheduler_1 | Traceback (most recent call last):
scheduler_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 204, in fetch_command
scheduler_1 | app_name = commands[subcommand]
scheduler_1 | KeyError: 'rqscheduler'
scheduler_1 |
scheduler_1 | During handling of the above exception, another exception occurred:
scheduler_1 |
scheduler_1 | Traceback (most recent call last):
scheduler_1 | File "/code/manage.py", line 8, in
scheduler_1 | execute_from_command_line(sys.argv)
scheduler_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
scheduler_1 | utility.execute()
scheduler_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
scheduler_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
scheduler_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 211, in fetch_command
scheduler_1 | settings.INSTALLED_APPS
scheduler_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
scheduler_1 | self._setup(name)
scheduler_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
scheduler_1 | self._wrapped = Settings(settings_module)
scheduler_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
scheduler_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
scheduler_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
sregistry_worker_1 exited with code 1
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
uwsgi_1 | self.execute( args, cmd_options)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
uwsgi_1 | self.check()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
uwsgi_1 | include_deployment_checks=include_deployment_checks,
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 377, in _run_checks
uwsgi_1 | return checks.run_checks(kwargs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
uwsgi_1 | new_errors = check(app_configs=app_configs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/templates.py", line 29, in check_string_if_invalid_is_string
uwsgi_1 | for conf in settings.TEMPLATES:
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
sregistry_scheduler_1 exited with code 1
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
uwsgi_1 | self.execute(*args, cmd_options)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
uwsgi_1 | self.check()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
uwsgi_1 | include_deployment_checks=include_deployment_checks,
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/commands/migrate.py", line 64, in _run_checks
uwsgi_1 | issues = run_checks(tags=[Tags.database])
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
uwsgi_1 | new_errors = check(app_configs=app_configs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/database.py", line 9, in check_database_backends
uwsgi_1 | for conn in connections.all():
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 216, in all
uwsgi_1 | return [self[alias] for alias in self]
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 213, in iter
uwsgi_1 | return iter(self.databases)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/utils/functional.py", line 80, in get
uwsgi_1 | res = instance.dict[self.name] = self.func(instance)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 147, in databases
uwsgi_1 | self._databases = settings.DATABASES
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
uwsgi_1 | self.execute(*args, *cmd_options)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
uwsgi_1 | self.check()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
uwsgi_1 | include_deployment_checks=include_deployment_checks,
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/commands/migrate.py", line 64, in _run_checks
uwsgi_1 | issues = run_checks(tags=[Tags.database])
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
uwsgi_1 | new_errors = check(app_configs=app_configs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/database.py", line 9, in check_database_backends
uwsgi_1 | for conn in connections.all():
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 216, in all
uwsgi_1 | return [self[alias] for alias in self]
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 213, in iter
uwsgi_1 | return iter(self.databases)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/utils/functional.py", line 80, in get
uwsgi_1 | res = instance.dict[self.name] = self.func(instance)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 147, in databases
uwsgi_1 | self._databases = settings.DATABASES
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 323, in run_from_argv
uwsgi_1 | self.execute( args, cmd_options)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 361, in execute
uwsgi_1 | self.check()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/base.py", line 390, in check
uwsgi_1 | include_deployment_checks=include_deployment_checks,
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/commands/migrate.py", line 64, in _run_checks
uwsgi_1 | issues = run_checks(tags=[Tags.database])
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/registry.py", line 72, in run_checks
uwsgi_1 | new_errors = check(app_configs=app_configs)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/checks/database.py", line 9, in check_database_backends
uwsgi_1 | for conn in connections.all():
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 216, in all
uwsgi_1 | return [self[alias] for alias in self]
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 213, in iter
uwsgi_1 | return iter(self.databases)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/utils/functional.py", line 80, in get
uwsgi_1 | res = instance.dict[self.name] = self.func(instance)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/db/utils.py", line 147, in databases
uwsgi_1 | self._databases = settings.DATABASES
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 204, in fetch_command
uwsgi_1 | app_name = commands[subcommand]
uwsgi_1 | KeyError: 'collectstatic'
uwsgi_1 |
uwsgi_1 | During handling of the above exception, another exception occurred:
uwsgi_1 |
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "manage.py", line 8, in
uwsgi_1 | execute_from_command_line(sys.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
uwsgi_1 | utility.execute()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 375, in execute
uwsgi_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/management/init.py", line 211, in fetch_command
uwsgi_1 | settings.INSTALLED_APPS
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
uwsgi_1 | Starting periodic command scheduler: cron.
uwsgi_1 | [uWSGI] getting INI configuration from uwsgi.ini
uwsgi_1 | Fri Nov 22 03:41:43 2019 - Starting uWSGI 2.0.18 (64bit) on [Fri Nov 22 03:41:43 2019]
uwsgi_1 | Fri Nov 22 03:41:43 2019 - compiled with version: 8.3.0 on 13 November 2019 17:26:15
uwsgi_1 | Fri Nov 22 03:41:43 2019 - os: Linux-3.10.0-1062.1.2.el7.x86_64 #1 SMP Mon Sep 16 14:19:51 EDT 2019
uwsgi_1 | Fri Nov 22 03:41:43 2019 - nodename: bd94f31a539a
uwsgi_1 | Fri Nov 22 03:41:43 2019 - machine: x86_64
uwsgi_1 | Fri Nov 22 03:41:43 2019 - clock source: unix
uwsgi_1 | Fri Nov 22 03:41:43 2019 - pcre jit disabled
uwsgi_1 | Fri Nov 22 03:41:43 2019 - detected number of CPU cores: 2
uwsgi_1 | Fri Nov 22 03:41:43 2019 - current working directory: /code
uwsgi_1 | Fri Nov 22 03:41:43 2019 - detected binary path: /usr/local/bin/uwsgi
uwsgi_1 | Fri Nov 22 03:41:43 2019 - uWSGI running as root, you can use --uid/--gid/--chroot options
uwsgi_1 | Fri Nov 22 03:41:43 2019 - WARNING: you are running uWSGI as root !!! (use the --uid flag)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - chdir() to /code/
uwsgi_1 | Fri Nov 22 03:41:43 2019 - your memory page size is 4096 bytes
uwsgi_1 | Fri Nov 22 03:41:43 2019 - detected max file descriptor number: 1048576
uwsgi_1 | Fri Nov 22 03:41:43 2019 - lock engine: pthread robust mutexes
uwsgi_1 | Fri Nov 22 03:41:43 2019 - thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - uwsgi socket 0 bound to TCP address :3031 fd 3
uwsgi_1 | Fri Nov 22 03:41:43 2019 - uWSGI running as root, you can use --uid/--gid/--chroot options
uwsgi_1 | Fri Nov 22 03:41:43 2019 - WARNING: you are running uWSGI as root !!! (use the --uid flag)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - Python version: 3.5.7 (default, Oct 17 2019, 07:04:41) [GCC 8.3.0]
uwsgi_1 | Fri Nov 22 03:41:43 2019 - Python main interpreter initialized at 0x55f9bc365000
uwsgi_1 | Fri Nov 22 03:41:43 2019 - uWSGI running as root, you can use --uid/--gid/--chroot options
uwsgi_1 | Fri Nov 22 03:41:43 2019 - WARNING: you are running uWSGI as root !!! (use the --uid flag)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - python threads support enabled
uwsgi_1 | Fri Nov 22 03:41:43 2019 - your server socket listen backlog is limited to 100 connections
uwsgi_1 | Fri Nov 22 03:41:43 2019 - your mercy for graceful operations on workers is 60 seconds
uwsgi_1 | Fri Nov 22 03:41:43 2019 - mapped 521440 bytes (509 KB) for 16 cores
uwsgi_1 | Fri Nov 22 03:41:43 2019 - Operational MODE: preforking+threaded
uwsgi_1 | Traceback (most recent call last):
uwsgi_1 | File "shub/wsgi.py", line 7, in
uwsgi_1 | application = get_wsgi_application()
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/core/wsgi.py", line 12, in get_wsgi_application
uwsgi_1 | django.setup(set_prefix=False)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/init.py", line 19, in setup
uwsgi_1 | configure_logging(settings.LOGGING_CONFIG, settings.LOGGING)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 79, in getattr
uwsgi_1 | self._setup(name)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 66, in _setup
uwsgi_1 | self._wrapped = Settings(settings_module)
uwsgi_1 | File "/usr/local/lib/python3.5/site-packages/django/conf/init.py", line 176, in init
uwsgi_1 | raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
uwsgi_1 | django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.
uwsgi_1 | Fri Nov 22 03:41:43 2019 - unable to load app 0 (mountpoint='') (callable not found or import error)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - no app loaded. going in full dynamic mode
uwsgi_1 | Fri Nov 22 03:41:43 2019 - uWSGI running as root, you can use --uid/--gid/--chroot options
uwsgi_1 | Fri Nov 22 03:41:43 2019 - WARNING: you are running uWSGI as root !!! (use the --uid flag)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - uWSGI is running in multiple interpreter mode
uwsgi_1 | Fri Nov 22 03:41:43 2019 - spawned uWSGI master process (pid: 35)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - spawned uWSGI worker 1 (pid: 37, cores: 4)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - spawned uWSGI worker 2 (pid: 38, cores: 4)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - spawned uWSGI worker 3 (pid: 39, cores: 4)
uwsgi_1 | Fri Nov 22 03:41:43 2019 - spawned uWSGI worker 4 (pid: 40, cores: 4)