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

Can not input sudo password when run foreman:restart #9

Open
yesmeck opened this issue Jun 17, 2013 · 9 comments
Open

Can not input sudo password when run foreman:restart #9

yesmeck opened this issue Jun 17, 2013 · 9 comments

Comments

@yesmeck
Copy link
Contributor

yesmeck commented Jun 17, 2013

Hello, I'm using the master branch. When I run foreman:restart, capistrano will hang when prompting for sudo password.
Should we use foreman_sudo here?
https://github.com/hyperoslo/capistrano-foreman/blob/master/lib/capistrano/foreman.rb#L28

@jgorset
Copy link
Contributor

jgorset commented Jun 17, 2013

Hi @yesmeck,

I'm not sure that will help. Capistrano isn't particularly great with input, so I think you will have to configure your sudoers file so that the command won't prompt for a password (see NOPASSWD).

@yesmeck
Copy link
Contributor Author

yesmeck commented Jun 17, 2013

Yes, NOPASSWORD is a solution.

But if I chang this line:

run "sudo service #{options[:app]} start || sudo service #{options[:app]}  restart"

to

run "#{foreman_sudo} service #{options[:app]} start || #{foreman_sudo} service #{options[:app]}  restart"

and

set :foreman_sudo, "rvmsudo -p 'sudo password: '"

Capistrano also will works.

@mcfiredrill
Copy link

I have the same problem. In fact, I think you should just use #{sudo} and use the global capistrano sudo setting.

@jgorset
Copy link
Contributor

jgorset commented Sep 1, 2013

I'd really like to implement this, @mcfiredrill, but I can't find any documentation on a sudo variable — could you direct me?

@glaszig
Copy link
Contributor

glaszig commented Dec 30, 2013

@jgorset this?

@ralfthewise
Copy link

+1 since upstart supports user jobs and the newer session jobs, you can run upstart jobs without using sudo at all

@glaszig
Copy link
Contributor

glaszig commented Feb 5, 2014

@ralfthewise erm, user/session jobs only start when a user logs in and starts some sort of x session, no? i don't think upstart iterates all users of the system and loads their jobs...

@ralfthewise
Copy link

No, they're just like usual upstart jobs except they run in the context of an unprivileged user. See http://upstart.ubuntu.com/cookbook/#user-job and http://upstart.ubuntu.com/cookbook/#session-job

@glaszig
Copy link
Contributor

glaszig commented Feb 5, 2014

section Session Job:

[...] Session Jobs are not managed by Upstart running as PID 1 - they are managed by the users own Session Init.

section Session Init:

Traditionally, this job has been handled by applications such as "gnome-session" [...]

and then below in section Non-graphical Sessions:

However, what if you want to use a Session Init on a server? This is not fully supported right now, but can be achieved as follows.

Create two System Job similar to the following...

so, as i understand it, those jobs won't be started upon boot but only when the user actively initiates such a session by, e.g., launching gnome or some other tool which in turn only happens when you login.

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

5 participants