You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This problem was observed on both brierfoxforecast.com and openprediction.xyz.
Attempting to visit markets/ results in Error: TypeError: Failed to fetch
Looking at logs for postgres, we seem to have a failure to find the .env file.
Where did this come from? Not certain, but it could have been due to a security vulnerability that we have that exists. There are several Github dependabot issues that are pending. There are several Dependabot issues pending that could be worked on.
root@breirfoxforecast-alpha:~# docker compose -p scripts logs | grep postgres
socialpredict-postgres-container | The files belonging to this database system will be owned by user "postgres".
socialpredict-postgres-container | This user must also own the server process.
socialpredict-postgres-container |
socialpredict-postgres-container | The database cluster will be initialized with locale "en_US.utf8".
socialpredict-postgres-container | The default database encoding has accordingly been set to "UTF8".
socialpredict-postgres-container | The default text search configuration will be set to "english".
socialpredict-postgres-container |
socialpredict-postgres-container | Data page checksums are disabled.
socialpredict-postgres-container |
socialpredict-postgres-container | fixing permissions on existing directory /var/lib/postgresql/data ... ok
socialpredict-postgres-container | creating subdirectories ... ok
socialpredict-postgres-container | selecting dynamic shared memory implementation ... posix
socialpredict-postgres-container | selecting default "max_connections" ... 100
socialpredict-postgres-container | selecting default "shared_buffers" ... 128MB
socialpredict-postgres-container | selecting default time zone ... Etc/UTC
socialpredict-postgres-container | creating configuration files ... ok
socialpredict-postgres-container | running bootstrap script ... ok
socialpredict-postgres-container | performing post-bootstrap initialization ... ok
socialpredict-postgres-container | syncing data to disk ... ok
socialpredict-postgres-container |
socialpredict-postgres-container |
socialpredict-postgres-container | Success. You can now start the database server using:
socialpredict-postgres-container |
socialpredict-postgres-container | pg_ctl -D /var/lib/postgresql/data -l logfile start
socialpredict-postgres-container |
socialpredict-postgres-container | initdb: warning: enabling "trust" authentication for local connections
socialpredict-postgres-container | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
socialpredict-postgres-container | waiting for server to start....2024-10-26 17:21:09.955 UTC [47] LOG: starting PostgreSQL 17.0 (Debian 17.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
socialpredict-postgres-container | 2024-10-26 17:21:09.962 UTC [47] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
socialpredict-postgres-container | 2024-10-26 17:21:09.994 UTC [50] LOG: database system was shut down at 2024-10-26 17:21:09 UTC
socialpredict-postgres-container | 2024-10-26 17:21:10.007 UTC [47] LOG: database system is ready to accept connections
socialpredict-postgres-container | done
socialpredict-postgres-container | server started
socialpredict-postgres-container | CREATE DATABASE
socialpredict-postgres-container |
socialpredict-postgres-container |
socialpredict-postgres-container | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
socialpredict-postgres-container |
socialpredict-postgres-container | 2024-10-26 17:21:10.634 UTC [47] LOG: received fast shutdown request
socialpredict-postgres-container | waiting for server to shut down....2024-10-26 17:21:10.638 UTC [47] LOG: aborting any active transactions
socialpredict-postgres-container | 2024-10-26 17:21:10.646 UTC [47] LOG: background worker "logical replication launcher" (PID 53) exited with exit code 1
socialpredict-postgres-container | 2024-10-26 17:21:10.666 UTC [48] LOG: shutting down
socialpredict-postgres-container | 2024-10-26 17:21:10.670 UTC [48] LOG: checkpoint starting: shutdown immediate
socialpredict-postgres-container | 2024-10-26 17:21:10.771 UTC [48] LOG: checkpoint complete: wrote 921 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.057 s, sync=0.028 s, total=0.104 s; sync files=301, longest=0.007 s, average=0.001 s; distance=4238 kB, estimate=4238 kB; lsn=0/1908990, redo lsn=0/1908990
socialpredict-postgres-container | 2024-10-26 17:21:10.789 UTC [47] LOG: database system is shut down
socialpredict-postgres-container | done
socialpredict-postgres-container | server stopped
socialpredict-postgres-container |
socialpredict-postgres-container | PostgreSQL init process complete; ready for start up.
socialpredict-postgres-container |
socialpredict-postgres-container | 2024-10-26 17:21:10.920 UTC [1] LOG: starting PostgreSQL 17.0 (Debian 17.0-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
socialpredict-postgres-container | 2024-10-26 17:21:10.922 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
socialpredict-postgres-container | 2024-10-26 17:21:10.922 UTC [1] LOG: listening on IPv6 address "::", port 5432
socialpredict-postgres-container | 2024-10-26 17:21:10.932 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
socialpredict-postgres-container | 2024-10-26 17:21:10.947 UTC [63] LOG: database system was shut down at 2024-10-26 17:21:10 UTC
socialpredict-postgres-container | 2024-10-26 17:21:10.961 UTC [1] LOG: database system is ready to accept connections
socialpredict-postgres-container | 2024-10-26 17:26:11.003 UTC [61] LOG: checkpoint starting: time
socialpredict-postgres-container | 2024-10-26 17:26:22.509 UTC [61] LOG: checkpoint complete: wrote 117 buffers (0.7%); 0 WAL file(s) added, 0 removed, 0 recycled; write=11.470 s, sync=0.011 s, total=11.507 s; sync files=73, longest=0.004 s, average=0.001 s; distance=426 kB, estimate=426 kB; lsn=0/19734C0, redo lsn=0/1973430
socialpredict-postgres-container | 2024-10-28 19:31:54.529 UTC [61] LOG: checkpoint starting: time
socialpredict-postgres-container | 2024-10-28 19:31:57.010 UTC [61] LOG: checkpoint complete: wrote 25 buffers (0.2%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.423 s, sync=0.017 s, total=2.481 s; sync files=20, longest=0.013 s, average=0.001 s; distance=4 kB, estimate=384 kB; lsn=0/19745F8, redo lsn=0/19745A0
socialpredict-nginx-container | 94.72.101.21 - - [29/Oct/2024:13:20:45 +0000] "GET /docker/postgres/.env HTTP/1.1" 301 169 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36" "-"
socialpredict-frontend-container | 172.18.0.4 - - [29/Oct/2024:14:03:53 +0000] "GET /docker/postgres/.env HTTP/1.0" 404 555 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36" "-"
socialpredict-frontend-container | 2024/10/29 14:03:53 [error] 28#28: *6212 open() "/usr/share/nginx/html/docker/postgres/.env" failed (2: No such file or directory), client: 172.18.0.4, server: localhost, request: "GET /docker/postgres/.env HTTP/1.0", host: "frontend"
socialpredict-nginx-container | 94.72.101.21 - - [29/Oct/2024:14:03:53 +0000] "GET /docker/postgres/.env HTTP/1.1" 404 555 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36" "-"
The text was updated successfully, but these errors were encountered:
Using master from:
f482b6c
This problem was observed on both brierfoxforecast.com and openprediction.xyz.
Error: TypeError: Failed to fetch
Looking at logs for postgres, we seem to have a failure to find the .env file.
Where did this come from? Not certain, but it could have been due to a security vulnerability that we have that exists. There are several Github dependabot issues that are pending. There are several Dependabot issues pending that could be worked on.
The text was updated successfully, but these errors were encountered: