similar to: can''t get mongrel to work as daemon

Displaying 20 results from an estimated 20000 matches similar to: "can''t get mongrel to work as daemon"

2010 May 10
1
Rails/mongrel/httpd issue - F13, rails 2.3.5
Hi, I have an issue with mongrel and rails. I add -B option(debug) to mongrel_rails in /etc/init.d/mongrel-rails but it didn't display more logs : http://ovirt.pastebin.com/N5v94cTu This is the page I get when I try to reach the ovirt web interface, I see the html tags (kerberos auth is working) : <html><body>You are being <a
2007 Jun 15
1
mongrel cluster issues, plain old mongrel OK
I just created a test rails app, and am having very wierd issues with mongrel cluster. Here''s what I''m doing: rails test sudo chown -R mongrel:mongrel test cd test sudo mongrel_rails \ cluster::configure -e production \ -p 8000 -N 3 -a 127.0.0.1 --user mongrel \ --group mongrel It correctly writes the mongrel_cluster.yml file to the config directory. Now,
2010 Jun 13
5
script/server vs mongrel_rails start issue
I am having different results between when I start mongrel with script/ server and with mongrel_rails start. When I run script/server to boot mongrel everything runs fine, no errors. When I run mongrel_rails start I get the following errors - verified the problem on a fresh app and on two different environments (mac and yes, windows server 2008). The actual line of fault changes but the problem
2009 Feb 18
1
Linux ps reports mongrel as [ruby18]
I''m running two sets of mongrels using mongrel 1.1.4, one for production one for staging. When executing ''ps'' from a linux shell, the production mongrels report as expected, however the staging processes are listed as [ruby 18]. The result seems to be that mongrel_rails cannot stop the staging processes because it doesn''t recognize [ruby18] as a mongrel
2006 Nov 30
1
Restarting mongrel cluster from other directories
I want to restart my Mongrels from crontab periodically to free up memory. I tried this: [admin at mudcrapce ~]$ mongrel_rails cluster::restart -C /var/www/apps/mudcrapce/current/config/mongrel_cluster.yml Restarting 5 Mongrel servers... mongrel_rails restart -P log/mongrel.3040.pid !!! PID file log/mongrel.3040.pid does not exist. Not running? mongrel::restart reported an error. Use
2008 Jan 30
3
Not all mongrel starting (Errno:EEXIST)
I''m playing with the mongrel clustering, and am having a problem getting 2 mongrels to start up reliably. This should be a pretty simple cluster, with just 2 instances running. My mongrel config (mongrel_cluster.yml) looks like: cwd: /deployment/installed/myapp/current log_file: log/mongrel.log port: "8000" environment: production address: 127.0.0.1 pid_file:
2007 Dec 11
2
Mongrel not starting: `initialize_without_backlog'': Cannot assign requested address - bind(2) (Errno::EADDRNOTAVAIL)
Hi I have a rather strange problem with mongrel and I would be grateful if anyone could assist me with resolving. I have an application running mongrel 1.1.1 and rails 1.2.5 with ruby 1.8.6. It was all working fine and starting as expected. But I did a server reboot once and mongrel has refused to start up since. I get the following error:
2006 Aug 10
7
mongrel stops responding after period of no use
I just moved from apache2/fcgi to apache2.2/mongrel and everything seems to work great except for 2 issues, one being major and one minor. the major issue i am experiencing is that after a period of time where my rails apps are not used, typically overnight, the mongrel processes become unresponsive. I currently have 3 apps running behind an apache2.2 proxy. every morning when i come in to
2007 Feb 02
1
Monit / mongel_cluster 0.2.2 / mongrel 1.0.1
Hi, I''ve a few problems with my rails app at the minute, causing mongrels in a cluster to die, while I debug I''ve setup monit to keep the site running. Problem is, whenever monit starts one of my mongrels via mongrel_rails cluster::start --only 8000 --clean -C /url/to/yml/file I get the following in my log/mongrel.log: ** Mongrel available at 127.0.0.1:8000 ** Writing PID file
2009 Jan 01
1
gem_original_require no such file to load -- /var/www/vhosts/gophotoswap.com/httpdocs/current/config/environment ( LoadError )
** Daemonized, any open files are closed. Look at /var/www/vhosts/ gophotoswap.com/httpdocs/shared/pids/mongrel.8000.pid and /var/www/ vhosts/gophotoswap.com/httpdocs/shared/log/mongrel.8000.log for info. ** Starting Mongrel listening at 127.0.0.1:8000 ** Initiating groups for "mongrel":"mongrel". ** Changing group to "mongrel". ** Changing user to
2007 Sep 17
4
Mongrel clusters are not being started on reboot
I''ve done a clean install of Ubuntu 7.04 server in 2 different machines and everytime I reboot the machine or manually run /etc/ init.d/mongrel_cluster restart/start the mongrels won''t start correctly. I have to manually start them by using mongrel_rails cluster::start from each app folder. I''ve been searching around and it looks like mongrel has some problems
2007 Aug 10
10
what is the correct way to stop/start a mongrel instance using monit with mongrel cluster
Hi -- I have been reading documentation and googling around to find the correct way to do this but I have found many ways that seem to not work, or the documentation makes no reference to. I am using mongrel cluster with 10 mongrels for each server. Recently I installed monit but which lead me to find the correct way to start/stop mongrel instances one pid at a time. I am assuming one pid at a
2008 May 30
3
Mongrel error since updating to OSX 10.5.3
Howdy, I''m getting an error message when trying to run one of my rails apps, which seems to have started after updating to 10.5.3. mattdaw-2:v1.5_patch mdaw$ mongrel_rails start ** Starting Mongrel listening at 0.0.0.0:3000 ** Starting Rails with development environment... /usr/local/ruby-patched/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../ lib/mongrel/tcphack.rb:12:in
2007 Oct 28
2
cluster::restart doesn''t wait for stop before starting
Hi, I''m calling restart from my Capistrano task. I have this in my deploy.rb file: # until mongrel_cluster updates to cap2... namespace :deploy do task :start, :roles => :app do start_mongrel_cluster end task :stop, :roles => :app do stop_mongrel_cluster end task :restart, :roles => :app do restart_mongrel_cluster end end (What''s the scoop on
2006 Sep 22
3
Mongrel spinning on read_multipart
On Zed''s suggestion, I caught two new spinning mongrels and sent a SIGUSR2. The code appears to be stuck in read_multipart for both processes: # kill -USR2 6109 ** USR2 signal received. Thu Sep 21 14:55:39 EDT 2006: Reaping 1 threads for slow workers because of ''shutdown'' Thread #<Thread:0x419d7ce0 run> is too old, killing. Waiting for 1 requests to finish, could
2008 Jan 31
1
Production problem for mongrel
Hi, I am working on deplying my Rail app to QA and then move to production. Since on our QA servers, there is no internet access and also for production servers, internet access is strictly prohibited. As a result, there is no way to install mongrel by use "gem install mongrel" command. The first option I tried is to put mongrel and all other gems under the vendor directly in my app,
2007 Jul 16
2
mongrel_rails start working mongrel_rails cluster::start not working
Hi everybody, I have installed mongrel and mongrel cluster in a new linux box .... at the end of the day I was able to lunch mongrel (mongrel_rails start -e production) and all is working fine with. However, when I tried to set a mongrel cluster the command mongrel_rails cluster::start get the following output : starting port 8000 starting port 8001 starting port 8002 But when I lunched the
2010 Sep 22
12
Mongrel service
Hi all Environment: Windows 7 64 bit Ruby 1.9.2.p0 Rails 3 I am getting the following error when I run the following command mongrel_rails service::install -N MyTestApp_4001 -p 4001 -e production: "Msvcrt-ruby18.dll is missing" Thanks in advance Gerhard -------------- next part -------------- An HTML attachment was scrubbed... URL:
2007 Mar 29
10
Mongrel Service won''t start on windows
64bit Intel 8 CPU server Windows 2003 Server Service set to run as LocalSystem, doesn''t work as user account either The error we see is: "Service failed to start in a timely..." Which I have seen in the past email trails as working The app works from mongrel_rails start and from mongrel_service console -N servicename -p 3000 -c c:\rails_apps\appname -e production We upgraded
2006 Sep 01
2
Making Mongrel play well with Monit
Hi! I run a mongrel cluster with 6 mongrels in it. I want to monitor them individually for process hangs (and then restart them) and this is the solution I came up with: Here''s my configuration file for monit (/usr/local/etc/monitrc): [snipped relevant bits] ------ #check lighttpd process check process lighttpd with pidfile /var/run/lighttpd.pid start program =