similar to: Vlad problems

Hey y''all: mongrel_cluster provides management tools for running Mongrel behind a reverse-proxy/load balancer. It is an extraction from Rails Machine, a deployment service and Ruby library that simplifies Rails application deployment. This release fixes bugs and adds a Capistrano task library. Changes: -changed pid file format to include port -only write configuration options

Paul Did you ever get to the bottom of this. I''m having a similar (though possibly different) problem with a Rails app failing occasionally and on just one mongrel instance, which from the trace and behaviour seems to be ImageSceince/RubyInline related. See my post on Rails deployment group:

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

I''ve been playing around with Vlad the deployer, and quite like it. However, has anyone used it to stop/start background rb processes via the ./script/backgroundrb script? Eric ----------------------------------------------------- Eric Pugh | Principal | OpenSource Connections, LLC | 434.466.1467 | http://www.opensourceconnections.com

I have CentOS 6 and with webmin/virtualmin panel, and each time that I reboot Apache can't start: Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80 (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down I do: netstat -tulpn| grep :80 tcp 0 0 :::80 :::* LISTEN

Hi LIst; I would like to bring apache up to listen on an lternate port (like 81 instead of 80) however if I change the listen value in the httpd.conf file then it fails to start saying that : (13)Permission denied: make_sock: could not bind to address :81 any Ideas??

If I do 'systemctl start httpd', apache will start right up. But during boot, it doesn't and I get the resulting errors below. Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address 10.20.30.11:80 Jun 15 21:17:28 dream httpd[1534]: no listening sockets available, shutting down Jun 15 21:17:28 dream httpd[1534]: AH00015:

Hi, We have seen this messages on one of our server. OS: CentOS 5.5 Processor: Xeon E5520 @ 2.27GHz Memory: 24 GB localhost ]# rpm -qa | grep httpd httpd-2.2.3-43.el5.centos.3 system-config-httpd-1.3.3.3-1.el5 httpd-devel-2.2.3-43.el5.centos.3 httpd-devel-2.2.3-43.el5.centos.3 Need help in collecting data and solve the issue. Below are the details message kernel: httpd[2090]: segfault at

Dear experts, Since I''ve moved my *puppetmaster* form SL5 (Scientific Linux) to SL6 with SELinux on, I''m facing loads of trouble. I also move away from WEBrick to apache/passenger, following the instruction here: http://projects.puppetlabs.com/projects/1/wiki/Using_Passenger > and I can''t start httpd any more. It fails with this: Starting httpd: (98)Address

Hi *, What''s the best way to find out on which port mongrel is running from within Rails? I have a cluster of mongrels behind a balancer (Pen) behind a webserver (Apache). In Rails, request.port return 80 and request.env[''SERVER_PORT''] returns 3000 (the port of Pen) Any ideas? Cheers, Max

Hey all, I'm having a little bit of a weird issue on my web host. I was just wondering if anyone's seen anything like this before. The problem is that you can't seem to restart apache via the stock init script that comes with apache: [root at beta:~] #service httpd restart Stopping httpd: [FAILED] Starting httpd: [Mon Mar 03 11:21:14 2014]

Hi, i restarted my apache and now im getting this error. Stopping httpd: [FAILED] Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80 no listening sockets available, shutting down Unable to open logs [FAILED] -------------- next part -------------- An HTML

Apache was working with self signed certificate. We changed the ssl.conf file to read certicates from godaddy and it it failed to restart because of incorrecrt parphrase. bash-3.2# /sbin/service httpd restart Stopping httpd: [ OK ] Starting httpd: Apache/2.2.3 mod_ssl/2.2.3 (Pass Phrase Dialog) Some of your private key files are encrypted for

hello, i'm starting/stopping icecast (1.3.11) & ices (0.2.2) from a web interface. fine so far, but now i see strange things: both ices & icecast, once started , (ices -B ... , icecast -b ...), both processes and their childs are listening also to port 80, besides their normal operation. i've found out because apache didn't restart (Address already in use: make_sock: could

Il 16/06/20 06:21, Gordon Messmer ha scritto: > On 6/15/20 7:06 PM, Jay Hart wrote: >> If I do 'systemctl start httpd', apache will start right up.? But >> during boot, it doesn't and I >> get the resulting errors below. >> >> Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested >> address: AH00072: make_sock: could >> not bind

Hi All, I'm trying to run multiple instances ( 2 ) of Apache on a single IP address. I need this because I need the two instances to run as different users. I've set up two config files with the following: config-1 config-2 ServerRoot "/etc/httpd" ServerRoot "/etc/httpd" Listen 10.220.1.156:80

Sent from my BlackBerry wireless device from MTN -----Original Message----- From: adekunleadekoya at gmail.com Date: Fri, 28 Sep 2012 18:49:33 To: <CentOS at mailing.list> Reply-To: adekunleadekoya at gmail.com Subject: Apache : Listen on ports other than 80 Hi, I just install centos 6.3 on my oracle virtualbox. I tried 2 configure apache 2 listen on port say 1010 but after adding a

On 6/15/20 7:06 PM, Jay Hart wrote: > If I do 'systemctl start httpd', apache will start right up. But during boot, it doesn't and I > get the resulting errors below. > > Jun 15 21:17:28 dream httpd[1534]: (99)Cannot assign requested address: AH00072: make_sock: could > not bind to address 10.20.30.11:80 httpd is starting before an interface has been configured with

Il 16/06/20 08:11, Alessandro Baggi ha scritto: > > > Il 16/06/20 06:21, Gordon Messmer ha scritto: >> On 6/15/20 7:06 PM, Jay Hart wrote: >>> If I do 'systemctl start httpd', apache will start right up.? But >>> during boot, it doesn't and I >>> get the resulting errors below. >>> >>> Jun 15 21:17:28 dream httpd[1534]:

> > > Il 16/06/20 08:11, Alessandro Baggi ha scritto: >> >> >> Il 16/06/20 06:21, Gordon Messmer ha scritto: >>> On 6/15/20 7:06 PM, Jay Hart wrote: >>>> If I do 'systemctl start httpd', apache will start right up.? But >>>> during boot, it doesn't and I >>>> get the resulting errors below. >>>>