Port 9000 down on fresh build with docker-compose

[jotamjr]

Issue Type

• Bug Report

Faraday version

Faraday v5.1.1

Component Name

If you know where the problem lays indicate it:
WebSocket port 9000

Steps to reproduce

Built faraday using docker-compose following the steps from the wiki and using master YAML file.

Expected results

Adding docker-compose output:

docker-compose up
Creating network "faraday_default" with the default driver
Creating volume "faraday_db" with local driver
Pulling db (postgres:12.7-alpine)...
12.7-alpine: Pulling from library/postgres
29291e31a76a: Pull complete
c7f8a1ea71cb: Pull complete
64d8912b293d: Pull complete
c5ea624bd2f9: Pull complete
8b31ea9e78e2: Pull complete
73b55a167823: Pull complete
182bdad89856: Pull complete
8106b49e33bd: Pull complete
Digest: sha256:8b4e93c283134e56936c0115e552e3dbac05f323c898b100408ed6df77f3e1b5
Status: Downloaded newer image for postgres:12.7-alpine
Pulling redis (redis:6.2-alpine)...
6.2-alpine: Pulling from library/redis
4abcf2066143: Pull complete
03ed65a553ab: Pull complete
5e02229dc2ff: Pull complete
876d718c369b: Pull complete
fed7a611aab9: Pull complete
271aea565ef9: Pull complete
4f4fb700ef54: Pull complete
e99016e57f48: Pull complete
Digest: sha256:51d6c56749a4243096327e3fb964a48ed92254357108449cb6e23999c37773c5
Status: Downloaded newer image for redis:6.2-alpine
Pulling app (index.docker.io/faradaysec/faraday:)...
latest: Pulling from faradaysec/faraday
6eab20599fab: Pull complete
f790e9177a85: Pull complete
6dbe8744009a: Pull complete
176e3d22ecf5: Pull complete
0e85dc1c893f: Pull complete
8f6ba2923867: Pull complete
57383699295d: Pull complete
a477370dd63b: Pull complete
4eac83001ed9: Pull complete
9310c7e77649: Pull complete
7fc3795037e4: Pull complete
31041a8eb17a: Pull complete
b876b5086670: Pull complete
71840f5ffa2c: Pull complete
7db332a0c190: Pull complete
Digest: sha256:f849f0b3f055c0a54d298b1de4e619ccad2905993f581b02e2354b577a7f3d63
Status: Downloaded newer image for faradaysec/faraday:latest
Creating faraday_db    ... done
Creating faraday_redis ... done
Creating faraday_app   ... done
Attaching to faraday_db, faraday_redis, faraday_app
db_1     | The files belonging to this database system will be owned by user "postgres".
db_1     | This user must also own the server process.
db_1     |
db_1     | The database cluster will be initialized with locale "en_US.utf8".
db_1     | The default database encoding has accordingly been set to "UTF8".
db_1     | The default text search configuration will be set to "english".
db_1     |
db_1     | Data page checksums are disabled.
redis_1  | 1:C 12 Mar 2024 02:46:24.849 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1  | 1:C 12 Mar 2024 02:46:24.849 # Redis version=6.2.14, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1  | 1:C 12 Mar 2024 02:46:24.849 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
db_1     |
redis_1  | 1:M 12 Mar 2024 02:46:24.849 * monotonic clock: POSIX clock_gettime
db_1     | fixing permissions on existing directory /var/lib/postgresql/data ... ok
app_1    | Tue Mar 12 02:46:25 UTC 2024 Creating server.ini
redis_1  | 1:M 12 Mar 2024 02:46:24.849 * Running mode=standalone, port=6379.
db_1     | creating subdirectories ... ok
redis_1  | 1:M 12 Mar 2024 02:46:24.849 # Server initialized
redis_1  | 1:M 12 Mar 2024 02:46:24.849 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
db_1     | selecting dynamic shared memory implementation ... posix
redis_1  | 1:M 12 Mar 2024 02:46:24.849 * Ready to accept connections
db_1     | selecting default max_connections ... 100
db_1     | selecting default shared_buffers ... 128MB
db_1     | selecting default time zone ... UTC
db_1     | creating configuration files ... ok
db_1     | running bootstrap script ... ok
db_1     | performing post-bootstrap initialization ... sh: locale: not found
db_1     | 2024-03-12 02:46:25.100 UTC [30] WARNING:  no usable system locales were found
app_1    | Waiting for postgres on db
db_1     | ok
db_1     | syncing data to disk ... ok
db_1     |
db_1     |
db_1     | Success. You can now start the database server using:
db_1     |
db_1     |     pg_ctl -D /var/lib/postgresql/data -l logfile start
db_1     |
db_1     | initdb: warning: enabling "trust" authentication for local connections
db_1     | You can change this by editing pg_hba.conf or using the option -A, or
db_1     | --auth-local and --auth-host, the next time you run initdb.
db_1     | waiting for server to start....2024-03-12 02:46:25.461 UTC [35] LOG:  starting PostgreSQL 12.7 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
db_1     | 2024-03-12 02:46:25.462 UTC [35] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1     | 2024-03-12 02:46:25.472 UTC [36] LOG:  database system was shut down at 2024-03-12 02:46:25 UTC
db_1     | 2024-03-12 02:46:25.474 UTC [35] LOG:  database system is ready to accept connections
db_1     |  done
db_1     | server started
db_1     | CREATE DATABASE
db_1     |
db_1     |
db_1     | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
db_1     |
db_1     | waiting for server to shut down...2024-03-12 02:46:25.615 UTC [35] LOG:  received fast shutdown request
db_1     | .2024-03-12 02:46:25.615 UTC [35] LOG:  aborting any active transactions
db_1     | 2024-03-12 02:46:25.616 UTC [35] LOG:  background worker "logical replication launcher" (PID 42) exited with exit code 1
db_1     | 2024-03-12 02:46:25.616 UTC [37] LOG:  shutting down
db_1     | 2024-03-12 02:46:25.622 UTC [35] LOG:  database system is shut down
db_1     |  done
db_1     | server stopped
db_1     |
db_1     | PostgreSQL init process complete; ready for start up.
db_1     |
db_1     | 2024-03-12 02:46:25.720 UTC [1] LOG:  starting PostgreSQL 12.7 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
db_1     | 2024-03-12 02:46:25.720 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
db_1     | 2024-03-12 02:46:25.720 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1     | 2024-03-12 02:46:25.721 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1     | 2024-03-12 02:46:25.740 UTC [49] LOG:  database system was shut down at 2024-03-12 02:46:25 UTC
db_1     | 2024-03-12 02:46:25.743 UTC [1] LOG:  database system is ready to accept connections
app_1    | Tue Mar 12 02:46:26 UTC 2024 Creating tables on database faraday...
app_1    | Creating tables
app_1    | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
app_1    | INFO  [alembic.runtime.migration] Will assume transactional DDL.
app_1    | INFO  [alembic.runtime.migration] Running stamp_revision  -> f7ca45632cce
app_1    | Tables created successfully!
app_1    | Tue Mar 12 02:46:28 UTC 2024 Creating superuser...
app_1    | 2024-03-12T02:46:29+0000 - passlib.handlers.bcrypt - WARNING {MainThread} [pid:31] [bcrypt.py:622 - _load_backend_mixin()]  (trapped) error reading bcrypt version
app_1    | Traceback (most recent call last):
app_1    |   File "/usr/local/lib/python3.8/site-packages/passlib/handlers/bcrypt.py", line 620, in _load_backend_mixin
app_1    |     version = _bcrypt.__about__.__version__
app_1    | AttributeError: module 'bcrypt' has no attribute '__about__'
app_1    | User faraday created successfully!
app_1    | Admin user created with username: faraday password: [REDACTED]
app_1    | Update swagger...
app_1    | /usr/local/lib/python3.8/site-packages/apispec/ext/marshmallow/common.py:139: UserWarning: Multiple schemas resolved to the name Service. The name has been modified. Either manually add each of the schemas with a different name or provide a custom schema_name_resolver.
app_1    |   warnings.warn(
app_1    | /usr/local/lib/python3.8/site-packages/apispec/ext/marshmallow/common.py:82: UserWarning: Only explicitly-declared fields will be included in the Schema Object. Fields defined in Meta.fields or Meta.additional are ignored.
app_1    |   warnings.warn(
app_1    | Tue Mar 12 02:46:32 UTC 2024 Running migrations ...
app_1    | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
app_1    | INFO  [alembic.runtime.migration] Will assume transactional DDL.
app_1    | Tue Mar 12 02:46:34 UTC 2024 Starting Faraday server with workers...
app_1    | Initializing faraday server
app_1    | Server initialized for gevent.
app_1    | 2024-03-12T02:46:35+0000 - engineio.server - INFO {MainThread} [pid:48] [base_server.py:99 - __init__()]  Server initialized for gevent.
app_1    | [2024-03-12 02:46:35,769] INFO in app: Celery is enabled ...
app_1    | 2024-03-12T02:46:35+0000 - faraday.server.app - INFO {MainThread} [pid:48] [app.py:551 - register_extensions()]  Celery is enabled ...
app_1    | [2024-03-12 02:46:35,769] INFO in app: Checking celery configuration ...
app_1    | 2024-03-12T02:46:35+0000 - faraday.server.app - INFO {MainThread} [pid:48] [app.py:552 - register_extensions()]  Checking celery configuration ...
app_1    | 2024-03-12T02:46:35+0000 - alembic.runtime.migration - INFO {MainThread} [pid:48] [migration.py:216 - __init__()]  Context impl PostgresqlImpl.
app_1    | 2024-03-12T02:46:35+0000 - alembic.runtime.migration - INFO {MainThread} [pid:48] [migration.py:219 - __init__()]  Will assume transactional DDL.
app_1    | 2024-03-12T02:46:35+0000 - faraday.start_server - WARNING {MainThread} [pid:48] [start_server.py:96 - check_postgresql()]  No workspaces found
app_1    | 2024-03-12T02:46:35+0000 - sh.command - INFO {MainThread} [pid:48] [sh.py:579 - info()]  <Command '/usr/local/bin/faraday-worker', pid 51>: process started
app_1    | Starting celery %s Namespace(concurrency=None, loglevel=None, queue='celery')
app_1    |
app_1    |  -------------- celery@84f245117f73 v5.3.6 (emerald-rush)
app_1    | --- ***** -----
app_1    | -- ******* ---- Linux-6.6.13-amd64-x86_64-with-glibc2.2.5 2024-03-12 02:46:37
app_1    | - *** --- * ---
app_1    | - ** ---------- [config]
app_1    | - ** ---------- .> app:         faraday.server.app:0x7f12a22cbe80
app_1    | - ** ---------- .> transport:   redis://redis:6379//
app_1    | - ** ---------- .> results:     redis://redis:6379/
app_1    | - *** --- * --- .> concurrency: 15 (prefork)
app_1    | -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
app_1    | --- ***** -----
app_1    |  -------------- [queues]
app_1    |                 .> celery           exchange=celery(direct) key=celery
app_1    |
app_1    |
app_1    | 2024-03-12T02:50:47+0000 - geventwebsocket.handler - INFO {Dummy-3} [pid:48] [handler.py:242 - log_request()]  x.x.x.x - - [2024-03-12 02:50:47] "GET / HTTP/1.1" 304 141 0.005699
app_1    | 2024-03-12T02:50:47+0000 - geventwebsocket.handler - INFO {Dummy-4} [pid:48] [handler.py:242 - log_request()]  x.x.x.x - - [2024-03-12 02:50:47] "GET /static/css/main.ceb0f717.chunk.css HTTP/1.1" 304 154 0.001802
app_1    | 2024-03-12T02:50:47+0000 - geventwebsocket.handler - INFO {Dummy-5} [pid:48] [handler.py:242 - log_request()]  x.x.x.x - - [2024-03-12 02:50:47] "GET /static/js/main.b7784f70.chunk.js HTTP/1.1" 304 153 0.001297
app_1    | 2024-03-12T02:50:47+0000 - geventwebsocket.handler - INFO {Dummy-3} [pid:48] [handler.py:242 - log_request()]  x.x.x.x - - [2024-03-12 02:50:47] "GET /static/js/2.6900211a.chunk.js HTTP/1.1" 200 3064160 0.485222
app_1    | 2024-03-12T02:50:48+0000 - geventwebsocket.handler - INFO {Dummy-3} [pid:48] [handler.py:242 - log_request()]  1x.x.x.x - - [2024-03-12 02:50:48] "GET /_api/v3/ws/filter?q=%7B%22offset%22%3A0%2C%22limit%22%3A10%7D&histogram=true&exclude_stats=false&list_view=false HTTP/1.1" 401 470 0.001374

We usually see faraday.server.web binding in port 9000 in the logs.

[ezk06eer]

@jotamjr Hi, now all is up on port 5985, we will shortly modify the docker-compose and also the docs.

Cheers!

[jotamjr]

Thanks for the update @ezk06eer, I can confirm that I'm able to connect the faraday-dispatcher using port 5985. Can we keep this open until the docs are updated?

Regards,