API tools faq
paste
Advertisement
Guest User

log

a guest
Apr 5th, 2017
106
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 31.18 KB | None | 0 0
raw download clone embed print report
  1. database_1 | LOG: database system was shut down at 2017-04-03 09:50:36 UTC
  2. database_1 | LOG: MultiXact member wraparound protections are now enabled
  3. database_1 | LOG: database system is ready to accept connections
  4. database_1 | LOG: autovacuum launcher started
  5. redis_1 | Starting redis-server...
  6. redis_1 | _._
  7. redis_1 | _.-``__ ''-._
  8. redis_1 | _.-`` `. `_. ''-._ Redis 2.8.4 (00000000/0) 64 bit
  9. redis_1 | .-`` .-```. ```\/ _.,_ ''-._
  10. redis_1 | ( ' , .-` | `, ) Running in stand alone mode
  11. redis_1 | |`-._`-...-` __...-.``-._|'` _.-'| Port: 6379
  12. redis_1 | | `-._ `._ / _.-' | PID: 1
  13. redis_1 | `-._ `-._ `-./ _.-' _.-'
  14. redis_1 | |`-._`-._ `-.__.-' _.-'_.-'|
  15. redis_1 | | `-._`-._ _.-'_.-' | http://redis.io
  16. redis_1 | `-._ `-._`-.__.-'_.-' _.-'
  17. redis_1 | |`-._`-._ `-.__.-' _.-'_.-'|
  18. redis_1 | | `-._`-._ _.-'_.-' |
  19. redis_1 | `-._ `-._`-.__.-'_.-' _.-'
  20. redis_1 | `-._ `-.__.-' _.-'
  21. redis_1 | `-._ _.-'
  22. redis_1 | `-.__.-'
  23. redis_1 |
  24. redis_1 | [1] 03 Apr 09:59:08.648 # Server started, Redis version 2.8.4
  25. redis_1 | [1] 03 Apr 09:59:08.648 # 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.
  26. redis_1 | [1] 03 Apr 09:59:08.648 * DB loaded from disk: 0.000 seconds
  27. redis_1 | [1] 03 Apr 09:59:08.648 * The server is now ready to accept connections on port 6379
  28. redis_1 | [1] 03 Apr 09:59:08.648 * The server is now ready to accept connections at /var/run/redis/redis.sock
  29. zulip_1 | === Begin Initial Configuration Phase ===
  30. zulip_1 | Preparing and linking the uploads folder ...
  31. zulip_1 | Prepared and linked the uploads directory.
  32. zulip_1 | Executing nginx configuration ...
  33. zulip_1 | Nginx configuration succeeded.
  34. zulip_1 | Exectuing certificates configuration...
  35. zulip_1 | Certificates configuration succeeded.
  36. zulip_1 | Setting database configuration ...
  37. zulip_1 | Setting key "DATABASES", type "array" in file "/home/zulip/deployments/current/zproject/settings.py".
  38. zulip_1 | Setting key "REMOTE_POSTGRES_HOST", type "string" in file "/etc/zulip/settings.py".
  39. zulip_1 | Setting key "REMOTE_POSTGRES_SSLMODE", type "string" in file "/etc/zulip/settings.py".
  40. zulip_1 | Database configuration succeeded.
  41. zulip_1 | Setting Zulip secrets ...
  42. zulip_1 | Generating Zulip secrets ...
  43. zulip_1 | Generated Camo config file /etc/default/camo
  44. zulip_1 | Generated /etc/zulip/zulip-secrets.conf with auto-generated secrets!
  45. zulip_1 | Secrets generation succeeded.
  46. zulip_1 | Secret found for "rabbitmq_password".
  47. zulip_1 | Secret added for "email_password".
  48. zulip_1 | Secret found for "secret_key".
  49. zulip_1 | Zulip secrets configuration succeeded.
  50. zulip_1 | Activating authentication backends ...
  51. zulip_1 | Setting key "AUTHENTICATION_BACKENDS", type "array" in file "/etc/zulip/settings.py".
  52. zulip_1 | Adding authentication backend "EmailAuthBackend".
  53. zulip_1 | Authentication backend activation succeeded.
  54. zulip_1 | Executing Zulip configuration ...
  55. zulip_1 | Setting key "EXTERNAL_HOST", type "string" in file "/etc/zulip/settings.py".
  56. zulip_1 | Setting key "EMAIL_HOST", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
  57. zulip_1 | Setting key "ALLOWED_HOSTS", type "array" in file "/etc/zulip/settings.py".
  58. zulip_1 | Setting key "NOREPLY_EMAIL_ADDRESS", type "string" in file "/etc/zulip/settings.py".
  59. zulip_1 | Setting key "ZULIP_ADMINISTRATOR", type "string" in file "/etc/zulip/settings.py".
  60. zulip_1 | Setting key "REDIS_HOST", type "string" in file "/etc/zulip/settings.py".
  61. zulip_1 | Setting key "RABBITMQ_HOST", type "string" in file "/etc/zulip/settings.py".
  62. zulip_1 | Setting key "EMAIL_HOST_USER", type "string" in file "/home/zulip/deployments/current/zproject/settings.py".
  63. zulip_1 | Setting key "DEFAULT_FROM_EMAIL", type "string" in file "/etc/zulip/settings.py".
  64. zulip_1 | Setting key "MEMCACHED_LOCATION", type "string" in file "/etc/zulip/settings.py".
  65. zulip_1 | Setting key "EMAIL_USE_SSL", type "bool" in file "/home/zulip/deployments/current/zproject/settings.py".
  66. zulip_1 | Setting key "ADMIN_DOMAIN", type "string" in file "/etc/zulip/settings.py".
  67. zulip_1 | Setting key "EMAIL_USE_TLS", type "bool" in file "/home/zulip/deployments/current/zproject/settings.py".
  68. zulip_1 | Setting key "EMAIL_PORT", type "integer" in file "/home/zulip/deployments/current/zproject/settings.py".
  69. zulip_1 | Zulip configuration succeeded.
  70. zulip_1 | Auto backup enabled.
  71. zulip_1 | === End Initial Configuration Phase ===
  72. zulip_1 | === Begin Bootstrap Phase ===
  73. zulip_1 | Waiting for database server to allow connections ...
  74. zulip_1 | (Re)creating database structure ...
  75. zulip_1 | Setting up the database, schema and user ...
  76. database_1 | ERROR: role "zulip" already exists
  77. database_1 | STATEMENT: CREATE USER zulip;
  78. zulip_1 | ERROR: role "zulip" already exists
  79. zulip_1 | ALTER ROLE
  80. database_1 | ERROR: database "zulip" already exists
  81. database_1 | STATEMENT: CREATE DATABASE zulip OWNER=zulip;
  82. zulip_1 | ERROR: database "zulip" already exists
  83. database_1 | ERROR: schema "zulip" already exists
  84. database_1 | STATEMENT: CREATE SCHEMA zulip AUTHORIZATION zulip;
  85. zulip_1 | ERROR: schema "zulip" already exists
  86. zulip_1 | Creating tsearch_extras extension ...
  87. database_1 | FATAL: password authentication failed for user "postgres"
  88. database_1 | DETAIL: User "postgres" has no password assigned.
  89. database_1 | Connection matched pg_hba.conf line 95: "host all all all md5"
  90. zulip_1 | psql: FATAL: password authentication failed for user "postgres"
  91. zulip_1 | Database structure recreated.
  92. zulip_1 | Bootstrapping RabbitMQ ...
  93. zulip_1 | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
  94. zulip_1 | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_HOST
  95. zulip_1 | + RABBITMQ_HOST=rabbitmq
  96. zulip_1 | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
  97. zulip_1 | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_USERNAME
  98. zulip_1 | + RABBITMQ_USERNAME=zulip
  99. zulip_1 | +++ dirname /root/zulip/scripts/setup/configure-rabbitmq
  100. zulip_1 | ++ /root/zulip/scripts/setup/../get-django-setting RABBITMQ_PASSWORD
  101. rabbitmq_1 |
  102. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:11 ===
  103. rabbitmq_1 | Starting RabbitMQ 3.5.5 on Erlang 18.1
  104. rabbitmq_1 | Copyright (C) 2007-2015 Pivotal Software, Inc.
  105. rabbitmq_1 | Licensed under the MPL. See http://www.rabbitmq.com/
  106. rabbitmq_1 |
  107. rabbitmq_1 | RabbitMQ 3.5.5. Copyright (C) 2007-2015 Pivotal Software, Inc.
  108. rabbitmq_1 | ## ## Licensed under the MPL. See http://www.rabbitmq.com/
  109. rabbitmq_1 | ## ##
  110. rabbitmq_1 | ########## Logs: tty
  111. rabbitmq_1 | ###### ## tty
  112. rabbitmq_1 | ##########
  113. rabbitmq_1 | Starting broker...
  114. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:11 ===
  115. rabbitmq_1 | node : rabbit@zulip-rabbit
  116. rabbitmq_1 | home dir : /var/lib/rabbitmq
  117. rabbitmq_1 | config file(s) : /etc/rabbitmq/rabbitmq.config
  118. rabbitmq_1 | cookie hash : LjhGt+fKyUoSVqAP1IfBNg==
  119. rabbitmq_1 | log : tty
  120. rabbitmq_1 | sasl log : tty
  121. rabbitmq_1 | database dir : /var/lib/rabbitmq/mnesia/rabbit@zulip-rabbit
  122. zulip_1 | + RABBITMQ_PASSWORD=zulip
  123. zulip_1 | + sudo rabbitmqctl -n rabbitmq delete_user zulip
  124. rabbitmq_1 |
  125. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  126. rabbitmq_1 | Memory limit set to 799MB of 1999MB total.
  127. rabbitmq_1 |
  128. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  129. rabbitmq_1 | Disk free limit set to 50MB
  130. rabbitmq_1 |
  131. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  132. rabbitmq_1 | Limiting to approx 1048476 file handles (943626 sockets)
  133. rabbitmq_1 |
  134. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  135. rabbitmq_1 | FHC read buffering: ON
  136. rabbitmq_1 | FHC write buffering: ON
  137. rabbitmq_1 |
  138. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  139. rabbitmq_1 | Priority queues enabled, real BQ is rabbit_variable_queue
  140. rabbitmq_1 |
  141. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  142. rabbitmq_1 | msg_store_transient: using rabbit_msg_store_ets_index to provide index
  143. rabbitmq_1 |
  144. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  145. rabbitmq_1 | msg_store_persistent: using rabbit_msg_store_ets_index to provide index
  146. rabbitmq_1 |
  147. rabbitmq_1 | =WARNING REPORT==== 3-Apr-2017::09:59:12 ===
  148. rabbitmq_1 | msg_store_persistent: rebuilding indices from scratch
  149. rabbitmq_1 |
  150. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  151. rabbitmq_1 | started TCP Listener on [::]:5672
  152. rabbitmq_1 | completed with 0 plugins.
  153. rabbitmq_1 |
  154. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::09:59:12 ===
  155. rabbitmq_1 | Server startup complete; 0 plugins started.
  156. zulip_1 | Error: unable to connect to node rabbitmq@23a33bf5b102: nodedown
  157. zulip_1 |
  158. zulip_1 | DIAGNOSTICS
  159. zulip_1 | ===========
  160. zulip_1 |
  161. zulip_1 | nodes in question: [rabbitmq@23a33bf5b102]
  162. zulip_1 |
  163. zulip_1 | hosts, their running nodes and ports:
  164. zulip_1 | - 23a33bf5b102: [{rabbitmqctl100,41459}]
  165. zulip_1 |
  166. zulip_1 | current node details:
  167. zulip_1 | - node name: rabbitmqctl100@23a33bf5b102
  168. zulip_1 | - home dir: /var/lib/rabbitmq
  169. zulip_1 | - cookie hash: B7AeIMkoq5l6DQ31B6EP/w==
  170. zulip_1 |
  171. zulip_1 | + true
  172. zulip_1 | + sudo rabbitmqctl -n rabbitmq delete_user zulip
  173. zulip_1 | Error: unable to connect to node rabbitmq@23a33bf5b102: nodedown
  174. zulip_1 |
  175. zulip_1 | DIAGNOSTICS
  176. zulip_1 | ===========
  177. zulip_1 |
  178. zulip_1 | nodes in question: [rabbitmq@23a33bf5b102]
  179. zulip_1 |
  180. zulip_1 | hosts, their running nodes and ports:
  181. zulip_1 | - 23a33bf5b102: [{rabbitmqctl145,39141}]
  182. zulip_1 |
  183. zulip_1 | current node details:
  184. zulip_1 | - node name: rabbitmqctl145@23a33bf5b102
  185. zulip_1 | - home dir: /var/lib/rabbitmq
  186. zulip_1 | - cookie hash: B7AeIMkoq5l6DQ31B6EP/w==
  187. zulip_1 |
  188. zulip_1 | + true
  189. zulip_1 | + sudo rabbitmqctl -n rabbitmq delete_user guest
  190. zulip_1 | Error: unable to connect to node rabbitmq@23a33bf5b102: nodedown
  191. zulip_1 |
  192. zulip_1 | DIAGNOSTICS
  193. zulip_1 | ===========
  194. zulip_1 |
  195. zulip_1 | nodes in question: [rabbitmq@23a33bf5b102]
  196. zulip_1 |
  197. zulip_1 | hosts, their running nodes and ports:
  198. zulip_1 | - 23a33bf5b102: [{rabbitmqctl190,36387}]
  199. zulip_1 |
  200. zulip_1 | current node details:
  201. zulip_1 | - node name: rabbitmqctl190@23a33bf5b102
  202. zulip_1 | - home dir: /var/lib/rabbitmq
  203. zulip_1 | - cookie hash: B7AeIMkoq5l6DQ31B6EP/w==
  204. zulip_1 |
  205. zulip_1 | + true
  206. zulip_1 | + sudo rabbitmqctl -n rabbitmq add_user zulip zulip
  207. zulip_1 | Error: unable to connect to node rabbitmq@23a33bf5b102: nodedown
  208. zulip_1 |
  209. zulip_1 | DIAGNOSTICS
  210. zulip_1 | ===========
  211. zulip_1 |
  212. zulip_1 | nodes in question: [rabbitmq@23a33bf5b102]
  213. zulip_1 |
  214. zulip_1 | hosts, their running nodes and ports:
  215. zulip_1 | - 23a33bf5b102: [{rabbitmqctl236,33985}]
  216. zulip_1 |
  217. zulip_1 | current node details:
  218. zulip_1 | - node name: rabbitmqctl236@23a33bf5b102
  219. zulip_1 | - home dir: /var/lib/rabbitmq
  220. zulip_1 | - cookie hash: B7AeIMkoq5l6DQ31B6EP/w==
  221. zulip_1 |
  222. zulip_1 | Deleting user "zulip" ...
  223. zulip_1 | Deleting user "zulip" ...
  224. zulip_1 | Deleting user "guest" ...
  225. zulip_1 | Creating user "zulip" ...
  226. zulip_1 | RabbitMQ bootstrap succeeded.
  227. zulip_1 | Executing Zulip user creation script ...
  228. zulip_1 | Zulip user creation left enabled.
  229. zulip_1 | Executing Zulip first start init ...
  230. zulip_1 | ++ dirname /home/zulip/deployments/current/scripts/setup/initialize-database
  231. zulip_1 | + cd /home/zulip/deployments/current/scripts/setup/../..
  232. zulip_1 | + ./manage.py checkconfig
  233. zulip_1 | + ./manage.py migrate --noinput
  234. zulip_1 | Operations to perform:
  235. zulip_1 | Apply all migrations: analytics, auth, confirmation, contenttypes, guardian, sessions, sites, social_django, zerver
  236. zulip_1 | Running migrations:
  237. zulip_1 | Applying contenttypes.0001_initial... OK
  238. zulip_1 | Applying auth.0001_initial... OK
  239. zulip_1 | Applying zerver.0001_initial... OK
  240. zulip_1 | Applying zerver.0002_django_1_8... OK
  241. zulip_1 | Applying zerver.0003_custom_indexes... OK
  242. zulip_1 | Applying zerver.0004_userprofile_left_side_userlist... OK
  243. zulip_1 | Applying zerver.0005_auto_20150920_1340... OK
  244. zulip_1 | Applying zerver.0006_zerver_userprofile_email_upper_idx... OK
  245. zulip_1 | Applying zerver.0007_userprofile_is_bot_active_indexes... OK
  246. zulip_1 | Applying zerver.0008_preregistrationuser_upper_email_idx... OK
  247. zulip_1 | Applying zerver.0009_add_missing_migrations... OK
  248. zulip_1 | Applying zerver.0010_delete_streamcolor... OK
  249. zulip_1 | Applying zerver.0011_remove_guardian... OK
  250. zulip_1 | Applying zerver.0012_remove_appledevicetoken... OK
  251. zulip_1 | Applying zerver.0013_realmemoji... OK
  252. zulip_1 | Applying zerver.0014_realm_emoji_url_length... OK
  253. zulip_1 | Applying zerver.0015_attachment... OK
  254. zulip_1 | Applying zerver.0016_realm_create_stream_by_admins_only... OK
  255. zulip_1 | Applying zerver.0017_userprofile_bot_type... OK
  256. zulip_1 | Applying zerver.0018_realm_emoji_message... OK
  257. zulip_1 | Applying zerver.0019_preregistrationuser_realm_creation... OK
  258. zulip_1 | Applying zerver.0020_add_tracking_attachment... OK
  259. zulip_1 | Applying zerver.0021_migrate_attachment_data... OK
  260. zulip_1 | Applying zerver.0022_subscription_pin_to_top... OK
  261. zulip_1 | Applying zerver.0023_userprofile_default_language... OK
  262. zulip_1 | Applying zerver.0024_realm_allow_message_editing... OK
  263. zulip_1 | Applying zerver.0025_realm_message_content_edit_limit... OK
  264. zulip_1 | Applying zerver.0026_delete_mituser... OK
  265. zulip_1 | Applying zerver.0027_realm_default_language... OK
  266. zulip_1 | Applying zerver.0028_userprofile_tos_version... OK
  267. zulip_1 | Applying zerver.0029_realm_subdomain... OK
  268. zulip_1 | Applying zerver.0030_realm_org_type... OK
  269. zulip_1 | Applying zerver.0031_remove_system_avatar_source... OK
  270. zulip_1 | Applying zerver.0032_verify_all_medium_avatar_images... OK
  271. zulip_1 | Applying zerver.0033_migrate_domain_to_realmalias... OK
  272. zulip_1 | Applying zerver.0034_userprofile_enable_online_push_notifications... OK
  273. zulip_1 | Applying zerver.0035_realm_message_retention_period_days... OK
  274. zulip_1 | Applying zerver.0036_rename_subdomain_to_string_id... OK
  275. zulip_1 | Applying zerver.0037_disallow_null_string_id... OK
  276. zulip_1 | Applying zerver.0038_realm_change_to_community_defaults... OK
  277. zulip_1 | Applying zerver.0039_realmalias_drop_uniqueness... OK
  278. zulip_1 | Applying zerver.0040_realm_authentication_methods... OK
  279. zulip_1 | Applying zerver.0041_create_attachments_for_old_messages... OK
  280. zulip_1 | Applying zerver.0042_attachment_file_name_length... OK
  281. zulip_1 | Applying zerver.0043_realm_filter_validators... OK
  282. zulip_1 | Applying zerver.0044_reaction... OK
  283. zulip_1 | Applying zerver.0045_realm_waiting_period_threshold... OK
  284. zulip_1 | Applying zerver.0046_realmemoji_author... OK
  285. zulip_1 | Applying zerver.0047_realm_add_emoji_by_admins_only... OK
  286. zulip_1 | Applying zerver.0048_enter_sends_default_to_false... OK
  287. zulip_1 | Applying zerver.0049_userprofile_pm_content_in_desktop_notifications... OK
  288. zulip_1 | Applying zerver.0050_userprofile_avatar_version... OK
  289. zulip_1 | Applying analytics.0001_initial... OK
  290. zulip_1 | Applying analytics.0002_remove_huddlecount... OK
  291. zulip_1 | Applying analytics.0003_fillstate... OK
  292. zulip_1 | Applying analytics.0004_add_subgroup... OK
  293. zulip_1 | Applying analytics.0005_alter_field_size... OK
  294. zulip_1 | Applying analytics.0006_add_subgroup_to_unique_constraints... OK
  295. zulip_1 | Applying analytics.0007_remove_interval... OK
  296. zulip_1 | Applying analytics.0008_add_count_indexes... OK
  297. zulip_1 | Applying contenttypes.0002_remove_content_type_name... OK
  298. zulip_1 | Applying auth.0002_alter_permission_name_max_length... OK
  299. zulip_1 | Applying auth.0003_alter_user_email_max_length... OK
  300. zulip_1 | Applying auth.0004_alter_user_username_opts... OK
  301. zulip_1 | Applying auth.0005_alter_user_last_login_null... OK
  302. zulip_1 | Applying auth.0006_require_contenttypes_0002... OK
  303. zulip_1 | Applying auth.0007_alter_validators_add_error_messages... OK
  304. zulip_1 | Applying auth.0008_alter_user_username_max_length... OK
  305. zulip_1 | Applying confirmation.0001_initial... OK
  306. zulip_1 | Applying confirmation.0002_realmcreationkey... OK
  307. zulip_1 | Applying guardian.0001_initial... OK
  308. zulip_1 | Applying sessions.0001_initial... OK
  309. zulip_1 | Applying sites.0001_initial... OK
  310. zulip_1 | Applying sites.0002_alter_domain_unique... OK
  311. zulip_1 | Applying social_django.0001_initial... OK
  312. zulip_1 | Applying social_django.0002_add_related_name... OK
  313. zulip_1 | Applying social_django.0003_alter_email_max_length... OK
  314. zulip_1 | Applying social_django.0004_auto_20160423_0400... OK
  315. zulip_1 | Applying social_django.0005_auto_20160727_2333... OK
  316. zulip_1 | + ./manage.py createcachetable third_party_api_results
  317. zulip_1 | + ./manage.py initialize_voyager_db
  318. zulip_1 | Successfully populated database with initial data.
  319. zulip_1 | Please run ./manage.py generate_realm_creation_link to generate link for creating organization
  320. zulip_1 | + '[' -e /var/run/supervisor.sock ']'
  321. zulip_1 | + set +x
  322. zulip_1 | Congratulations! You have successfully configured your Zulip database.
  323. zulip_1 | If you haven't already, you should configure email in /etc/zulip/settings.py.
  324. zulip_1 | Then create your organization and user by opening the link to your Zulip
  325. zulip_1 | instance generated by ./manage.py generate_realm_creation_link.
  326. zulip_1 |
  327. zulip_1 | See docs/prod-health-check-debug.md for instructions on how to confirm your Zulip
  328. zulip_1 | install is healthy, change your realm's domain, debug common issues, and otherwise
  329. zulip_1 | finish setting things up.
  330. zulip_1 | Zulip first start init sucessful.
  331. zulip_1 | Migrating Zulip to new version ...
  332. zulip_1 | Operations to perform:
  333. zulip_1 | Apply all migrations: analytics, auth, confirmation, contenttypes, guardian, sessions, sites, social_django, zerver
  334. zulip_1 | Running migrations:
  335. zulip_1 | No migrations to apply.
  336. zulip_1 | Zulip migration succeeded.
  337. zulip_1 | Post setup scripts execution ...
  338. zulip_1 | No post-setup.d folder found. Continuing.
  339. zulip_1 | === End Bootstrap Phase ===
  340. zulip_1 | === Begin Run Phase ===
  341. zulip_1 | Starting Zulip using supervisor with "/etc/supervisor/supervisord.conf" config ...
  342. zulip_1 |
  343. zulip_1 | 2017-04-03 09:59:39,956 CRIT Supervisor running as root (no user in config file)
  344. zulip_1 | 2017-04-03 09:59:39,957 WARN Included extra file "/etc/supervisor/conf.d/cron.conf" during parsing
  345. zulip_1 | 2017-04-03 09:59:39,957 WARN Included extra file "/etc/supervisor/conf.d/nginx.conf" during parsing
  346. zulip_1 | 2017-04-03 09:59:39,957 WARN Included extra file "/etc/supervisor/conf.d/zulip.conf" during parsing
  347. zulip_1 | 2017-04-03 09:59:39,957 WARN Included extra file "/etc/supervisor/conf.d/zulip_db.conf" during parsing
  348. zulip_1 | 2017-04-03 09:59:39,957 WARN Included extra file "/etc/supervisor/conf.d/zulip_postsetup.conf" during parsing
  349. zulip_1 | 2017-04-03 09:59:39,996 INFO RPC interface 'supervisor' initialized
  350. zulip_1 | 2017-04-03 09:59:39,996 CRIT Server 'unix_http_server' running without any HTTP authentication checking
  351. zulip_1 | 2017-04-03 09:59:39,997 INFO supervisord started with pid 1
  352. zulip_1 | 2017-04-03 09:59:41,000 INFO spawned: 'zulip-django' with pid 312
  353. zulip_1 | 2017-04-03 09:59:41,003 INFO spawned: 'zulip-tornado' with pid 313
  354. zulip_1 | 2017-04-03 09:59:41,005 INFO spawned: 'process-fts-updates' with pid 314
  355. zulip_1 | 2017-04-03 09:59:41,007 INFO spawned: 'zulip-events-message_sender-4' with pid 315
  356. zulip_1 | 2017-04-03 09:59:41,010 INFO spawned: 'zulip-events-message_sender-0' with pid 316
  357. zulip_1 | 2017-04-03 09:59:41,014 INFO spawned: 'zulip-events-message_sender-1' with pid 317
  358. zulip_1 | 2017-04-03 09:59:41,017 INFO spawned: 'zulip-events-message_sender-2' with pid 318
  359. zulip_1 | 2017-04-03 09:59:41,022 INFO spawned: 'zulip-events-message_sender-3' with pid 319
  360. zulip_1 | 2017-04-03 09:59:41,036 INFO spawned: 'cron' with pid 320
  361. zulip_1 | 2017-04-03 09:59:41,038 INFO spawned: 'nginx' with pid 321
  362. zulip_1 | 2017-04-03 09:59:41,060 INFO spawned: 'zulip-postsetup-create_user' with pid 322
  363. zulip_1 | 2017-04-03 09:59:41,061 INFO spawned: 'zulip-events-error_reports' with pid 323
  364. zulip_1 | 2017-04-03 09:59:41,088 INFO spawned: 'zulip-events-user-presence' with pid 324
  365. zulip_1 | 2017-04-03 09:59:41,090 INFO spawned: 'zulip-deliver-enqueued-emails' with pid 325
  366. zulip_1 | 2017-04-03 09:59:41,108 INFO spawned: 'zulip-events-slowqueries' with pid 326
  367. zulip_1 | 2017-04-03 09:59:41,125 INFO spawned: 'zulip-events-email_mirror' with pid 327
  368. zulip_1 | 2017-04-03 09:59:41,163 INFO spawned: 'zulip-events-user-activity-interval' with pid 328
  369. zulip_1 | 2017-04-03 09:59:41,172 INFO spawned: 'zulip-events-confirmation-emails' with pid 329
  370. zulip_1 | 2017-04-03 09:59:41,215 INFO spawned: 'zulip-events-missedmessage_mobile_notifications' with pid 330
  371. zulip_1 | 2017-04-03 09:59:41,232 INFO spawned: 'zulip-events-signups' with pid 331
  372. zulip_1 | 2017-04-03 09:59:41,271 INFO spawned: 'zulip-events-digest_emails' with pid 332
  373. zulip_1 | 2017-04-03 09:59:41,311 INFO spawned: 'zulip-events-embed_links' with pid 333
  374. zulip_1 | 2017-04-03 09:59:41,367 INFO spawned: 'zulip-events-missedmessage_reminders' with pid 334
  375. zulip_1 | 2017-04-03 09:59:41,388 INFO spawned: 'zulip-events-user-activity' with pid 335
  376. zulip_1 | 2017-04-03 09:59:41,406 INFO spawned: 'zulip-events-feedback_messages' with pid 336
  377. zulip_1 | 2017-04-03 09:59:42,460 INFO success: zulip-django entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  378. zulip_1 | 2017-04-03 09:59:42,461 INFO success: zulip-tornado entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  379. zulip_1 | 2017-04-03 09:59:42,461 INFO success: process-fts-updates entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  380. zulip_1 | 2017-04-03 09:59:42,461 INFO success: zulip-events-message_sender-4 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  381. zulip_1 | 2017-04-03 09:59:42,461 INFO success: zulip-events-message_sender-0 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  382. zulip_1 | 2017-04-03 09:59:42,462 INFO success: zulip-events-message_sender-1 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  383. zulip_1 | 2017-04-03 09:59:42,462 INFO success: zulip-events-message_sender-2 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  384. zulip_1 | 2017-04-03 09:59:42,462 INFO success: zulip-events-message_sender-3 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  385. zulip_1 | 2017-04-03 09:59:42,462 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  386. zulip_1 | 2017-04-03 09:59:42,462 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  387. zulip_1 | 2017-04-03 09:59:42,463 INFO success: zulip-postsetup-create_user entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  388. zulip_1 | 2017-04-03 09:59:42,463 INFO success: zulip-events-error_reports entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  389. zulip_1 | 2017-04-03 09:59:42,463 INFO success: zulip-events-user-presence entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  390. zulip_1 | 2017-04-03 09:59:42,464 INFO success: zulip-deliver-enqueued-emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  391. zulip_1 | 2017-04-03 09:59:42,464 INFO success: zulip-events-slowqueries entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  392. zulip_1 | 2017-04-03 09:59:42,464 INFO success: zulip-events-email_mirror entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  393. zulip_1 | 2017-04-03 09:59:42,465 INFO success: zulip-events-user-activity-interval entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  394. zulip_1 | 2017-04-03 09:59:42,465 INFO success: zulip-events-confirmation-emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  395. zulip_1 | 2017-04-03 09:59:42,466 INFO success: zulip-events-missedmessage_mobile_notifications entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  396. zulip_1 | 2017-04-03 09:59:42,466 INFO success: zulip-events-signups entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  397. zulip_1 | 2017-04-03 09:59:42,466 INFO success: zulip-events-digest_emails entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  398. zulip_1 | 2017-04-03 09:59:42,467 INFO success: zulip-events-embed_links entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  399. zulip_1 | 2017-04-03 09:59:42,467 INFO success: zulip-events-missedmessage_reminders entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  400. zulip_1 | 2017-04-03 09:59:42,467 INFO success: zulip-events-user-activity entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  401. zulip_1 | 2017-04-03 09:59:42,468 INFO success: zulip-events-feedback_messages entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
  402. rabbitmq_1 |
  403. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:11 ===
  404. rabbitmq_1 | accepting AMQP connection <0.218.0> (172.20.0.6:36458 -> 172.20.0.2:5672)
  405. rabbitmq_1 |
  406. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:14 ===
  407. rabbitmq_1 | accepting AMQP connection <0.238.0> (172.20.0.6:36460 -> 172.20.0.2:5672)
  408. rabbitmq_1 |
  409. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:14 ===
  410. rabbitmq_1 | accepting AMQP connection <0.251.0> (172.20.0.6:36462 -> 172.20.0.2:5672)
  411. rabbitmq_1 |
  412. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:15 ===
  413. rabbitmq_1 | accepting AMQP connection <0.264.0> (172.20.0.6:36464 -> 172.20.0.2:5672)
  414. rabbitmq_1 |
  415. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:16 ===
  416. rabbitmq_1 | accepting AMQP connection <0.277.0> (172.20.0.6:36466 -> 172.20.0.2:5672)
  417. rabbitmq_1 |
  418. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:16 ===
  419. rabbitmq_1 | accepting AMQP connection <0.290.0> (172.20.0.6:36468 -> 172.20.0.2:5672)
  420. rabbitmq_1 |
  421. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  422. rabbitmq_1 | accepting AMQP connection <0.303.0> (172.20.0.6:36474 -> 172.20.0.2:5672)
  423. rabbitmq_1 |
  424. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  425. rabbitmq_1 | accepting AMQP connection <0.316.0> (172.20.0.6:36476 -> 172.20.0.2:5672)
  426. rabbitmq_1 |
  427. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  428. rabbitmq_1 | accepting AMQP connection <0.329.0> (172.20.0.6:36478 -> 172.20.0.2:5672)
  429. rabbitmq_1 |
  430. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  431. rabbitmq_1 | accepting AMQP connection <0.342.0> (172.20.0.6:36480 -> 172.20.0.2:5672)
  432. rabbitmq_1 |
  433. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  434. rabbitmq_1 | accepting AMQP connection <0.351.0> (172.20.0.6:36484 -> 172.20.0.2:5672)
  435. rabbitmq_1 |
  436. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  437. rabbitmq_1 | accepting AMQP connection <0.364.0> (172.20.0.6:36488 -> 172.20.0.2:5672)
  438. rabbitmq_1 |
  439. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  440. rabbitmq_1 | accepting AMQP connection <0.367.0> (172.20.0.6:36490 -> 172.20.0.2:5672)
  441. rabbitmq_1 |
  442. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  443. rabbitmq_1 | accepting AMQP connection <0.370.0> (172.20.0.6:36492 -> 172.20.0.2:5672)
  444. rabbitmq_1 |
  445. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  446. rabbitmq_1 | accepting AMQP connection <0.399.0> (172.20.0.6:36494 -> 172.20.0.2:5672)
  447. rabbitmq_1 |
  448. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:17 ===
  449. rabbitmq_1 | accepting AMQP connection <0.408.0> (172.20.0.6:36496 -> 172.20.0.2:5672)
  450. rabbitmq_1 |
  451. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:18 ===
  452. rabbitmq_1 | accepting AMQP connection <0.417.0> (172.20.0.6:36498 -> 172.20.0.2:5672)
  453. rabbitmq_1 |
  454. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:18 ===
  455. rabbitmq_1 | accepting AMQP connection <0.430.0> (172.20.0.6:36500 -> 172.20.0.2:5672)
  456. rabbitmq_1 |
  457. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:18 ===
  458. rabbitmq_1 | accepting AMQP connection <0.435.0> (172.20.0.6:36502 -> 172.20.0.2:5672)
  459. rabbitmq_1 |
  460. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:18 ===
  461. rabbitmq_1 | accepting AMQP connection <0.441.0> (172.20.0.6:36504 -> 172.20.0.2:5672)
  462. rabbitmq_1 |
  463. rabbitmq_1 | =WARNING REPORT==== 3-Apr-2017::10:00:19 ===
  464. rabbitmq_1 | closing AMQP connection <0.408.0> (172.20.0.6:36496 -> 172.20.0.2:5672):
  465. rabbitmq_1 | connection_closed_abruptly
  466. rabbitmq_1 |
  467. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:26 ===
  468. rabbitmq_1 | accepting AMQP connection <0.466.0> (172.20.0.6:36512 -> 172.20.0.2:5672)
  469. rabbitmq_1 |
  470. rabbitmq_1 | =WARNING REPORT==== 3-Apr-2017::10:00:26 ===
  471. rabbitmq_1 | closing AMQP connection <0.466.0> (172.20.0.6:36512 -> 172.20.0.2:5672):
  472. rabbitmq_1 | connection_closed_abruptly
  473. zulip_1 | 2017-04-03 10:00:35,098 INFO reaped unknown pid 489
  474. rabbitmq_1 |
  475. rabbitmq_1 | =INFO REPORT==== 3-Apr-2017::10:00:38 ===
  476. rabbitmq_1 | accepting AMQP connection <0.476.0> (172.20.0.6:36526 -> 172.20.0.2:5672)
  477. rabbitmq_1 |
  478. rabbitmq_1 | =WARNING REPORT==== 3-Apr-2017::10:00:38 ===
  479. rabbitmq_1 | closing AMQP connection <0.476.0> (172.20.0.6:36526 -> 172.20.0.2:5672):
  480. rabbitmq_1 | connection_closed_abruptly
  481. zulip_1 | 2017-04-03 10:00:38,729 INFO exited: zulip-postsetup-create_user (exit status 0; expected)
  482. ^CGracefully stopping... (press Ctrl+C again to force)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!