-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NSSM wont install due to previous version running #14
Comments
since why run isn't supported i was able to fix this by modifying the default recipe and adding a notification on the remote_file resource to kill NSSM. i tried in another wrapper cookbook to subscribe to the resource but it did not work. |
Can you please submit a PR with the bug fix? Thanks in advance. |
its not elegant at all as most would not want to blindly force kill nssm in all cases just like that and potentially cause other issues. im not sure if theres a better solution to it, right now i needed to get it tot work for my use case but i will find some time to make a proper commit with a better solution that covers all use cases. just wanted to document here in case anyone else had ideas. ideally fixing the whyrun issue in #15 would essentially allow us to kill it ourselves with a notification making this a closed will not resolve issue since fixing whyrun is the best solution. |
given that whyrun is now supported and its easier to manage the services and kill them ourselves gracefully to allow for overwrites this issue is now irrelevant |
Since upgrading to the latest version of the cookbook, it keeps trying to install a newer version of NSSM and since NSSM is currently running it gets an access denied error trying to overwrite the file failing the chef run.
The text was updated successfully, but these errors were encountered: