https://prefect.io logo
Powered by
Title
l

Lon Nix

11/02/2021, 8:58 PM
Any idea what this means? It's in the 
Failed flows
section of the dashboard. I can't find any errors in pod logs 
Something went wrong while trying to fetch failed flow information. Please try refreshing your page. If this error persists, return to this page after a few minutes.
a

Anna Geller

11/02/2021, 9:08 PM
that’s interesting, thanks for sharing. I don’t want to prematurely judge why this might be happening but maybe some delay in fetching flow information from the pods? Could you share a screenshot of the UI? Does it happen again after refreshing the UI? It could be a flow heartbeats issue, too…
l

Lon Nix

11/02/2021, 9:10 PM
its consistent and has been happening since the initial setup earlier today
I'm not even sure where to look for this. Is it trying to pull from the postgres db here? Where is the info coming from and going to?
a

Anna Geller

11/02/2021, 9:14 PM
in which part of the UI did you see the error? was it here?
l

Lon Nix

11/02/2021, 9:14 PM
yup!
I'm wondering if there is just a bigger issue of not being able to read flow data. Everywhere I should see flows I don't see anything or I see that error. I have verified the database is being written to but is it possible its not being read from properly?
a

Anna Geller

11/02/2021, 9:20 PM
if I’m not mistaken it’s built based on this query: https://github.com/PrefectHQ/ui/blob/master/src/graphql/Agent/table-flow-runs.gql So it basically retrieves the information about failed flow runs from the backend and displays them there. Perhaps you can try exploring the same information using GraphQL to check if the UI is the issue here?
l

Lon Nix

11/02/2021, 9:20 PM
I'll check. Thanks
@Xinchi He ^^^
definitely some issues there 
{
  "errors": [
    {
      "message": "expected a list, but found null",
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "path": [
        "flow_run"
      ],
      "extensions": {
        "path": "$.selectionSet.flow_run.args.where.state._in",
        "code": "validation-failed",
        "exception": {
          "message": "expected a list, but found null"
        }
      }
    }
  ],
  "data": null
}
it says validation failed but doesn't say what it tried to validate to or with. Any thoughts?
👍 1
a

Anna Geller

11/02/2021, 9:27 PM
I sometimes get UNAUTHENTICATED as API response when I’m logged in for a long time. Sometimes refreshing a UI may help, but not sure how it works with Server
but thanks for checking that and keep me posted when you find out more
x

Xinchi He

11/02/2021, 9:37 PM
I am on the same team as @Lon Nix. We also cannot see flows for a project under the 
FLOWS
tab, it says 
You have no flows in this project!
, but we can see the flow from the left tab (like a file explorer). In addition, when the flow runs the live log section show nothing, simply just keep loading forever. Any thoughts or insights here? Thanks a lot!
l

Lon Nix

11/02/2021, 9:57 PM
The issue was a version mis-match. I put hasura at v2.0.10 because its a newer tag. When I went back to the default value of the helm chart, v1.3.3, it started working (I had to drop and re-create the db though)
👏 2
new issue: when the job executes (that's happening now) it just prints the prefect help output then exits. The job template we're using specifies 
command: ["/bin/sh", "-c"]
          args: ["prefect execute flow-run"]
but the output is just 
Usage: prefect [OPTIONS] COMMAND [ARGS]...

  The Prefect CLI for creating, managing, and inspecting your flows.

  Note: a Prefect Cloud API token is required for all Cloud related commands. If a token
  is not set then run `prefect auth login` to set it.

  Query Commands:
      get         List high-level object information
      describe    Retrieve detailed object descriptions

  Action Commands:
.......
a

Anna Geller

11/02/2021, 10:21 PM
maybe you can specify the API endpoint to ensure it looks for your Server endpoint rather than Cloud? it looks like it tries to access Cloud endpoint 
export PREFECT__CLOUD__API="<http://hostname/graphql>"
l

Lon Nix

11/02/2021, 10:26 PM
we got past it by removing some of our custom job template spec. Now we're back to the 
Failed to load and execute Flow's environment: HTTPUnauthorized('No valid credentials provided')
error again (but this time its showing in the ui like it should)
its got to be an issue with our connection to github
a

Anna Geller

11/02/2021, 10:28 PM
if you need some examples how to set it up: https://github.com/anna-geller/packaging-prefect-flows/tree/master/flows you need personal access token, and if you store it as PrefectSecret, then it should be straightforward to configure
k

Kevin Kho

11/02/2021, 10:33 PM
If you want to try a flow I have on Github that is public you can use this. I agree with the assessment it could be the Github credentials though
x

Xinchi He

11/02/2021, 10:34 PM
Thanks @Anna Geller and @Kevin Kho . I think we are using the SSH key + Git storage approach.
k

Kevin Kho

11/02/2021, 10:36 PM
Just makign sure you’ve seen these docs ?
x

Xinchi He

11/02/2021, 10:38 PM
Thanks @Kevin Kho, it seems we need to build a customized image with 
openssh_client
installed.
2 Views
#prefect-serverJoin Slack
Powered by