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.

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

logs of sim4life jobs not appearing in UI logs #5336

Closed
Tracked by #950 ...
sanderegg opened this issue Feb 15, 2024 · 2 comments
Closed
Tracked by #950 ...

logs of sim4life jobs not appearing in UI logs #5336

sanderegg opened this issue Feb 15, 2024 · 2 comments
Assignees
Labels
a:apiserver api-server service a:dask-service Any of the dask services: dask-scheduler/sidecar or worker a:director-v2 issue related with the director-v2 service

Comments

@sanderegg
Copy link
Member

sanderegg commented Feb 15, 2024

  • start sim4life
  • create solver jobs
    --> no logs appear in the osparc logs tab
@sanderegg sanderegg self-assigned this Feb 15, 2024
@sanderegg sanderegg transferred this issue from ITISFoundation/osparc-issues Feb 15, 2024
@sanderegg sanderegg added a:director-v2 issue related with the director-v2 service a:apiserver api-server service a:dask-service Any of the dask services: dask-scheduler/sidecar or worker labels Feb 15, 2024
@sanderegg sanderegg added this to the Schoggilebe milestone Feb 15, 2024
@sanderegg
Copy link
Member Author

steps taken to reproduce.

local testing:

  • start osparc in devel mode
  • start a jupyter notebook in osparc
  • connect to the local api-server via osparc python library and send jobs, "simulating"
    --> logs are visible in the UI

tested in sim4life.io

  • start sim4life.io
  • start jupyter inside sim4life.io
  • run the same code as above, using the ENVs given to have the node_id in the project_metadata
    --> logs are invisible in the UI! Also the comp_runs table shows that the project metadata are not sent to the computational backend

tested in AWS-master

  • same procedure as in sim4life.io
    --> logs are visible in the UI! seems to be fixed.
    to be confirmed by @mguidon

@sanderegg
Copy link
Member Author

s4l is starting the job prior to setting the project metadata, therefore no logs are streamed back.
changing that lead to some issues as director-v2 complains when the node_id in the metadata is unknown. This is fixed by #5432

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:apiserver api-server service a:dask-service Any of the dask services: dask-scheduler/sidecar or worker a:director-v2 issue related with the director-v2 service
Projects
None yet
Development

No branches or pull requests

2 participants