Nomad Service Does Not Restart

Nomad
1

Below are the details related to nomad.
Part of a cluster, one of the client nodes with GPU is having this issue
Nomad v1.2.3 (a79efc8422082c4790046c3f5ad92c542592a54f)
Running on - Linux taitprod 5.4.0-135-generic #152~18.04.2-Ubuntu SMP Tue Nov 29 08:23:49 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

It was running fine, but needed to restart node service due to a change in client.hcl. On service restart kept getting the error below.

Any ideas besides reinstall nomad?

sudo systemctl status nomad.service
● nomad.service - Nomad
   Loaded: loaded (/etc/systemd/system/nomad.service; enabled; vendor preset: enabled)
   Active: activating (auto-restart) (Result: exit-code) since Sat 2022-12-31 14:04:51 EST; 1s ago
     Docs: https://www.nomadproject.io/docs/
  Process: 22551 ExecStart=/usr/local/bin/nomad agent -config /etc/nomad.d (code=exited, status=1/FAILURE)
 Main PID: 22551 (code=exited, status=1/FAILURE)

sudo journalctl -e -u nomad.service|grep error

Dec 31 14:03:30 taitprod nomad[20253]:     2022-12-31T14:03:30.485-0500 [ERROR] agent: error starting agent:
Dec 31 14:03:30 taitprod nomad[20253]:   error=
Dec 31 14:03:30 taitprod nomad[20253]:   | failed to create plugin loader: failed to initialize plugin loader: parsing plugin configurations failed: 1 error occurred:
2

Hello! It looks like the problem is in the configuration file (error parsing) – any way you can share the rest of the error and the change in the config file?

3

Thank you for your post. I figured that last night and it was with the image_delay value i had set. Looks like it understand hours, but I had days specified as the value. This fixed the issue.

1 Like