Gremlin not accepting changes to config.yaml file

Modified on Tue, 18 Oct, 2022 at 4:49 PM

Issue: After restarting Gremlin daemon and making changes to config.yaml file, the changes are not reflected in agent. 


 


Cause: After the .credentials file is configured for the first time, Gremlin will give it precedent when reading the config files on start up. 


 


Resolution: After making a change to the config.yaml file, delete the .credentials file and then restart the gremlin daemon. The config.yaml file will be read and a new .credentials file will be created. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article