** Ruby version is not up-to-date; loading cgi_multipart_eof_fix
** Starting Mongrel listening at 0.0.0.0:3000
** Changing group to mongrel.
** FAILED to change user:group mongrel:mongrel: Operation not permitted
I ran into something similar a few weeks ago. I ended up running my
mongrel with www-data instead of mongrel as the user/group since
that’s what my nginx runs as. (not sure if that’s bad… anyone?)
I’m trying to start mongrel, but this time as user mongrel:
mongrel_rails start --user mongrel --group mongrel
** FAILED to change user:group mongrel:mongrel: Operation not permitted
A process needs to start under root to be allowed to change their
effective user id like this. So, try “sudo mongrel_rails start --user
mongrel --group mongrel”.
OK, thank you. That made sense… I’ll see how everything goes with
capistrano etc. Maybe there’ll be some problems because of this sudo…
but I’ll find out soon enough…
For now I have another question… It’s regarding stale PID files… the
solution is here:
but I don’t know where exactly to add this… if I look at the patch -
this line for example: “config =
Mongrel::Rails::RailsConfigurator.new(settings) do”. It seems to me that
this should exist in my file… right? And it doesn’t…
I don’t want to apply this patch blindly (maybe it’s for different
version than 1.01). And since I don’t know a whole lot about patches,
I’d like to ask you how exactly do I do that… thank you!
david
I’m trying to start mongrel, but this time as user mongrel:
mongrel_rails start --user mongrel --group mongrel
** FAILED to change user:group mongrel:mongrel: Operation not permitted
A process needs to start under root to be allowed to change their
effective user id like this. So, try “sudo mongrel_rails start --user
mongrel --group mongrel”.