Nomad: Version 0.5.0 rpc error: alloc lookup failed on command nomad logs or alloc-status

Created on 18 Nov 2016  路  2Comments  路  Source: hashicorp/nomad

If you have a question, prepend your issue with [question] or preferably use the nomad mailing list.

If filing a bug please include the following:

Nomad version

Only on v0.5.0

Operating system and Environment details

Debian8

Issue

When execute nomad logs or alloc-status command get

nomad logs fabio
Error querying allocation: Unexpected response code: 500 (rpc error: alloc lookup failed: index error: Invalid UUID: encoding/hex: invalid byte: U+0069 'i')

However status command is all good

Reproduction steps

As above

Nomad Server logs (if appropriate)

Nov 18 00:32:51 ip-172-31-0-25 nomad[787]: 2016/11/18 00:32:51.858783 [ERR] http: Request /v1/allocations?prefix=fabi, error: rpc error: alloc lookup failed: index error: Invalid UUID: encoding/hex: invalid byte: U+0069 'i'

Nomad Client logs (if appropriate)

Error querying allocation: Unexpected response code: 500 (rpc error: alloc lookup failed: index error: Invalid UUID: encoding/hex: invalid byte: U+0069 'i')

Job file (if appropriate)

NA

Most helpful comment

Oops ,I was mixed up with docker command .
Of course you have to have a allocation to get the log , all good.

Updated : actaully just found there also a option to use job name

nomad logs -stderr -f -tail -job fabio

Thanks
Kevin

All 2 comments

Hey nomad logs takes an allocation ID. "fabio" is the jobs name. I would run nomad status fabio and then get the allocation ID from there and run logs!

Let me know if you have any other questions!

Oops ,I was mixed up with docker command .
Of course you have to have a allocation to get the log , all good.

Updated : actaully just found there also a option to use job name

nomad logs -stderr -f -tail -job fabio

Thanks
Kevin

Was this page helpful?
0 / 5 - 0 ratings