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

Unable to connect to Upstart Ubuntu 15.10 #734

Closed
richardmcsong opened this issue Jan 8, 2016 · 4 comments
Closed

Unable to connect to Upstart Ubuntu 15.10 #734

richardmcsong opened this issue Jan 8, 2016 · 4 comments

Comments

@richardmcsong
Copy link

Hi, while running "include nginx" it returns this error:

Error: /Stage[main]/Nginx::Service/Service[nginx]: Could not evaluate: Execution of '/sbin/status nginx' returned 1: status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Error: /Stage[main]/Nginx::Service/Service[nginx]: Failed to call refresh: Execution of '/sbin/status nginx' returned 1: status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
Error: /Stage[main]/Nginx::Service/Service[nginx]: Execution of '/sbin/status nginx' returned 1: status: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

I know Ubuntu 15 relies on systemd now... is there a way to get puppet to use systemctl status nginx?

@3flex
Copy link
Contributor

3flex commented Jan 9, 2016

This should be handled by Puppet itself (it should try using systemd on supported systems). This module's not doing anything custom with the service unless configtest_enable parameter is set to true, but I don't think that's what's happening here.

Are you using Puppet from the distro or upstream? Which version?

@richardmcsong
Copy link
Author

im using the puppet from the distro, version 3.7.2

@3flex
Copy link
Contributor

3flex commented Jan 12, 2016

Are you being affected by this bug? https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1457957

@richardmcsong
Copy link
Author

hmm good point! i aliased my status, start and end commands... and puppet doesn't seem to be erroring anymore. Thanks!

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

No branches or pull requests

2 participants