Skip to content
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

Error message when running the server enable action on windows #436

Closed
brentm5 opened this issue May 17, 2017 · 3 comments
Closed

Error message when running the server enable action on windows #436

brentm5 opened this issue May 17, 2017 · 3 comments

Comments

@brentm5
Copy link

brentm5 commented May 17, 2017

We are using a relatively older version of this cookbook (1.4.3) and today we started seeing an error which was really vague. Ended up tracking it down to the new version of nssm. It might make sense to actually lock this cookbook down to at least be ~> 2.0. I am not sure if any other versions were affected by this as well however.

==============================================================
           Error executing action `enable` on resource 'consul_service[consul]'
==============================================================
           ArgumentError
           -------------
           wrong number of arguments (1 for 0)

brentm5 added a commit to brentm5/consul-cookbook that referenced this issue May 17, 2017
Fixes sous-chefs#436 by keeping the the nssm cookbook under 3.0.0
@legal90
Copy link
Contributor

legal90 commented May 18, 2017

@brentm5 Have you tried the latest state of consul cookbook from master branch?
It should be fixed by #422 (not released yet)

@brentm5
Copy link
Author

brentm5 commented May 18, 2017

Nope, but if that solves the issue its good enough for me. I just didn't see a fix anywhere. Ill go ahead and close out my PR as well.

@brentm5 brentm5 closed this as completed May 18, 2017
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants