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

Log Jobs activity from the Controller node #119

Open
luiztauffer opened this issue Jan 13, 2024 · 1 comment
Open

Log Jobs activity from the Controller node #119

luiztauffer opened this issue Jan 13, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@luiztauffer
Copy link
Collaborator

It might be interesting to log the activity for jobs from the controller node, this will help us catch errors that happen before the dendro processes run inside a successfully started job.

For example, I just got a Batch job failing right before the start, some authorization issue when pulling the docker image... the Dendro logs are empty, but I can find the source of error using boto3:

batch_client.describe_jobs(jobs=['4f9aa92c-966a-48f0-894f-444c9859cdb3'])
'status': 'FAILED',
   'attempts': [{'container': {'containerInstanceArn': 'xxxxxxxxxxxxxxxxxxx',
      'taskArn': 'xxxxxxxxxxxxxxxxxxxxxxxxx',
      'reason': 'CannotPullContainerError: Error response from daemon: Head "https://ghcr.io/v2/catalystneuro/dendro_si_kilosort25/manifests/latest": unauthorized',
    },
@magland
Copy link
Collaborator

magland commented Jan 13, 2024

So I think we'll need to store the aws batch job id in the dendro job record.

@luiztauffer luiztauffer added the enhancement New feature or request label Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants