Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

edb.server: Received signal: 15. Shutting down #5895

Closed
petersamokhin opened this issue Aug 4, 2023 · 8 comments · Fixed by #5900
Closed

edb.server: Received signal: 15. Shutting down #5895

petersamokhin opened this issue Aug 4, 2023 · 8 comments · Fixed by #5900

Comments

@petersamokhin
Copy link

petersamokhin commented Aug 4, 2023 •
edited
Loading

hello there! still trying to make edgedb work on a remote postgres backend. while #5894 is not yet merged, I tried to test the setup locally to figure out the minimal requirements required, and I receive a weird error:

INFO 47 2023-08-04T18:53:37.035 edb.server: Connection established to backend database: edgedb
INFO 47 2023-08-04T18:53:37.902 edb.server: Received signal: 15.
INFO 47 2023-08-04T18:53:37.903 edb.server: Shutting down.
ERROR: Could not complete instance bootstrap in 30000000 seconds. If you have slow hardware, consider increasing the timeout via the EDGEDB_DOCKER_BOOTSTRAP_TIMEOUT_SEC variable.

I changed the timeout from 300 to 30000000 seconds to demonstrate the wrong message.
The actual setup takes just a few seconds, so the timeout was not reached.

however, the main issue here is that the server fails with exit code 1, and shows some "signal: 15" in logs

SQL setup 
CREATE DATABASE edgedb;
CREATE USER edgedb WITH ENCRYPTED PASSWORD 'edgedb';
ALTER DATABASE edgedb OWNER TO edgedb;
Full log (67 lines) 
2023-08-04T18:53:18.903472095Z Bootstrapping EdgeDB instance on remote Postgres cluster...
2023-08-04T18:53:20.121165721Z INFO 47 2023-08-04T18:53:20.120 edb.server: starting EdgeDB server 3.2+740bb0d, built on 2023-07-21T19:08Z from revision b7dc55395 (2023-07-21T01:09Z) for aarch64-unknown-linux-gnu
INFO 47 2023-08-04T18:53:20.121 edb.server: instance name: '_unknown'
INFO 47 2023-08-04T18:53:21.372 edb.server: Detected 97 backend connections available.
INFO 47 2023-08-04T18:53:26.834 edb.server: Creating the necessary PostgreSQL extensions...
INFO 47 2023-08-04T18:53:26.860 edb.server: Initializing the standard library...
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_1262" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_1262_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_2964" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_2964_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_1213" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_1213_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_1260" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_1260_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.248 edb.server: skipping "pg_toast_2396" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_2396_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_6000" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_6000_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_3592" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_3592_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_6243" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_6243_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_6100" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_toast_6100_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_database_datname_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_database_oid_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_db_role_setting_databaseid_rol_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_tablespace_oid_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_tablespace_spcname_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_authid_rolname_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_authid_oid_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_auth_members_role_member_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_auth_members_member_role_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_shdepend_depender_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_shdepend_reference_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_shdescription_o_c_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_replication_origin_roiident_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_replication_origin_roname_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_shseclabel_object_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_parameter_acl_parname_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_parameter_acl_oid_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_subscription_oid_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_subscription_subname_index" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_authid" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_subscription" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_database" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_db_role_setting" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_tablespace" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_auth_members" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_shdepend" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_shdescription" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_replication_origin" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_shseclabel" --- only superuser can analyze it
WARNING 47 2023-08-04T18:53:29.249 edb.server: skipping "pg_parameter_acl" --- only superuser can analyze it
INFO 47 2023-08-04T18:53:29.403 edb.server: Configuring database: edgedb
INFO 47 2023-08-04T18:53:29.927 edb.server: introspecting extensions for database 'edgedb'
INFO 47 2023-08-04T18:53:35.001 edb.server: Connection established to backend database: edgedb
INFO 47 2023-08-04T18:53:35.003 edb.server: generating JOSE key pair in "/tmp/tmp.EGcU8WAFUg/xjwfk6gc/edbjwskeys.pem"
INFO 47 2023-08-04T18:53:35.013 edb.server: loading TLS certificates
INFO 47 2023-08-04T18:53:36.757 edb.server: started 1 compiler worker process
INFO 47 2023-08-04T18:53:36.758 edb.server: introspecting database 'edgedb'
INFO 47 2023-08-04T18:53:37.008 edb.server: Serving on 127.0.0.1:39719
INFO 47 2023-08-04T18:53:37.008 edb.server: Serving admin on /tmp/tmp.EGcU8WAFUg/.s.EDGEDB.admin.39719
INFO 47 2023-08-04T18:53:37.035 edb.server: Connection established to backend database: edgedb
INFO 47 2023-08-04T18:53:37.902 edb.server: Received signal: 15.
INFO 47 2023-08-04T18:53:37.903 edb.server: Shutting down.
ERROR: Could not complete instance bootstrap in 30000000 seconds. If you have slow hardware, consider increasing the timeout via the EDGEDB_DOCKER_BOOTSTRAP_TIMEOUT_SEC variable.
@elprans
Copy link
Member

elprans commented Aug 4, 2023

When you say "locally", what you mean is that you're trying to run a local Docker container pointed to a remote hosted Postgres instance or local vanilla Postgres? What's your OS?

@petersamokhin
Copy link
Author

petersamokhin commented Aug 4, 2023 •
edited
Loading

@elprans macOS Ventura 13.4.1 (22F82), both edgedb (3.2) and postgres (15.2) are in docker.
It's docker-compose but with a SQL step to setup the db between the postgres and edgedb runs

@elprans
Copy link
Member

elprans commented Aug 4, 2023

Is the Postgres image arm64 or x86_64? There have been problems with emulation of x86 Postgres on macOS.

@petersamokhin
Copy link
Author

@elprans it's arm64 (Apple Silicon)

@elprans
Copy link
Member

elprans commented Aug 4, 2023

Can you attach the Postgres container log as well please?

@petersamokhin
Copy link
Author

petersamokhin commented Aug 4, 2023 •
edited
Loading

@elprans sure thing. Below is the logs from linux/arm64 postgres 14.8 (the same version that is used by edgedb3.2)

postgres container logs 
2023-08-04T22:17:32.330007927Z The files belonging to this database system will be owned by user "postgres".
2023-08-04T22:17:32.330036427Z This user must also own the server process.
2023-08-04T22:17:32.330038761Z 
2023-08-04T22:17:32.330040552Z The database cluster will be initialized with locale "en_US.utf8".
2023-08-04T22:17:32.330042386Z The default database encoding has accordingly been set to "UTF8".
2023-08-04T22:17:32.330044094Z The default text search configuration will be set to "english".
2023-08-04T22:17:32.330045802Z 
2023-08-04T22:17:32.330047386Z Data page checksums are disabled.
2023-08-04T22:17:32.330049052Z 
2023-08-04T22:17:32.330093386Z fixing permissions on existing directory /var/lib/postgresql/data ... ok
2023-08-04T22:17:32.330431677Z creating subdirectories ... ok
2023-08-04T22:17:32.330441677Z selecting dynamic shared memory implementation ... posix
2023-08-04T22:17:32.348499427Z selecting default max_connections ... 100
2023-08-04T22:17:32.370984261Z selecting default shared_buffers ... 128MB
2023-08-04T22:17:32.382130761Z selecting default time zone ... Etc/UTC
2023-08-04T22:17:32.383203802Z creating configuration files ... ok
2023-08-04T22:17:32.472465761Z running bootstrap script ... ok
2023-08-04T22:17:32.726758386Z performing post-bootstrap initialization ... ok
2023-08-04T22:17:32.816822261Z syncing data to disk ... ok
2023-08-04T22:17:32.816844678Z 
2023-08-04T22:17:32.816846844Z 
2023-08-04T22:17:32.816848428Z Success. You can now start the database server using:
2023-08-04T22:17:32.816850178Z 
2023-08-04T22:17:32.816852011Z     pg_ctl -D /var/lib/postgresql/data -l logfile start
2023-08-04T22:17:32.816853719Z 
2023-08-04T22:17:32.816878928Z initdb: warning: enabling "trust" authentication for local connections
2023-08-04T22:17:32.816952094Z You can change this by editing pg_hba.conf or using the option -A, or
2023-08-04T22:17:32.816954844Z --auth-local and --auth-host, the next time you run initdb.
2023-08-04T22:17:32.855650011Z waiting for server to start....2023-08-04 22:17:32.855 UTC [48] LOG:  starting PostgreSQL 14.8 (Debian 14.8-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2023-08-04T22:17:32.856335094Z 2023-08-04 22:17:32.856 UTC [48] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-04T22:17:32.859983886Z 2023-08-04 22:17:32.859 UTC [49] LOG:  database system was shut down at 2023-08-04 22:17:32 UTC
2023-08-04T22:17:32.864173178Z 2023-08-04 22:17:32.864 UTC [48] LOG:  database system is ready to accept connections
2023-08-04T22:17:32.942928344Z  done
2023-08-04T22:17:32.942947511Z server started
2023-08-04T22:17:32.974053386Z 
2023-08-04T22:17:32.974069511Z /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
2023-08-04T22:17:32.974080178Z 
2023-08-04T22:17:32.975125344Z waiting for server to shut down...2023-08-04 22:17:32.975 UTC [48] LOG:  received fast shutdown request
2023-08-04T22:17:32.976780636Z .2023-08-04 22:17:32.976 UTC [48] LOG:  aborting any active transactions
2023-08-04T22:17:32.979463094Z 2023-08-04 22:17:32.979 UTC [48] LOG:  background worker "logical replication launcher" (PID 55) exited with exit code 1
2023-08-04T22:17:32.979598386Z 2023-08-04 22:17:32.979 UTC [50] LOG:  shutting down
2023-08-04T22:17:32.990084219Z 2023-08-04 22:17:32.990 UTC [48] LOG:  database system is shut down
2023-08-04T22:17:33.080540094Z  done
2023-08-04T22:17:33.080566303Z server stopped
2023-08-04T22:17:33.082163636Z 
2023-08-04T22:17:33.082187136Z PostgreSQL init process complete; ready for start up.
2023-08-04T22:17:33.082189594Z 
2023-08-04T22:17:33.103170344Z 2023-08-04 22:17:33.103 UTC [1] LOG:  starting PostgreSQL 14.8 (Debian 14.8-1.pgdg120+1) on aarch64-unknown-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2023-08-04T22:17:33.103236636Z 2023-08-04 22:17:33.103 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-08-04T22:17:33.103243761Z 2023-08-04 22:17:33.103 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-08-04T22:17:33.105098094Z 2023-08-04 22:17:33.105 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-08-04T22:17:33.108205053Z 2023-08-04 22:17:33.108 UTC [61] LOG:  database system was shut down at 2023-08-04 22:17:32 UTC
2023-08-04T22:17:33.112346636Z 2023-08-04 22:17:33.112 UTC [1] LOG:  database system is ready to accept connections
2023-08-04T22:17:49.112793421Z 2023-08-04 22:17:49.112 UTC [190] ERROR:  permission denied for view pg_file_settings
2023-08-04T22:17:49.112837129Z 2023-08-04 22:17:49.112 UTC [190] STATEMENT:  
2023-08-04T22:17:49.112840838Z 	                SELECT
2023-08-04T22:17:49.112843629Z 	                    setting
2023-08-04T22:17:49.112846463Z 	                FROM
2023-08-04T22:17:49.112848713Z 	                    pg_file_settings
2023-08-04T22:17:49.112850963Z 	                WHERE
2023-08-04T22:17:49.112853296Z 	                    setting = 'cluster_name'
2023-08-04T22:17:49.112855713Z 	                    AND sourcefile = ((
2023-08-04T22:17:49.112857963Z 	                        SELECT setting
2023-08-04T22:17:49.112860213Z 	                        FROM pg_settings WHERE name = 'data_directory'
2023-08-04T22:17:49.112862546Z 	                    ) || '/postgresql.auto.conf')
2023-08-04T22:17:49.112864796Z 	                
2023-08-04T22:17:49.113284129Z 2023-08-04 22:17:49.113 UTC [190] ERROR:  must be superuser to create superusers
2023-08-04T22:17:49.113306254Z 2023-08-04 22:17:49.113 UTC [190] STATEMENT:  CREATE ROLE "bef4a321-3314-11ee-946e-850c8246b8f5" WITH SUPERUSER
2023-08-04T22:17:51.980993589Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_1262" --- only superuser can analyze it
2023-08-04T22:17:51.981021881Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_1262_index" --- only superuser can analyze it
2023-08-04T22:17:51.981024131Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_2964" --- only superuser can analyze it
2023-08-04T22:17:51.981026089Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_2964_index" --- only superuser can analyze it
2023-08-04T22:17:51.981028006Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_1213" --- only superuser can analyze it
2023-08-04T22:17:51.981029714Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_1213_index" --- only superuser can analyze it
2023-08-04T22:17:51.981031464Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_1260" --- only superuser can analyze it
2023-08-04T22:17:51.981033631Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_1260_index" --- only superuser can analyze it
2023-08-04T22:17:51.981054881Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_2396" --- only superuser can analyze it
2023-08-04T22:17:51.981069089Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_2396_index" --- only superuser can analyze it
2023-08-04T22:17:51.981071464Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_6000" --- only superuser can analyze it
2023-08-04T22:17:51.981073381Z 2023-08-04 22:17:51.980 UTC [191] WARNING:  skipping "pg_toast_6000_index" --- only superuser can analyze it
2023-08-04T22:17:51.981075214Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_toast_3592" --- only superuser can analyze it
2023-08-04T22:17:51.981076964Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_toast_3592_index" --- only superuser can analyze it
2023-08-04T22:17:51.981078714Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_toast_6100" --- only superuser can analyze it
2023-08-04T22:17:51.981082589Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_toast_6100_index" --- only superuser can analyze it
2023-08-04T22:17:51.981206714Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_database_datname_index" --- only superuser can analyze it
2023-08-04T22:17:51.981217464Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_database_oid_index" --- only superuser can analyze it
2023-08-04T22:17:51.981219714Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_db_role_setting_databaseid_rol_index" --- only superuser can analyze it
2023-08-04T22:17:51.981221589Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_tablespace_oid_index" --- only superuser can analyze it
2023-08-04T22:17:51.981223256Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_tablespace_spcname_index" --- only superuser can analyze it
2023-08-04T22:17:51.981225006Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_authid_rolname_index" --- only superuser can analyze it
2023-08-04T22:17:51.981234797Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_authid_oid_index" --- only superuser can analyze it
2023-08-04T22:17:51.981236881Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_auth_members_role_member_index" --- only superuser can analyze it
2023-08-04T22:17:51.981238797Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_auth_members_member_role_index" --- only superuser can analyze it
2023-08-04T22:17:51.981241131Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_shdepend_depender_index" --- only superuser can analyze it
2023-08-04T22:17:51.981242922Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_shdepend_reference_index" --- only superuser can analyze it
2023-08-04T22:17:51.981245506Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_shdescription_o_c_index" --- only superuser can analyze it
2023-08-04T22:17:51.981271172Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_replication_origin_roiident_index" --- only superuser can analyze it
2023-08-04T22:17:51.981274006Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_replication_origin_roname_index" --- only superuser can analyze it
2023-08-04T22:17:51.981275839Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_shseclabel_object_index" --- only superuser can analyze it
2023-08-04T22:17:51.981372672Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_subscription_oid_index" --- only superuser can analyze it
2023-08-04T22:17:51.981379797Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_subscription_subname_index" --- only superuser can analyze it
2023-08-04T22:17:51.981381756Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_authid" --- only superuser can analyze it
2023-08-04T22:17:51.981435756Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_subscription" --- only superuser can analyze it
2023-08-04T22:17:51.981518339Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_database" --- only superuser can analyze it
2023-08-04T22:17:51.981524256Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_db_role_setting" --- only superuser can analyze it
2023-08-04T22:17:51.981528381Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_tablespace" --- only superuser can analyze it
2023-08-04T22:17:51.981530172Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_auth_members" --- only superuser can analyze it
2023-08-04T22:17:51.981531922Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_shdepend" --- only superuser can analyze it
2023-08-04T22:17:51.981533672Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_shdescription" --- only superuser can analyze it
2023-08-04T22:17:51.981654631Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_replication_origin" --- only superuser can analyze it
2023-08-04T22:17:51.981661797Z 2023-08-04 22:17:51.981 UTC [191] WARNING:  skipping "pg_shseclabel" --- only superuser can analyze it

this actually looks concerning:

[190] ERROR:  must be superuser to create superusers
[190] STATEMENT:  CREATE ROLE "bef4a321-3314-11ee-946e-850c8246b8f5" WITH SUPERUSER

this functionality is not gonna be available in our case. No superusers, no database or extensions creation from SQL

@elprans
Copy link
Member

elprans commented Aug 4, 2023

That's fine, EdgeDB can work without superuser access (the error is the result of probing). That said, this might hint to why EdgeDB fails to bootstrap. Can you share the whole startup script please?

@petersamokhin
Copy link
Author

petersamokhin commented Aug 4, 2023 •
edited
Loading

@elprans just in case, I'd like to highlight that everything works with no issues if I don't provide EDGEDB_SERVER_BACKEND_DSN, i.e. if the embedded postgres is used.

there is a separate tiny repo that reproduces the issue:
https://github.com/nightstory/edgedb-postgres-issue

just ran this showcase on ubuntu server, with linux/amd64 postgres docker image, no difference — the issue is still reproducible for me

@elprans elprans mentioned this issue Aug 5, 2023
Merged
elprans added a commit that referenced this issue Aug 5, 2023
@elprans
Fix healthchecks on single-database instances
73691b9 
Instances running on backends without `CREATE_DATABASE` capability will
only have the `edgedb` database in them, while the healthcheck endpoints
attempt to connect to the system database which is only present in
multi-database mode.

Fixes: #5895
elprans added a commit that referenced this issue Aug 7, 2023
@elprans
Fix healthchecks on single-database instances (#5900)
7ce7162 
Instances running on backends without `CREATE_DATABASE` capability will
only have the `edgedb` database in them, while the healthcheck endpoints
attempt to connect to the system database which is only present in
multi-database mode.

Fixes: #5895
elprans added a commit that referenced this issue Aug 22, 2023
@elprans
Fix healthchecks on single-database instances (#5900)
fa6937f 
Instances running on backends without `CREATE_DATABASE` capability will
only have the `edgedb` database in them, while the healthcheck endpoints
attempt to connect to the system database which is only present in
multi-database mode.

Fixes: #5895
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix healthchecks on single-database instances edgedb/edgedb
2 participants
@elprans @petersamokhin