Martin Felder
10/13/2021, 4:31 PMapollo_1 | PayloadTooLargeError: request entity too large
apollo_1 | at readStream (/apollo/node_modules/raw-body/index.js:155:17)
apollo_1 | at getRawBody (/apollo/node_modules/raw-body/index.js:108:12)
apollo_1 | at read (/apollo/node_modules/body-parser/lib/read.js:77:3)
apollo_1 | at jsonParser (/apollo/node_modules/body-parser/lib/types/json.js:135:5)
apollo_1 | at Layer.handle [as handle_request] (/apollo/node_modules/express/lib/router/layer.js:95:5)
apollo_1 | at trim_prefix (/apollo/node_modules/express/lib/router/index.js:317:13)
apollo_1 | at /apollo/node_modules/express/lib/router/index.js:284:7
apollo_1 | at Function.process_params (/apollo/node_modules/express/lib/router/index.js:335:12)
apollo_1 | at next (/apollo/node_modules/express/lib/router/index.js:275:10)
apollo_1 | at cors (/apollo/node_modules/cors/lib/index.js:188:7)
every 2 seconds or so. The server UI also does not seem to be running. Does anyone have an idea what this means?Zanie
10/13/2021, 5:04 PMZach Angell
10/13/2021, 6:08 PMMartin Felder
10/14/2021, 8:55 AM--external-postgres
option, so that's not it apparently. There are no flows or agents registered yet.Zach Angell
10/14/2021, 1:20 PMThere are no flows or agents registered yet.Hmm okay that's good to know. I'm trying to figure out what's hitting the Prefect Server API with large requests π€ I'll try to reproduce on my end
prefect
0.15.6 + prefect server start
works as expected for me. Is there something else that could be hitting your server api or any other unique features of your server setup?Martin Felder
10/18/2021, 6:51 AMZach Angell
10/18/2021, 1:42 PM:space_invader::space_invader::space_invader: UI running at localhost:8080 :space_invader::space_invader::space_invader:
Maybe the PayloadTooLargeError
is just a red herringMartin Felder
10/20/2021, 10:04 AMconfig.toml
as stated above and adding the --expose
flag to prefect server start
, which I understand I'm supposed to do at 0.15.5+, I'm still getting
ui_1 | Missing the PREFECT_SERVER__BASE_URL environment variable. Using default
ui_1 | πΎπΎπΎ UI running at localhost:8080 πΎπΎπΎ
Setting export PREFECT_SERVER__BASE_URL=<http://172.16.18.70>
changes nothing, neither does adding -v master -uv master
to the server start. Strangely enough, the expose flag does not appear when I run perfect server start --help
, although I seem to be using the correct executable:
$ conda env list
# conda environments:
#
base /opt/miniconda
ws_prefect * /opt/miniconda/envs/ws_prefect
$ which prefect
/opt/miniconda/envs/ws_prefect/bin/prefect
$ conda list | grep prefect
# packages in environment at /opt/miniconda/envs/ws_prefect:
prefect 0.15.6 pyhd8ed1ab_0 conda-forge
What am I doing wrong?Zach Angell
10/20/2021, 1:28 PMUI running at localhost:8080
message is also a red herring, it doesn't log the actual UI url thereprefect server start --expose
?Martin Felder
10/20/2021, 2:27 PMZach Angell
10/20/2021, 4:41 PM