· 9 years ago · Apr 05, 2017, 08:16 AM
1zulip_1 | === Begin Initial Configuration Phase ===
2zulip_1 | Preparing and linking the uploads folder ...
3zulip_1 | Prepared and linked the uploads directory.
4zulip_1 | Executing nginx configuration ...
5zulip_1 | Nginx configuration succeeded.
6zulip_1 | Exectuing certificates configuration...
7zulip_1 | Certificates configuration succeeded.
8zulip_1 | Setting database configuration ...
9zulip_1 | Setting key "DATABASES", type "array" in file "/home/zulip/deployments/current/zproject/settings.py".
10zulip_1 | Setting key "REMOTE_POSTGRES_HOST", type "string" in file "/etc/zulip/settings.py".
11zulip_1 | Setting key "REMOTE_POSTGRES_SSLMODE", type "string" in file "/etc/zulip/settings.py".
12zulip_1 | Database configuration succeeded.
13zulip_1 | Setting Zulip secrets ...
14zulip_1 | Generating Zulip secrets ...
15zulip_1 | Generated Camo config file /etc/default/camo
16zulip_1 | Generated /etc/zulip/zulip-secrets.conf with auto-generated secrets!
17zulip_1 | Secrets generation succeeded.
18zulip_1 | Secret found for "rabbitmq_password".
19zulip_1 | Secret added for "email_password".
20zulip_1 | Secret found for "secret_key".
21zulip_1 | Zulip secrets configuration succeeded.
22zulip_1 | Activating authentication backends ...
23zulip_1 | Setting key "AUTHENTICATION_BACKENDS", type "array" in file "/etc/zulip/settings.py".
24zulip_1 | Adding authentication backend "EmailAuthBackend".
25zulip_1 | Authentication backend activation succeeded.
26zulip_1 | Executing Zulip configuration ...
27zulip_1 | Setting key "EXTERNAL_HOST", type "string" in file "/etc/zulip/settings.py".
28zulip_1 | Setting key "EMAIL_HOST", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
29zulip_1 | Setting key "ALLOWED_HOSTS", type "array" in file "/etc/zulip/settings.py".
30zulip_1 | Setting key "NOREPLY_EMAIL_ADDRESS", type "string" in file "/etc/zulip/settings.py".
31zulip_1 | Setting key "ZULIP_ADMINISTRATOR", type "string" in file "/etc/zulip/settings.py".
32zulip_1 | Setting key "REDIS_HOST", type "string" in file "/etc/zulip/settings.py".
33zulip_1 | Setting key "RABBITMQ_HOST", type "string" in file "/etc/zulip/settings.py".
34zulip_1 | Setting key "EMAIL_HOST_USER", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
35zulip_1 | Setting key "DEFAULT_FROM_EMAIL", type "string" in file "/etc/zulip/settings.py".
36zulip_1 | Setting key "MEMCACHED_LOCATION", type "string" in file "/etc/zulip/settings.py".
37zulip_1 | Setting key "EMAIL_USE_SSL", type "bool" in file "/home/zulip/deployments/current/zproject/settings.py".
38zulip_1 | Setting key "ADMIN_DOMAIN", type "string" in file "/etc/zulip/settings.py".
39zulip_1 | Setting key "EMAIL_USE_TLS", type "bool" in file "/home/zulip/deployments/current/zproject/settings.py".
40zulip_1 | Setting key "EMAIL_PORT", type "integer" in file "/home/zulip/deployments/current/zproject/settings.py".
41database_1 | LOG: database system was shut down at 2017-04-05 08:06:50 UTC
42database_1 | LOG: MultiXact member wraparound protections are now enabled
43database_1 | LOG: database system is ready to accept connections
44database_1 | LOG: autovacuum launcher started
45redis_1 | Starting redis-server...
46redis_1 | _._
47redis_1 | _.-``__ ''-._
48redis_1 | _.-`` `. `_. ''-._ Redis 2.8.4 (00000000/0) 64 bit
49redis_1 | .-`` .-```. ```\/ _.,_ ''-._
50redis_1 | ( ' , .-` | `, ) Running in stand alone mode
51redis_1 | |`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
52redis_1 | | `-._ `._ / _.-' | PID: 1
53redis_1 | `-._ `-._ `-./ _.-' _.-'
54redis_1 | |`-._`-._ `-.__.-' _.-'_.-'|
55redis_1 | | `-._`-._ _.-'_.-' | http://redis.io
56redis_1 | `-._ `-._`-.__.-'_.-' _.-'
57redis_1 | |`-._`-._ `-.__.-' _.-'_.-'|
58redis_1 | | `-._`-._ _.-'_.-' |
59redis_1 | `-._ `-._`-.__.-'_.-' _.-'
60redis_1 | `-._ `-.__.-' _.-'
61redis_1 | `-._ _.-'
62redis_1 | `-.__.-'
63redis_1 |
64redis_1 | [1] 05 Apr 08:07:20.807 # Server started, Redis version 2.8.4
65redis_1 | [1] 05 Apr 08:07:20.808 # 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.
66redis_1 | [1] 05 Apr 08:07:20.808 * DB loaded from disk: 0.000 seconds
67redis_1 | [1] 05 Apr 08:07:20.808 * The server is now ready to accept connections on port 6379
68redis_1 | [1] 05 Apr 08:07:20.808 * The server is now ready to accept connections at /var/run/redis/redis.sock
69rabbitmq_1 |
70rabbitmq_1 | RabbitMQ 3.5.5. Copyright (C) 2007-2015 Pivotal Software, Inc.
71rabbitmq_1 | ## ## Licensed under the MPL. See http://www.rabbitmq.com/
72rabbitmq_1 | ## ##
73rabbitmq_1 | ########## Logs: tty
74rabbitmq_1 | ###### ## tty
75rabbitmq_1 | ##########
76rabbitmq_1 | Starting broker...
77rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
78rabbitmq_1 | Starting RabbitMQ 3.5.5 on Erlang 18.1
79rabbitmq_1 | Copyright (C) 2007-2015 Pivotal Software, Inc.
80rabbitmq_1 | Licensed under the MPL. See http://www.rabbitmq.com/
81rabbitmq_1 |
82rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
83rabbitmq_1 | node : rabbit@zulip-rabbit
84rabbitmq_1 | home dir : /var/lib/rabbitmq
85rabbitmq_1 | config file(s) : /etc/rabbitmq/rabbitmq.config
86rabbitmq_1 | cookie hash : LjhGt+fKyUoSVqAP1IfBNg==
87rabbitmq_1 | log : tty
88rabbitmq_1 | sasl log : tty
89rabbitmq_1 | database dir : /var/lib/rabbitmq/mnesia/rabbit@zulip-rabbit
90rabbitmq_1 |
91rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
92rabbitmq_1 | Memory limit set to 799MB of 1999MB total.
93rabbitmq_1 |
94rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
95rabbitmq_1 | Disk free limit set to 50MB
96rabbitmq_1 |
97rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
98rabbitmq_1 | Limiting to approx 1048476 file handles (943626 sockets)
99rabbitmq_1 |
100rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
101rabbitmq_1 | FHC read buffering: ON
102rabbitmq_1 | FHC write buffering: ON
103rabbitmq_1 |
104rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
105rabbitmq_1 | Priority queues enabled, real BQ is rabbit_variable_queue
106rabbitmq_1 |
107rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
108rabbitmq_1 | msg_store_transient: using rabbit_msg_store_ets_index to provide index
109rabbitmq_1 |
110rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
111rabbitmq_1 | msg_store_persistent: using rabbit_msg_store_ets_index to provide index
112rabbitmq_1 |
113rabbitmq_1 | =WARNING REPORT==== 5-Apr-2017::08:07:22 ===
114rabbitmq_1 | msg_store_persistent: rebuilding indices from scratch
115rabbitmq_1 |
116rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
117rabbitmq_1 | started TCP Listener on [::]:5672
118rabbitmq_1 | completed with 0 plugins.
119rabbitmq_1 |
120rabbitmq_1 | =INFO REPORT==== 5-Apr-2017::08:07:22 ===
121rabbitmq_1 | Server startup complete; 0 plugins started.
122zulip_1 | Zulip configuration succeeded.
123zulip_1 | Auto backup enabled.
124zulip_1 | === End Initial Configuration Phase ===
125zulip_1 | === Begin Bootstrap Phase ===
126zulip_1 | Waiting for database server to allow connections ...
127database_1 | FATAL: database "zulip" does not exist
128zulip_1 | (Re)creating database structure ...
129zulip_1 | Setting up the database, schema and user ...
130database_1 | FATAL: database "zulip" does not exist
131zulip_1 | Creating tsearch_extras extension ...
132zulip_1 | psql: FATAL: database "zulip" does not exist
133database_1 | FATAL: password authentication failed for user "postgres"
134database_1 | DETAIL: User "postgres" has no password assigned.
135database_1 | Connection matched pg_hba.conf line 95: "host all all all md5"
136zulip_1 | Database structure recreated.
137zulip_1 | Bootstrapping RabbitMQ ...
138zulip_1 | psql: FATAL: password authentication failed for user "postgres"
139zulip_1 | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
140zulip_1 | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_HOST
141zulip_1 | + RABBITMQ_HOST=rabbitmq
142zulip_1 | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
143zulip_1 | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_USERNAME
144zulip_1 | + RABBITMQ_USERNAME=zulip
145zulip_1 | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
146zulip_1 | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_PASSWORD
147zulip_1 | + RABBITMQ_PASSWORD=zulip
148zulip_1 | + sudo rabbitmqctl -n rabbitmq delete_user zulip
149zulip_1 | Error: unable to connect to node rabbitmq@162a28b23025: nodedown
150zulip_1 |
151zulip_1 | DIAGNOSTICS
152zulip_1 | ===========
153zulip_1 |
154zulip_1 | nodes in question: [rabbitmq@162a28b23025]
155zulip_1 |
156zulip_1 | hosts, their running nodes and ports:
157zulip_1 | - 162a28b23025: [{rabbitmqctl100,36053}]
158zulip_1 |
159zulip_1 | current node details:
160zulip_1 | - node name: rabbitmqctl100@162a28b23025
161zulip_1 | - home dir: /var/lib/rabbitmq
162zulip_1 | - cookie hash: 4j076LuBG3ByXuH1ubvmcQ==
163zulip_1 |
164zulip_1 | + true
165zulip_1 | + sudo rabbitmqctl -n rabbitmq delete_user zulip
166zulip_1 | Error: unable to connect to node rabbitmq@162a28b23025: nodedown
167zulip_1 |
168zulip_1 | DIAGNOSTICS
169zulip_1 | ===========
170zulip_1 |
171zulip_1 | nodes in question: [rabbitmq@162a28b23025]
172zulip_1 |
173zulip_1 | hosts, their running nodes and ports:
174zulip_1 | - 162a28b23025: [{rabbitmqctl145,33465}]
175zulip_1 |
176zulip_1 | current node details:
177zulip_1 | - node name: rabbitmqctl145@162a28b23025
178zulip_1 | - home dir: /var/lib/rabbitmq
179zulip_1 | - cookie hash: 4j076LuBG3ByXuH1ubvmcQ==
180zulip_1 |
181zulip_1 | + true
182zulip_1 | + sudo rabbitmqctl -n rabbitmq delete_user guest
183zulip_1 | Error: unable to connect to node rabbitmq@162a28b23025: nodedown
184zulip_1 |
185zulip_1 | DIAGNOSTICS
186zulip_1 | ===========
187zulip_1 |
188zulip_1 | nodes in question: [rabbitmq@162a28b23025]
189zulip_1 |
190zulip_1 | hosts, their running nodes and ports:
191zulip_1 | - 162a28b23025: [{rabbitmqctl190,33101}]
192zulip_1 |
193zulip_1 | current node details:
194zulip_1 | - node name: rabbitmqctl190@162a28b23025
195zulip_1 | - home dir: /var/lib/rabbitmq
196zulip_1 | - cookie hash: 4j076LuBG3ByXuH1ubvmcQ==
197zulip_1 |
198zulip_1 | + true
199zulip_1 | + sudo rabbitmqctl -n rabbitmq add_user zulip zulip
200zulip_1 | Error: unable to connect to node rabbitmq@162a28b23025: nodedown
201zulip_1 |
202zulip_1 | DIAGNOSTICS
203zulip_1 | ===========
204zulip_1 |
205zulip_1 | nodes in question: [rabbitmq@162a28b23025]
206zulip_1 |
207zulip_1 | hosts, their running nodes and ports:
208zulip_1 | - 162a28b23025: [{rabbitmqctl236,46057}]
209zulip_1 |
210zulip_1 | current node details:
211zulip_1 | - node name: rabbitmqctl236@162a28b23025
212zulip_1 | - home dir: /var/lib/rabbitmq
213zulip_1 | - cookie hash: 4j076LuBG3ByXuH1ubvmcQ==
214zulip_1 |
215zulip_1 | Deleting user "zulip" ...
216zulip_1 | Deleting user "zulip" ...
217zulip_1 | Deleting user "guest" ...
218zulip_1 | Creating user "zulip" ...
219zulip_1 | RabbitMQ bootstrap succeeded.
220zulip_1 | Executing Zulip user creation script ...
221zulip_1 | Zulip user creation left enabled.
222zulip_1 | Executing Zulip first start init ...
223zulip_1 | ++ dirname /home/zulip/deployments/current/scripts/setup/initialize-database
224zulip_1 | + cd /home/zulip/deployments/current/scripts/setup/../..
225zulip_1 | + ./manage.py checkconfig
226zulip_1 | + ./manage.py migrate --noinput
227database_1 | FATAL: database "zulip" does not exist
228zulip_1 | Traceback (most recent call last):
229zulip_1 | File "./manage.py", line 29, in <module>
230zulip_1 | execute_from_command_line(sys.argv)
231zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 367, in execute_from_command_line
232zulip_1 | utility.execute()
233zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/core/management/__init__.py", line 359, in execute
234zulip_1 | self.fetch_command(subcommand).run_from_argv(self.argv)
235zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/core/management/base.py", line 294, in run_from_argv
236zulip_1 | self.execute(*args, **cmd_options)
237zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/core/management/base.py", line 345, in execute
238zulip_1 | output = self.handle(*args, **options)
239zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 83, in handle
240zulip_1 | executor = MigrationExecutor(connection, self.migration_progress_callback)
241zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/migrations/executor.py", line 20, in __init__
242zulip_1 | self.loader = MigrationLoader(self.connection)
243zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/migrations/loader.py", line 52, in __init__
244zulip_1 | self.build_graph()
245zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/migrations/loader.py", line 203, in build_graph
246zulip_1 | self.applied_migrations = recorder.applied_migrations()
247zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/migrations/recorder.py", line 65, in applied_migrations
248zulip_1 | self.ensure_schema()
249zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/migrations/recorder.py", line 52, in ensure_schema
250zulip_1 | if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
251zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/backends/base/base.py", line 233, in cursor
252zulip_1 | cursor = self.make_cursor(self._cursor())
253zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/backends/base/base.py", line 204, in _cursor
254zulip_1 | self.ensure_connection()
255zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
256zulip_1 | self.connect()
257zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/utils.py", line 94, in __exit__
258zulip_1 | six.reraise(dj_exc_type, dj_exc_value, traceback)
259zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/backends/base/base.py", line 199, in ensure_connection
260zulip_1 | self.connect()
261zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/backends/base/base.py", line 171, in connect
262zulip_1 | self.connection = self.get_new_connection(conn_params)
263zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/django/db/backends/postgresql/base.py", line 176, in get_new_connection
264zulip_1 | connection = Database.connect(**conn_params)
265zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zulip-venv/lib/python2.7/site-packages/psycopg2/__init__.py", line 164, in connect
266zulip_1 | conn = _connect(dsn, connection_factory=connection_factory, async=async)
267zulip_1 | File "/home/zulip/deployments/2017-03-31-21-32-48/zerver/lib/db.py", line 44, in __init__
268zulip_1 | super(TimeTrackingConnection, self).__init__(*args, **kwargs)
269zulip_1 | django.db.utils.OperationalError: FATAL: database "zulip" does not exist
270zulip_1 |
271zulip_1 | Zulip first start database initi failed in "initialize-database" exit code 1. Exiting.