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

Cannot open log/postrunjson files previously viewed #226

Closed
minneker opened this issue Aug 19, 2019 · 2 comments
Closed

Cannot open log/postrunjson files previously viewed #226

minneker opened this issue Aug 19, 2019 · 2 comments

Comments

@minneker
Copy link

When running the command: tibanna log --job-id=JOBIDHERE, I get the message: log/postrunjson file is not ready yet.Wait a few seconds/minutes and try again. which I understand is expected behavior. However, I get this message on log files I have already viewed previously. I am not sure if this is a client-side error or not, but I did not expect to see this message for log files I have previously viewed. Thank you!

@SooLee
Copy link
Member

SooLee commented Aug 19, 2019

It should work on previously viewed files. I can think of a couple of possible scenarios.

  1. the log/postrunjson file on s3 has been deleted manually (Tibanna does not delete them). This can be checked by either awscli (aws s3 ls s3://<logbucket>/<jobid>.log) or checking the S3 bucket on the browser.
  2. multiple step functions are being used and the job was run on a step function different from the currently set TIBANNA_DEFAULT_STEP_FUNCTION_NAME. In this case, tibanna log --job-id=<jobid> --sfn=<stepfunctionname> should work.

Could it be either of these cases?

@minneker
Copy link
Author

I have been unable to recreate the issue and it has not resurfaced since. I will keep an eye out, closing for now. Thank you for your prompt response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants