Skip to content
This repository has been archived by the owner on Oct 21, 2020. It is now read-only.

Executing COSI against a non-production environment may introduce config issues #38

Open
kamelkev opened this issue Sep 8, 2017 · 0 comments

Comments

@kamelkev
Copy link

kamelkev commented Sep 8, 2017

Recently was executing COSI from a Debian 8 virtual machine in combination with the --apiurl argument to point the requests at my development environment.

During this exercise I noticed that upon successful execution of COSI that no nad.js process appeared to be executing.

Upon investigation we found that the NAD_API_URL config variable within nad.conf was unpopulated. One would expect to find the --apiurl value here, but instead the default value was used instead.

Populating that config variable and restarting nad with systemctl start nad resulted in the process starting as expected.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant