Closed metamorphious closed 8 years ago
@metamorphious Could you make a backup of your existing data and delete the current data, repull the Docker zulip image and try again? I'm not running into this problem myself.
Deleted:
/opt/docker/zulip/postgresql/data/9.3
/opt/docker/zulip/redis/dump.rdb
/opt/docker/zulip/zulip/*
Did:
docker pull quay.io/galexrt/zulip:v1.3.10
v1.3.10: Pulling from galexrt/zulip
203137e8afd5: Already exists
2ff1bbbe9310: Already exists
933ae2486129: Already exists
a3ed95caeb02: Already exists
151530266ef9: Already exists
a425eccbecc7: Already exists
101d554e876e: Already exists
8d1677382d80: Already exists
cdc4165ca4c8: Already exists
0bca4baf391b: Already exists
039b964b4541: Already exists
74ebfc3baaf9: Already exists
Digest: sha256:5952e288b9837a9de670045ca1718b0b54d89e51f8eb5ae8ee76afcf88ed53a1
Status: Image is up to date for quay.io/galexrt/zulip:v1.3.10
still get the errors...
Can you try with the dev version and see if the errors persist? quay.io/galexrt/zulip:dev
dev version gives me the following error:
...
zulip_1 | Executing Zulip configuration ...
zulip_1 | Setting key "EXTERNAL_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "EMAIL_HOST", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1 | Setting key "NOREPLY_EMAIL_ADDRESS", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "ZULIP_ADMINISTRATOR", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "REDIS_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "RABBITMQ_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "EMAIL_HOST_USER", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1 | Setting key "DEFAULT_FROM_EMAIL", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "MEMCACHED_LOCATION", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "ADMIN_DOMAIN", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Traceback (most recent call last):
zulip_1 | File "/home/zulip/deployments/current/manage.py", line 24, in <module>
zulip_1 | execute_from_command_line(sys.argv)
zulip_1 | File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
zulip_1 | utility.execute()
zulip_1 | File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 312, in execute
zulip_1 | django.setup()
zulip_1 | File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 17, in setup
zulip_1 | configure_logging(settings.LOGGING_CONFIG, settings.LOGGING)
zulip_1 | File "/usr/lib/python2.7/dist-packages/django/utils/log.py", line 86, in configure_logging
zulip_1 | logging_config_func(logging_settings)
zulip_1 | File "/usr/lib/python2.7/logging/config.py", line 794, in dictConfig
zulip_1 | dictConfigClass(config).configure()
zulip_1 | File "/usr/lib/python2.7/logging/config.py", line 576, in configure
zulip_1 | '%r: %s' % (name, e))
zulip_1 | ValueError: Unable to configure handler 'zulip_admins': Cannot resolve 'zerver.logging_handlers.AdminZulipHandler': No module named logging_handlers
zulip_zulip_1 exited with code 1
@metamorphious Looking into the problem with the dev version image and the v1.3.10 image.
@metamorphious Could you try using the new released image from Docker Hub?
The new version is galexrt/zulip:v1.3.10-1
.
(Don't use the quay.io/galexrt/zulip
image currently! The builds on quay.io are currently "stuck" due to an endless build I caused.. But the Docker Hub images are up to date now)
Seems to be working now. Thanks for your work! The only thing is that I can't login at the webinterface. Tried the admin account and the user account specified in the docker-compose.yml. But I always get the login error: "Please enter a correct email and password. Note that both fields may be case-sensitive."
@metamorphious Have you tried with the following login details?
Taken from your posted docker-compose.yml
:
ZULIP_USER_EMAIL: "example@my-domain.com"
ZULIP_USER_PASS: "zulip"
yes I tested that.. but can't login with that too.
@metamorphious Could you please try to stop all containers, remove the current /opt/docker/zulip
, start again and check if those login details are working?
If the login still isn't working please attach the full logs of all containers as a comment.
Nope can't login with the credentials given in ZULIP_USER_EMAIL and ZULIP_USER_PASS. I tried to register a new user but i get the message "Your e-mail does not match any existing open organization. Use a different e-mail address, or contact admin@my-domain.com with questions." The domain (my-domain.com in this example) is set in ZULIP_USER_DOMAIN and in SETTING_ADMIN_DOMAIN.
Logs from docker-compose: (are there log files I could examine?)
$ docker-compose up
Creating dockerzulip_redis_1
Creating dockerzulip_memcached_1
Creating dockerzulip_rabbitmq_1
Creating dockerzulip_database_1
Creating dockerzulip_zulip_1
Attaching to dockerzulip_redis_1, dockerzulip_memcached_1, dockerzulip_rabbitmq_1, dockerzulip_database_1, dockerzulip_zulip_1
redis_1 | Starting redis-server...
redis_1 | _._
redis_1 | _.-``__ ''-._
redis_1 | _.-`` `. `_. ''-._ Redis 2.8.4 (00000000/0) 64 bit
redis_1 | .-`` .-```. ```\/ _.,_ ''-._
redis_1 | ( ' , .-` | `, ) Running in stand alone mode
redis_1 | |`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
redis_1 | | `-._ `._ / _.-' | PID: 1
redis_1 | `-._ `-._ `-./ _.-' _.-'
redis_1 | |`-._`-._ `-.__.-' _.-'_.-'|
redis_1 | | `-._`-._ _.-'_.-' | http://redis.io
redis_1 | `-._ `-._`-.__.-'_.-' _.-'
redis_1 | |`-._`-._ `-.__.-' _.-'_.-'|
redis_1 | | `-._`-._ _.-'_.-' |
redis_1 | `-._ `-._`-.__.-'_.-' _.-'
redis_1 | `-._ `-.__.-' _.-'
redis_1 | `-._ _.-'
redis_1 | `-.__.-'
redis_1 |
redis_1 | [1] 24 Apr 15:15:48.191 # Server started, Redis version 2.8.4
redis_1 | [1] 24 Apr 15:15:48.192 # 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] 24 Apr 15:15:48.192 * The server is now ready to accept connections on port 6379
redis_1 | [1] 24 Apr 15:15:48.192 * The server is now ready to accept connections at /var/run/redis/redis.sock
database_1 | Initializing datadir...
database_1 | Initializing certdir...
database_1 | Initializing logdir...
database_1 | Initializing rundir...
database_1 | Setting resolv.conf ACLs...
database_1 | setfacl: /etc/resolv.conf: Operation not supported
database_1 | Initializing database...
zulip_1 | === Begin Initial Configuration Phase ===
zulip_1 | Creating backups folder ...
zulip_1 | Created backups folder.
zulip_1 | Creating certs folder ...
zulip_1 | Created certs folder.
zulip_1 | Creating uploads folder ...
zulip_1 | Created uploads folder.
zulip_1 | Preparing and linking the uploads folder ...
zulip_1 | Prepared and linked the uploads directory.
zulip_1 | Executing nginx configuration ...
zulip_1 | Nginx configuration succeeded.
zulip_1 | Exectuing certificates configuration...
zulip_1 | No certs in "/data/certs".
zulip_1 | Autogenerating certificates ...
zulip_1 | Generating RSA private key, 4096 bit long modulus
zulip_1 | ........................................................++
zulip_1 | ........................................................................................++
zulip_1 | e is 65537 (0x10001)
zulip_1 | writing RSA key
zulip_1 | Signature ok
zulip_1 | subject=/C=US/ST=Denial/L=Springfield/O=Dis/CN=team.example.com
zulip_1 | Getting Private key
zulip_1 | Certificate autogeneration succeeded.
zulip_1 | Certificates configuration succeeded.
zulip_1 | Setting Zulip secrets ...
zulip_1 | Generating Zulip secrets ...
rabbitmq_1 |
rabbitmq_1 | RabbitMQ 3.5.5. Copyright (C) 2007-2015 Pivotal Software, Inc.
rabbitmq_1 | ## ## Licensed under the MPL. See http://www.rabbitmq.com/
rabbitmq_1 | ## ##
rabbitmq_1 | ########## Logs: tty
rabbitmq_1 | ###### ## tty
rabbitmq_1 | ##########
rabbitmq_1 | Starting broker...
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:51 ===
rabbitmq_1 | Starting RabbitMQ 3.5.5 on Erlang 18.1
rabbitmq_1 | Copyright (C) 2007-2015 Pivotal Software, Inc.
rabbitmq_1 | Licensed under the MPL. See http://www.rabbitmq.com/
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:51 ===
rabbitmq_1 | node : rabbit@zulip-rabbit
rabbitmq_1 | home dir : /var/lib/rabbitmq
rabbitmq_1 | config file(s) : /etc/rabbitmq/rabbitmq.config
rabbitmq_1 | cookie hash : U38MtqV4/Q7U0DvCRO7cGA==
rabbitmq_1 | log : tty
rabbitmq_1 | sasl log : tty
rabbitmq_1 | database dir : /var/lib/rabbitmq/mnesia/rabbit@zulip-rabbit
zulip_1 | Generated Camo config file /etc/default/camo
zulip_1 | Generated /etc/zulip/zulip-secrets.conf with auto-generated secrets!
zulip_1 | Secrets generation succeeded.
zulip_1 | Secret found for "rabbitmq_password".
zulip_1 | Secret added for "email_password".
zulip_1 | Zulip secrets configuration succeeded.
zulip_1 | Setting database configuration ...
zulip_1 | Setting key "DATABASES", type "array" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1 | Database configuration succeeded.
zulip_1 | Activating authentication backends ...
zulip_1 | Setting key "AUTHENTICATION_BACKENDS", type "array" in file "/etc/zulip/settings.py".
zulip_1 | Adding authentication backend "EmailAuthBackend".
zulip_1 | Authentication backend activation succeeded.
zulip_1 | Executing Zulip configuration ...
zulip_1 | Setting key "EXTERNAL_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "EMAIL_HOST", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1 | Setting key "NOREPLY_EMAIL_ADDRESS", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "ZULIP_ADMINISTRATOR", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "REDIS_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "RABBITMQ_HOST", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "EMAIL_HOST_USER", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
zulip_1 | Setting key "DEFAULT_FROM_EMAIL", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "MEMCACHED_LOCATION", type "string" in file "/etc/zulip/settings.py".
zulip_1 | Setting key "ADMIN_DOMAIN", type "string" in file "/etc/zulip/settings.py".
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:53 ===
rabbitmq_1 | Memory limit set to 800MB of 2000MB total.
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:53 ===
rabbitmq_1 | Disk free limit set to 50MB
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:53 ===
rabbitmq_1 | Limiting to approx 524188 file handles (471767 sockets)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:53 ===
rabbitmq_1 | FHC read buffering: ON
rabbitmq_1 | FHC write buffering: ON
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:53 ===
rabbitmq_1 | application: mnesia
rabbitmq_1 | exited: stopped
rabbitmq_1 | type: temporary
database_1 | Configuring hot standby...
database_1 | ‣ Setting postgresql.conf parameter: wal_level = 'hot_standby'
database_1 | ‣ Setting postgresql.conf parameter: max_wal_senders = '16'
database_1 | ‣ Setting postgresql.conf parameter: checkpoint_segments = '8'
database_1 | ‣ Setting postgresql.conf parameter: wal_keep_segments = '32'
database_1 | ‣ Setting postgresql.conf parameter: hot_standby = 'on'
database_1 | ‣ Setting postgresql.conf parameter: data_directory = '/var/lib/postgresql/9.3/main'
database_1 | ‣ Setting postgresql.conf parameter: log_directory = '/var/log/postgresql'
database_1 | ‣ Setting postgresql.conf parameter: log_filename = 'postgresql-9.3-main.log'
database_1 | ‣ Setting postgresql.conf parameter: ssl = 'off'
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | Priority queues enabled, real BQ is rabbit_variable_queue
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | Adding vhost '/'
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | Creating user 'zulip'
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | Setting user tags for user 'zulip' to [administrator]
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | Setting permissions for 'zulip' in '/' to '.*', '.*', '.*'
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | msg_store_transient: using rabbit_msg_store_ets_index to provide index
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | msg_store_persistent: using rabbit_msg_store_ets_index to provide index
rabbitmq_1 |
rabbitmq_1 | =WARNING REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | msg_store_persistent: rebuilding indices from scratch
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | started TCP Listener on [::]:5672
rabbitmq_1 | completed with 0 plugins.
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:15:54 ===
rabbitmq_1 | Server startup complete; 0 plugins started.
database_1 | Creating database user: zulip
zulip_1 | Zulip configuration succeeded.
zulip_1 | Auto backup enabled.
zulip_1 | === End Initial Configuration Phase ===
zulip_1 | === Begin Bootstrap Phase ===
zulip_1 | Waiting for database server to allow connections ...
database_1 | Creating database: zulip...
database_1 | ‣ Granting access to zulip user...
database_1 | Starting PostgreSQL 9.3...
database_1 | LOG: database system was shut down at 2016-04-24 15:15:56 UTC
database_1 | LOG: MultiXact member wraparound protections are now enabled
database_1 | LOG: database system is ready to accept connections
database_1 | LOG: autovacuum launcher started
zulip_1 | ..(Re)creating database structure ...
zulip_1 | Setting up the database, schema and user ...
zulip_1 | ERROR: permission denied to create role
database_1 | ERROR: permission denied to create role
database_1 | STATEMENT: CREATE USER zulip;
zulip_1 | ALTER ROLE
database_1 | ERROR: database "zulip" already exists
database_1 | STATEMENT: CREATE DATABASE zulip OWNER=zulip;
database_1 | ERROR: schema "zulip" already exists
database_1 | STATEMENT: CREATE SCHEMA zulip AUTHORIZATION zulip;
zulip_1 | ERROR: database "zulip" already exists
zulip_1 | ERROR: schema "zulip" already exists
zulip_1 | Creating tsearch_extras extension ...
database_1 | FATAL: password authentication failed for user "postgres"
database_1 | DETAIL: Connection matched pg_hba.conf line 94: "host all all 0.0.0.0/0 md5"
zulip_1 | psql: FATAL: password authentication failed for user "postgres"
zulip_1 | Database structure recreated.
zulip_1 | Bootstrapping RabbitMQ ...
zulip_1 | RabbitMQ deleting user "guest".
zulip_1 | RabbitMQ adding user "zulip".
zulip_1 | RabbitMQ setting user tags for "zulip".
zulip_1 | RabbitMQ setting permissions for user "zulip".
zulip_1 | RabbitMQ bootstrap succeeded.
zulip_1 | Executing Zulip user creation script ...
zulip_1 | Zulip user creation left enabled.
zulip_1 | Executing Zulip first start init ...
zulip_1 | First Start Init not needed. Continuing.
zulip_1 | Migrating Zulip to new version ...
zulip_1 | Operations to perform:
zulip_1 | Synchronize unmigrated apps: staticfiles, pipeline
zulip_1 | Apply all migrations: confirmation, sessions, guardian, zerver, sites, auth, contenttypes
zulip_1 | Synchronizing apps without migrations:
zulip_1 | Creating tables...
zulip_1 | Running deferred SQL...
zulip_1 | Installing custom SQL...
zulip_1 | Running migrations:
zulip_1 | Rendering model states... DONE
zulip_1 | Applying contenttypes.0001_initial... OK
zulip_1 | Applying contenttypes.0002_remove_content_type_name... OK
zulip_1 | Applying auth.0001_initial... OK
zulip_1 | Applying auth.0002_alter_permission_name_max_length... OK
zulip_1 | Applying auth.0003_alter_user_email_max_length... OK
zulip_1 | Applying auth.0004_alter_user_username_opts... OK
zulip_1 | Applying auth.0005_alter_user_last_login_null... OK
zulip_1 | Applying auth.0006_require_contenttypes_0002... OK
zulip_1 | Applying confirmation.0001_initial... OK
zulip_1 | Applying zerver.0001_initial... OK
zulip_1 | Applying guardian.0001_initial... OK
zulip_1 | Applying sessions.0001_initial... OK
zulip_1 | Applying sites.0001_initial... OK
zulip_1 | Applying zerver.0002_django_1_8... OK
zulip_1 | Applying zerver.0003_custom_indexes... OK
zulip_1 | Applying zerver.0004_userprofile_left_side_userlist... OK
zulip_1 | Applying zerver.0005_auto_20150920_1340... OK
zulip_1 | Applying zerver.0006_zerver_userprofile_email_upper_idx... OK
zulip_1 | Applying zerver.0007_userprofile_is_bot_active_indexes... OK
zulip_1 | Applying zerver.0008_preregistrationuser_upper_email_idx... OK
zulip_1 | Zulip migration succeeded.
zulip_1 | Post setup scripts execution ...
zulip_1 | No post-setup.d folder found. Continuing.
zulip_1 | === End Bootstrap Phase ===
zulip_1 | === Begin Run Phase ===
zulip_1 | Starting Zulip using supervisor with "/etc/supervisor/supervisord.conf" ...
zulip_1 |
zulip_1 | 2016-04-24 15:16:03,626 CRIT Supervisor running as root (no user in config file)
zulip_1 | 2016-04-24 15:16:03,626 WARN Included extra file "/etc/supervisor/conf.d/zulip_postsetup.conf" during parsing
zulip_1 | 2016-04-24 15:16:03,626 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
zulip_1 | 2016-04-24 15:16:03,626 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
zulip_1 | 2016-04-24 15:16:03,626 WARN Included extra file "/etc/supervisor/conf.d/zulip.conf" during parsing
zulip_1 | 2016-04-24 15:16:03,637 INFO Creating socket unix:///home/zulip/deployments/fastcgi-socket
zulip_1 | 2016-04-24 15:16:03,641 INFO Closing socket unix:///home/zulip/deployments/fastcgi-socket
zulip_1 | 2016-04-24 15:16:03,884 INFO RPC interface 'supervisor' initialized
zulip_1 | 2016-04-24 15:16:03,884 CRIT Server 'unix_http_server' running without any HTTP authentication checking
zulip_1 | 2016-04-24 15:16:03,887 INFO supervisord started with pid 1
zulip_1 | 2016-04-24 15:16:04,889 INFO Creating socket unix:///home/zulip/deployments/fastcgi-socket
zulip_1 | 2016-04-24 15:16:04,898 INFO spawned: 'zulip-django' with pid 98
zulip_1 | 2016-04-24 15:16:04,902 INFO spawned: 'zulip-tornado' with pid 99
zulip_1 | 2016-04-24 15:16:04,905 INFO spawned: 'zulip-postsetup-create_user' with pid 100
zulip_1 | 2016-04-24 15:16:04,913 INFO spawned: 'cron' with pid 101
zulip_1 | 2016-04-24 15:16:04,916 INFO spawned: 'nginx' with pid 102
zulip_1 | 2016-04-24 15:16:04,920 INFO spawned: 'zulip-events-message_sender-4' with pid 103
zulip_1 | 2016-04-24 15:16:04,922 INFO spawned: 'zulip-events-message_sender-0' with pid 104
zulip_1 | 2016-04-24 15:16:04,923 INFO spawned: 'zulip-events-message_sender-1' with pid 105
zulip_1 | 2016-04-24 15:16:04,924 INFO spawned: 'zulip-events-message_sender-2' with pid 106
zulip_1 | 2016-04-24 15:16:04,926 INFO spawned: 'zulip-events-message_sender-3' with pid 107
zulip_1 | 2016-04-24 15:16:04,930 INFO spawned: 'zulip-events-error_reports' with pid 108
zulip_1 | 2016-04-24 15:16:04,946 INFO spawned: 'zulip-events-user-presence' with pid 109
zulip_1 | 2016-04-24 15:16:04,968 INFO spawned: 'zulip-deliver-enqueued-emails' with pid 110
zulip_1 | 2016-04-24 15:16:04,979 INFO spawned: 'zulip-events-slowqueries' with pid 111
zulip_1 | 2016-04-24 15:16:04,990 INFO spawned: 'zulip-events-email_mirror' with pid 112
zulip_1 | 2016-04-24 15:16:04,995 INFO spawned: 'zulip-events-user-activity-interval' with pid 113
zulip_1 | 2016-04-24 15:16:05,013 INFO spawned: 'zulip-events-confirmation-emails' with pid 114
zulip_1 | 2016-04-24 15:16:05,038 INFO spawned: 'zulip-events-missedmessage_mobile_notifications' with pid 115
zulip_1 | 2016-04-24 15:16:05,041 INFO spawned: 'zulip-events-signups' with pid 116
zulip_1 | 2016-04-24 15:16:05,052 INFO spawned: 'zulip-events-digest_emails' with pid 117
zulip_1 | 2016-04-24 15:16:05,063 INFO spawned: 'zulip-events-missedmessage_reminders' with pid 118
zulip_1 | 2016-04-24 15:16:05,096 INFO spawned: 'zulip-events-user-activity' with pid 119
zulip_1 | 2016-04-24 15:16:05,113 INFO spawned: 'zulip-events-feedback_messages' with pid 120
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-django entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-tornado entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-postsetup-create_user entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-events-message_sender-4 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-events-message_sender-0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-events-message_sender-1 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-events-message_sender-2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-events-message_sender-3 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-events-error_reports entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-events-user-presence entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-deliver-enqueued-emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:05,973 INFO success: zulip-events-slowqueries entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-email_mirror entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-user-activity-interval entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-confirmation-emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-missedmessage_mobile_notifications entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-signups entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-digest_emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-missedmessage_reminders entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-user-activity entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
zulip_1 | 2016-04-24 15:16:06,976 INFO success: zulip-events-feedback_messages entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:14 ===
rabbitmq_1 | accepting AMQP connection <0.304.0> (172.17.0.6:32956 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:14 ===
rabbitmq_1 | accepting AMQP connection <0.328.0> (172.17.0.6:32960 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:14 ===
rabbitmq_1 | accepting AMQP connection <0.325.0> (172.17.0.6:32958 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.351.0> (172.17.0.6:32962 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.373.0> (172.17.0.6:32966 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.376.0> (172.17.0.6:32968 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.370.0> (172.17.0.6:32964 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.391.0> (172.17.0.6:32970 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.418.0> (172.17.0.6:32972 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.429.0> (172.17.0.6:32974 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.435.0> (172.17.0.6:32976 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.441.0> (172.17.0.6:32978 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.445.0> (172.17.0.6:32980 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.448.0> (172.17.0.6:32982 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.451.0> (172.17.0.6:32984 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.454.0> (172.17.0.6:32986 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.498.0> (172.17.0.6:32988 -> 172.17.0.4:5672)
rabbitmq_1 |
rabbitmq_1 | =INFO REPORT==== 24-Apr-2016::15:16:15 ===
rabbitmq_1 | accepting AMQP connection <0.525.0> (172.17.0.6:32990 -> 172.17.0.4:5672)
zulip_1 | 2016-04-24 15:16:16,140 INFO exited: zulip-postsetup-create_user (exit status 0; expected)
@metamorphious Thanks for the log output!
Do you know how to enter the container (docker exec ...
)?
If so, you can enter the container and run a cat /var/log/zulip/*
and post the output.
You can also when you enter the container, run su -c "/opt/createZulipAdmin.sh" zulip
and see if the script succeeds. The /opt/createZulipAdmin.sh
script inside the container should create an admin user with the given login details.
The problem is I can't reproduce the problem, that the script is not creating the user with the login details. But as I said try running the command above (su -c "/opt/createZulipAdmin.sh" zulip
) to create an new admin user.
cat /var/log/zulip/*
creates way too much output. I looked into error.log but it is empty.
The script creates following output:
su -c "/opt/createZulipAdmin.sh" zulip /opt/createZulipAdmin.sh: line 9: cannot create temp file for here-document: Operation not permitted
Can you try running /opt/createZulipAdmin.sh
without the su
arround it?
/opt# ./createZulipAdmin.sh zulip
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
Type "copyright", "credits" or "license" for more information.
IPython 1.2.1 -- An enhanced Interactive Python.
? -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help -> Python's own help system.
object? -> Details about 'object', use 'object??' for extra details.
In [1]:
In [2]:
In [3]:
In [4]:
In [5]:
In [6]:
In [6]: ...: ...: ...: ...:
In [7]: ...: ...: ...: ...:
In [8]: ---------------------------------------------------------------------------
DoesNotExist Traceback (most recent call last)
<ipython-input-8-df6328a9037a> in <module>()
----> 1 User = get_user_profile_by_email(email='tester@my-domain.com')
/home/zulip/deployments/2016-04-24-13-25-13/zerver/lib/cache.pyc in func_with_caching(*args, **kwargs)
111 return val[0]
112
--> 113 val = func(*args, **kwargs)
114
115 cache_set(key, val, cache_name=cache_name, timeout=timeout)
/home/zulip/deployments/2016-04-24-13-25-13/zerver/models.pyc in get_user_profile_by_email(email)
1071 @cache_with_key(user_profile_by_email_cache_key, timeout=3600*24*7)
1072 def get_user_profile_by_email(email):
-> 1073 return UserProfile.objects.select_related().get(email__iexact=email.strip())
1074
1075 @cache_with_key(active_user_dicts_in_realm_cache_key, timeout=3600*24*7)
/usr/lib/python2.7/dist-packages/django/db/models/query.pyc in get(self, *args, **kwargs)
332 raise self.model.DoesNotExist(
333 "%s matching query does not exist." %
--> 334 self.model._meta.object_name
335 )
336 raise self.model.MultipleObjectsReturned(
DoesNotExist: UserProfile matching query does not exist.
In [9]: ---------------------------------------------------------------------------
NameError Traceback (most recent call last)
<ipython-input-9-a290169f9270> in <module>()
----> 1 do_change_is_admin(User, True, 'administer')
NameError: name 'User' is not defined
In [10]: ---------------------------------------------------------------------------
NameError Traceback (most recent call last)
<ipython-input-10-846f33f6f2cc> in <module>()
----> 1 User.save()
NameError: name 'User' is not defined
@metamorphious Thanks for the logs! I'm sorry to tell you, but I can't really reproduce this problem.
You can try to create an user and or realm with the manage.py
command from zulip.
su - zulip
# And then check the help menu of the manage.py, on how to create an user
/home/zulip/deployments/current/manage.py --help
If you need help with the manage.py
command to create an user, please let me know.
Not really a solution for the problem but.. We set up a different machine with an other host OS (now Debian instead of Ubuntu) and everything works fine from the beginning. I have no idea what went wrong on the other machine and I doubt that we will investigate that further. Thanks for your help!
@metamorphious No problem. Good to hear, that you found a solution!
Closing as resolved.
I just had a running container, stopped it for changing some settings. Now I can't get it running again because of the database errors. I already tried to delete all database and zulip data. Even deleted all docker images and pulled again. Have the same errors.
Side question: Do I need your complete git repo or just the docker-compose.yml file?
docker-compose.yml:
Log: