grailbio / reflow

A language and runtime for distributed, incremental data processing in the cloud
Apache License 2.0
965 stars 52 forks source link

reflow logs fails with invalid URI #142

Open elimoss opened 3 years ago

elimoss commented 3 years ago

I'm trying to view the logs for a running job by providing the URI I get from reflow ps -l to reflow logs:

reflow logs ec2-44-233-146-173.us-west-2.compute.amazonaws.com:9000/f5439b80e833dfe8/259f67dde686b629aef272b3e9ab876fb7bc66358fba2011b83272d993532e11

and I get the strangely repetitive

alloc f5439b80e833dfe8: alloc f5439b80e833dfe8: invalid URI

Any ideas?

Thanks in advance for your help!

swami-m commented 3 years ago
reflow logs ec2-44-233-146-173.us-west-2.compute.amazonaws.com:9000/f5439b80e833dfe8/259f67dde686b629aef272b3e9ab876fb7bc66358fba2011b83272d993532e11

Can you clarify what version you are running ? (ie, output of)

> reflow version

I think some recent changes might've made it not possible to access those logs through the URI. Alternately, can you try if either of the following work ?

> reflow logs 259f67dd
> reflow logs 259f67dde686b629aef272b3e9ab876fb7bc66358fba2011b83272d993532e11

I suspect it might not, given your other question #141

Since you are trying to look for the logs of a particular exec, in the logs of the reflow run, you'll see the following:

stdout location: (cloudwatch) LogGroupName: reflow, LogStreamName: ...
stderr location: (cloudwatch) LogGroupName: reflow, LogStreamName: ...

You can access the logs through AWS console. Even if you don't see the output above, the stream name should be (in your above example)

and I get the strangely repetitive

Looking at the code, this is expected. (the first part is coming from the client while the second part is returned by the server)