I ve tried various config file settings both in the prefect

Question

I ve tried various config file settings both in the prefect config toml and by editing the python installed config in the site packages directory Had the same issue with the conda install Any ideas

Kyle Moon-Wright · Answer

Hey < Frank Lind> Can you share the traceback you re encountering I wonder if you re facing the same issue as discussed

Frank Lind · Answer

Hi Thanks for the response I didn t see an exact fix in the above thread This is a pip install in a conda base environment

Frank Lind · Answer

base av developer ubuntu ~$ prefect server start Pulling postgres done Pulling hasura done Pulling graphql done Pulling apollo done Pulling scheduler done Pulling ui done Creating network prefect server with the default driver Creating tmp postgres 1 done Creating tmp hasura 1 done Creating tmp graphql 1 done Creating tmp scheduler 1 done Creating tmp apollo 1 done Creating tmp ui 1 done Attaching to tmp postgres 1 tmp hasura 1 tmp graphql 1 tmp apollo 1 tmp scheduler 1 tmp ui 1 graphql 1 | graphql 1 | Running Alembic migrations graphql 1 | INFO alembic runtime migration Context impl PostgresqlImpl graphql 1 | INFO alembic runtime migration Will assume transactional DDL hasura 1 | type startup timestamp 2020 06 22T20 25 17 297+0000 level info detail kind server configuration info live query options batch size 100 refetch delay 1 transaction isolation ISOLATION LEVEL READ COMMITTED plan cache options plan cache size 100 enabled log types http log websocket log startup webhook log server host HostAny enable allowlist false log level info auth hook mode null use prepared statements true unauth role null stringify numeric types false enabled apis metadata graphql config pgdump enable telemetry true enable console true auth hook null jwt secret null cors config allowed origins disabled false ws read cookie null console assets dir null admin secret set false port 3000 hasura 1 | type startup timestamp 2020 06 22T20 25 17 297+0000 level info detail kind postgres connection info retries 1 database url postgres 5432 prefect server hasura 1 | internal could not connect to server Connection refused n tIs the server running on host postgres 172 26 0 2 and accepting n tTCP IP connections on port 5432 n path $ error connection error code postgres error apollo 1 | apollo 1 | gt serve apollo apollo 1 | gt node dist index js apollo 1 | postgres 1 | The files belonging to this database system will be owned by user postgres postgres 1 | This user must also own the server process postgres 1 | postgres 1 | The database cluster will be initialized with locale en US utf8 postgres 1 | The default database encoding has accordingly been set to UTF8 postgres 1 | The default text search configuration will be set to english postgres 1 | postgres 1 | Data page checksums are disabled postgres 1 | postgres 1 | fixing permissions on existing directory var lib postgresql data ok postgres 1 | creating subdirectories ok postgres 1 | selecting default max connections 100 postgres 1 | selecting default shared buffers 128MB postgres 1 | selecting default timezone Etc UTC postgres 1 | selecting dynamic shared memory implementation posix postgres 1 | creating configuration files ok postgres 1 | running bootstrap script ok postgres 1 | performing post bootstrap initialization ok graphql 1 | INFO alembic runtime migration Running upgrade gt 723da8052cbd create extensions graphql 1 | Error psycopg2 errors UniqueViolation duplicate key value violates unique constraint pg extension name index graphql 1 | DETAIL Key extname = pgcrypto already exists graphql 1 | graphql 1 | SQL graphql 1 | CREATE EXTENSION IF NOT EXISTS pgcrypto graphql 1 | CREATE EXTENSION IF NOT EXISTS pg trgm graphql 1 | graphql 1 | Background on this error at graphql 1 | graphql 1 | Could not upgrade the database postgres 1 | syncing data to disk postgres 1 | WARNING enabling trust authentication for local connections postgres 1 | You can change this by editing pg hba conf or using the option A or postgres 1 | auth local and auth host the next time you run initdb postgres 1 | ok postgres 1 | postgres 1 | Success You can now start the database server using postgres 1 | postgres 1 | pg ctl D var lib postgresql data l logfile start postgres 1 | postgres 1 | waiting for server to start 2020 06 22 20 25 16 823 UTC 47 LOG listening on Unix socket var run postgresql s PGSQL 5432 postgres 1 | 2020 06 22 20 25 16 849 UTC 48 LOG database system was shut down at 2020 06 22 20 25 16 UTC postgres 1 | 2020 06 22 20 25 16 857 UTC 47 LOG database system is ready to accept connections postgres 1 | done postgres 1 | server started postgres 1 | CREATE DATABASE postgres 1 | postgres 1 | postgres 1 | usr local bin docker entrypoint sh ignoring docker entrypoint initdb d postgres 1 | postgres 1 | 2020 06 22 20 25 17 366 UTC 47 LOG received fast shutdown request postgres 1 | waiting for server to shut down 2020 06 22 20 25 17 367 UTC 47 LOG aborting any active transactions postgres 1 | 2020 06 22 20 25 17 370 UTC 47 LOG background worker logical replication launcher PID 54 exited with exit code 1 postgres 1 | 2020 06 22 20 25 17 371 UTC 49 LOG shutting down postgres 1 | 2020 06 22 20 25 17 382 UTC 47 LOG database system is shut down postgres 1 | done postgres 1 | server stopped postgres 1 | postgres 1 | PostgreSQL init process complete ready for start up postgres 1 | postgres 1 | 2020 06 22 20 25 17 477 UTC 1 LOG listening on IPv4 address 0 0 0 0 port 5432 postgres 1 | 2020 06 22 20 25 17 477 UTC 1 LOG listening on IPv6 address port 5432 postgres 1 | 2020 06 22 20 25 17 479 UTC 1 LOG listening on Unix socket var run postgresql s PGSQL 5432 postgres 1 | 2020 06 22 20 25 17 492 UTC 65 LOG database system was shut down at 2020 06 22 20 25 17 UTC postgres 1 | 2020 06 22 20 25 17 495 UTC 1 LOG database system is ready to accept connections postgres 1 | 2020 06 22 20 25 19 629 UTC 73 ERROR duplicate key value violates unique constraint pg extension name index postgres 1 | 2020 06 22 20 25 19 629 UTC 73 DETAIL Key extname = pgcrypto already exists postgres 1 | 2020 06 22 20 25 19 629 UTC 73 STATEMENT postgres 1 | CREATE EXTENSION IF NOT EXISTS pgcrypto postgres 1 | CREATE EXTENSION IF NOT EXISTS pg trgm postgres 1 | ui 1 | Replacing graphql references with ui 1 | var www js app 7fd10635 js ui 1 | var www js chunk 290ef6aa c9577213 js ui 1 | var www js chunk 35d72edc aeb53d5b js ui 1 | var www js chunk 5d657775 61e987a9 js ui 1 | var www js chunk 65b545d9 8422ea0b js ui 1 | var www js chunk 6fd6fc38 7860b637 js ui 1 | var www js chunk 8fb1ff70 23e15619 js ui 1 | var www js chunk 93a4c748 ddd54c3b js ui 1 | var www js chunk c52f9fba 8c504a14 js ui 1 | var www js chunk d03cee18 0c5fb4fe js ui 1 | var www js chunk d3b865a4 60462056 js ui 1 | var www js chunk vendors f1c338f7 js ui 1 | var www js dashboard a5face6b js ui 1 | var www js dashboard~flow version groups b35296c6 js ui 1 | var www js dashboard~flow~flow run~interactive api~task~task run 64889ee7 js ui 1 | var www js dashboard~flow~flow run~schematics view~task~task run 5dbabe8e js ui 1 | var www js flow run e8d112a2 js ui 1 | var www js flow version groups 1891b372 js ui 1 | var www js flow 4d8eaec9 js ui 1 | var www js flow~flow run~interactive api~task~task run 12701769 js ui 1 | var www js flow~flow run~schematics view~task~task run 4d9b9eca js ui 1 | var www js interactive api 4362560d js ui 1 | var www js onboard page 4086ef69 js ui 1 | var www js schematics view 38febea4 js ui 1 | var www js schematics e3653fd6 js ui 1 | var www js task run d683a69e js ui 1 | var www js task 5d12d448 js ui 1 | var www js welcome df9a970c js ui 1 | space invader space invader space invader UI running at localhost 8080 space invader space invader space invader scheduler 1 | 2020 06 22 20 25 21 154 INFO prefect server Scheduler | Scheduler will start after an initial delay of 264 seconds apollo 1 | 2020 06 22T20 25 21 889Z Error fetching GraphQL health FetchError request to failed reason connect ECONNREFUSED 172 26 0 4 4201 apollo 1 | 2020 06 22T20 25 21 890Z Error Could not safely build a schema apollo 1 | at safelyBuildSchema apollo dist index js 129 11 apollo 1 | at process tickCallback internal process next tick js 68 7 Could not safely build a schema Error Could not safely build a schema apollo 1 | at safelyBuildSchema apollo dist index js 129 11 apollo 1 | at process tickCallback internal process next tick js 68 7 apollo 1 | 2020 06 22T20 25 21 890Z apollo 1 | Trying again in 3 seconds apollo 1 | apollo 1 | 2020 06 22T20 25 24 898Z Building schema apollo 1 | 2020 06 22T20 25 25 947Z Building schema complete apollo 1 | Server ready at rocket apollo 1 | 2020 06 22T20 25 26 076Z Sending telemetry to Prefect Technologies Inc source prefect server type startup payload id 5a9a3c85 cb0f 4f36 b5f2 f26fa264d3fd

Frank Lind · Answer

I turned on the debug for the graphql in the config file

Kyle Moon-Wright · Answer

Did you set the backend to server with `prefect backend server` before running `prefect server start` I ask because I am able to reproduce `FetchError request to <http graphql 4201 health> failed reason connect ECONNREFUSED 172 26 0 4 4201` while my backend is set to Cloud

Frank Lind · Answer

I had tried it Just repeated it and still get the same error trace

Frank Lind · Answer

base av developer ubuntu ~$ prefect backend server Backend switched to server base av developer ubuntu ~$ prefect server start Pulling postgres done Pulling hasura done Pulling graphql done Pulling apollo done Pulling scheduler done Pulling ui done Creating network prefect server with the default driver Creating tmp postgres 1 done Creating tmp hasura 1 done Creating tmp graphql 1 done Creating tmp scheduler 1 done Creating tmp apollo 1 done Creating tmp ui 1 done

Frank Lind · Answer

ui 1 | space invader space invader space invader UI running at localhost 8080 space invader space invader space invader apollo 1 | 2020 06 22T21 15 06 477Z Error fetching GraphQL health FetchError request to <http graphql 4201 health> failed reason connect ECONNREFUSED 172 27 0 4 4201 apollo 1 | 2020 06 22T21 15 06 478Z Error Could not safely build a schema apollo 1 | at safelyBuildSchema apollo dist index js 129 11 apollo 1 | at process tickCallback internal process next tick js 68 7 Could not safely build a schema Error Could not safely build a schema apollo 1 | at safelyBuildSchema apollo dist index js 129 11 apollo 1 | at process tickCallback internal process next tick js 68 7

Frank Lind · Answer

Hi I went to the developer instructions

Frank Lind · Answer

Frank Lind · Answer

and down into server services apollo and then did the npm install and start

Frank Lind · Answer

npm run start gt start home av developer Downloads prefect server services apollo gt nodemon exec babel node src index js nodemon 1 19 4 nodemon to restart at any time enter `rs` nodemon watching dir s src src nodemon watching extensions js mjs coffee litcoffee json py nodemon starting `babel node src index js` 2020 06 22T21 29 00 255Z Error fetching GraphQL health FetchError request to <http localhost 4201 health> failed reason connect ECONNREFUSED 127 0 0 1 4201 2020 06 22T21 29 00 266Z Error Could not safely build a schema at safelyBuildSchema home av developer Downloads prefect server services apollo src index js 126 11 at process tickCallback internal process next tick js 68 7 Could not safely build a schema Error Could not safely build a schema at safelyBuildSchema home av developer Downloads prefect server services apollo src index js 126 11 at process tickCallback internal process next tick js 68 7 2020 06 22T21 29 00 267Z Trying again in 3 seconds

Frank Lind · Answer

This time without any conda environment

Kyle Moon-Wright · Answer

Hey < Frank Lind> sorry to leave you hanging here I ll have to come back with answers for you as I have been encountering some weird behavior digging into this error If you are able to submit a it would be great to get more data on this any insight to narrow down the problem is greatly appreciated

Frank Lind · Answer

Hi Kyle Graphql Apollo service failure under Ubuntu 20 04 LTS 2842 now in Github

Kyle Moon-Wright · Answer

Fantastic thank you I ll be watching that one closely