You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2019/03/11 19:15:54 UTC
[GitHub] [incubator-superset] trmanish commented on issue #6887:
docker-compose up fails with "superset_superset_1 exited with code 243"
trmanish commented on issue #6887: docker-compose up fails with "superset_superset_1 exited with code 243"
URL: https://github.com/apache/incubator-superset/issues/6887#issuecomment-471682096
Hi @ButeForce I tried ur suggestion and this time on doing
docker-compose up didn't throw the 243 error. And shows everything running.
```
nf _NPROCESSORS_ONLN
superset_1 | + gunicorn --bind 0.0.0.0:8088 --workers 9 --timeout 60 --limit-request-line 0 --limit-request-field_size 0 superset:app
redis_1 | 1:C 11 Mar 18:10:12.905 # 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 | _._
redis_1 | _.-``__ ''-._
redis_1 | _.-`` `. `_. ''-._ Redis 3.2.12 (00000000/0) 64 bit
redis_1 | .-`` .-```. ```\/ _.,_ ''-._
redis_1 | ( ' , .-` | `, ) Running in standalone 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:M 11 Mar 18:10:12.907 # 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 11 Mar 18:10:12.907 # Server started, Redis version 3.2.12
redis_1 | 1:M 11 Mar 18:10:12.907 # 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 11 Mar 18:10:12.907 # 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 11 Mar 18:10:12.907 * The server is now ready to accept connections on port 6379
redis_1 | 1:signal-handler (1552329732) Received SIGTERM scheduling shutdown...
redis_1 | 1:M 11 Mar 18:42:12.263 # User requested shutdown...
redis_1 | 1:M 11 Mar 18:42:12.263 * Saving the final RDB snapshot before exiting.
redis_1 | 1:M 11 Mar 18:42:12.273 * DB saved on disk
redis_1 | 1:M 11 Mar 18:42:12.273 # Redis is now ready to exit, bye bye...
redis_1 | 1:C 11 Mar 19:02:54.132 # 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 | _._
redis_1 | _.-``__ ''-._
redis_1 | _.-`` `. `_. ''-._ Redis 3.2.12 (00000000/0) 64 bit
redis_1 | .-`` .-```. ```\/ _.,_ ''-._
redis_1 | ( ' , .-` | `, ) Running in standalone 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 | `-._ `-._`-.__.-'_.-' _.-'
```
```
postgres_1 | PostgreSQL init process complete; ready for start up.
postgres_1 |
postgres_1 | 2019-03-11 18:28:47.662 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_1 | 2019-03-11 18:28:47.662 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres_1 | 2019-03-11 18:28:47.683 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1 | 2019-03-11 18:28:47.713 UTC [62] LOG: database system was shut down at 2019-03-11 18:28:47 UTC
postgres_1 | 2019-03-11 18:28:47.724 UTC [1] LOG: database system is ready to accept connections
postgres_1 | 2019-03-11 18:42:12.195 UTC [1] LOG: received smart shutdown request
postgres_1 | 2019-03-11 18:42:12.199 UTC [1] LOG: worker process: logical replication launcher (PID 68) exited with exit code 1
postgres_1 | 2019-03-11 18:42:12.201 UTC [63] LOG: shutting down
postgres_1 | 2019-03-11 18:42:12.231 UTC [1] LOG: database system is shut down
postgres_1 | 2019-03-11 19:02:54.140 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_1 | 2019-03-11 19:02:54.140 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres_1 | 2019-03-11 19:02:54.159 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1 | 2019-03-11 19:02:54.198 UTC [23] LOG: database system was shut down at 2019-03-11 18:42:12 UTC
postgres_1 | 2019-03-11 19:02:54.218 UTC [1] LOG: database system is ready to accept connections
postgres_1 | 2019-03-11 19:05:35.612 UTC [37] LOG: unexpected EOF on client connection with an open transaction
postgres_1 | 2019-03-11 19:05:35.615 UTC [30] LOG: unexpected EOF on client connection with an open transaction
postgres_1 | 2019-03-11 19:05:35.622 UTC [33] LOG: unexpected EOF on client connection with an open transaction
postgres_1 | 2019-03-11 19:05:35.622 UTC [31] LOG: unexpected EOF on client connection with an open transaction
postgres_1 | 2019-03-11 19:05:35.624 UTC [36] LOG: unexpected EOF on client connection with an open transaction
postgres_1 | 2019-03-11 19:05:35.626 UTC [32] LOG: unexpected EOF on client connection with an open transaction
postgres_1 | 2019-03-11 19:05:35.627 UTC [39] LOG: unexpected EOF on client connection with an open transaction
postgres_1 | 2019-03-11 19:05:35.665 UTC [38] LOG: unexpected EOF on client connection with an open transaction
postgres_1 | 2019-03-11 19:05:35.965 UTC [1] LOG: received smart shutdown request
postgres_1 | 2019-03-11 19:05:35.972 UTC [1] LOG: worker process: logical replication launcher (PID 29) exited with exit code 1
postgres_1 | 2019-03-11 19:05:35.973 UTC [24] LOG: shutting down
postgres_1 | 2019-03-11 19:05:36.038 UTC [1] LOG: database system is shut down
postgres_1 | 2019-03-11 19:05:49.437 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
postgres_1 | 2019-03-11 19:05:49.438 UTC [1] LOG: listening on IPv6 address "::", port 5432
postgres_1 | 2019-03-11 19:05:49.457 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1 | 2019-03-11 19:05:49.503 UTC [23] LOG: database system was shut down at 2019-03-11 19:05:36 UTC
postgres_1 | 2019-03-11 19:05:49.525 UTC [1] LOG: database system is ready to accept connections
postgres_1 | 2019-03-11 19:06:18.957 UTC [30] ERROR: duplicate key value violates unique constraint "ab_user_username_key"
postgres_1 | 2019-03-11 19:06:18.957 UTC [30] DETAIL: Key (username)=(superset) already exists.
postgres_1 | 2019-03-11 19:06:18.957 UTC [30] STATEMENT: INSERT INTO ab_user (id, first_name, last_name, username, password, active, email, last_login, login_count, fail_login_count, created_on, changed_on, created_by_fk, changed_by_fk) VALUES (nextval('ab_user_id_seq'), 'root', 'root', 'superset', 'pbkdf2:sha256:50000$9QOJttHu$06ee34e8cbaf8f9e987931f6ae2ff4e1eea913136dd5f6fc841d02d00c869893', true, 'root@sap.com', NULL, NULL, NULL, '2019-03-11T19:06:18.956293'::timestamp, '2019-03-11T19:06:18.956325'::timestamp, NULL, NULL) RETURNING ab_user.id
redis_1 | 1:M 11 Mar 19:05:49.361 # 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 11 Mar 19:05:49.361 # 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 11 Mar 19:05:49.361 * DB loaded from disk: 0.000 seconds
redis_1 | 1:M 11 Mar 19:05:49.361 * The server is now ready to accept connections on port 6379
superset_1 | [2019-03-11 19:06:50 +0000] [8] [INFO] Starting gunicorn 19.8.0
superset_1 | [2019-03-11 19:06:50 +0000] [8] [INFO] Listening at: http://0.0.0.0:8088 (8)
superset_1 | [2019-03-11 19:06:50 +0000] [8] [INFO] Using worker: sync
superset_1 | [2019-03-11 19:06:50 +0000] [13] [INFO] Booting worker with pid: 13
superset_1 | [2019-03-11 19:06:50 +0000] [14] [INFO] Booting worker with pid: 14
superset_1 | [2019-03-11 19:06:50 +0000] [15] [INFO] Booting worker with pid: 15
superset_1 | [2019-03-11 19:06:50 +0000] [16] [INFO] Booting worker with pid: 16
superset_1 | [2019-03-11 19:06:50 +0000] [18] [INFO] Booting worker with pid: 18
superset_1 | [2019-03-11 19:06:50 +0000] [21] [INFO] Booting worker with pid: 21
superset_1 | [2019-03-11 19:06:50 +0000] [22] [INFO] Booting worker with pid: 22
superset_1 | [2019-03-11 19:06:51 +0000] [23] [INFO] Booting worker with pid: 23
superset_1 | [2019-03-11 19:06:51 +0000] [25] [INFO] Booting worker with pid: 25
```
But when I try to open the link in browser it doesn't connect.
http://localhost:8088. It does't connect. It works on my mac though without this 243 error.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org