Closed Dirrk closed 5 years ago
This issue was due to the meta variable "solr_cluster" not existing in the previous job. When it did work, I had it commented out and setup for json-file logging to view the logs in the ui. This was a known problem and not an issue with nomad.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
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
Output from
nomad version
Nomad v0.9.3 (c5e8b66c3789e4e7f9a83b4e188e9a937eea43ce)Operating system and Environment details
Linux ip-10-... 4.4.0-1084-aws #94-Ubuntu SMP Fri May 17 13:10:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
docker version
Issue
I have a cron job that will fail when running the allocation with an error (fails every time on any box). The error shows up on the client side and looks like this:
However, I changed the job Id by adding a -2 to the end of the job name and the failure does not happen. The -2 version of the job is the exact same job file as shown below but works without issue. I tried just stopping the original and then running garbage collection (the job no longer showed up and plan shows new job) but when I run that job again with the same Id it still fails every time. I think there is something stored incorrectly in the server db and I cannot reproduce it except for using the same job Id.
Reproduction steps
Specific to my cluster and I am not sure what data to give you to help you debug this.
Job file (if appropriate)
Failing job:
working job:
Nomad Client logs (if appropriate)
If possible please post relevant logs in the issue.
Logs and other artifacts may also be sent to: nomad-oss-debug@hashicorp.com
Please link to your Github issue in the email and reference it in the subject line:
Emails sent to that address are readable by all HashiCorp employees but are not publicly visible.
Nomad Server logs (if appropriate)
I have taken the snapshot from the server and copied it locally, I can send it to you if needed, but I will also perform additional testing if given feedback. I can reproduce this 100% of the time and my current work around (the new job id works fine)