joost baaij <[EMAIL PROTECTED]> writes:
> I'm a bit surprised I can't find anything about this in the mailing
> list archives.
So am I, because it's there.
> Basically since Mongrel 1.0.1 I've had Mongrels fall asleep without
> any real cause. A deep sleep, actually more like a coma. The mongre
On 2/2/07, Alan Maszt <[EMAIL PROTECTED]> wrote:
> I've upgraded from version 0.3.13.3 to 1.0.1 (along with dependencies). I can
> see service::install and service::remove commands, but not service::start and
> service::stop. Moreover, after installing the service with service::install,
> the se
On Feb 2, 2007, at 11:26 AM, Zed A. Shaw wrote:
> On Fri, 02 Feb 2007 14:43:29 +
> Tiago Macedo <[EMAIL PROTECTED]> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> I was wondering if this was a known issue or if anyone else had this
>> problem before. Maybe switching to Mongrel 1.0.1 with f
On Fri, 2 Feb 2007 08:51:42 -0800 (PST)
Alan Maszt <[EMAIL PROTECTED]> wrote:
> I've upgraded from version 0.3.13.3 to 1.0.1 (along with dependencies). I can
> see service::install and service::remove commands, but not service::start and
> service::stop. Moreover, after installing the service wi
I've upgraded from version 0.3.13.3 to 1.0.1 (along with dependencies). I can
see service::install and service::remove commands, but not service::start and
service::stop. Moreover, after installing the service with service::install,
the service shows up on the list in Control Panel/Administrativ
On Fri, 2 Feb 2007 12:10:03 +0100
joost baaij <[EMAIL PROTECTED]> wrote:
> *nix, Linux. No, not acts_as_ferret. I'm truncating log files
> manually every week or so, this has never been a problem anyway. Cpu,
> disk and network are all available in abundance.
>
> I couldn't say it also happen
On Fri, 02 Feb 2007 14:43:29 +
Tiago Macedo <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hey,
>
> I've been using Mongrel for quite some time now but I ran into an issue
> that threw me back to lighttpd + fastcgi.
>
> The application in question was runni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey,
I've been using Mongrel for quite some time now but I ran into an issue
that threw me back to lighttpd + fastcgi.
The application in question was running fine in the production
environment with SQLSessionStore and using a mongrel cluster behind
On 2/2/07, joost baaij <[EMAIL PROTECTED]> wrote:
> *nix, Linux. No, not acts_as_ferret. I'm truncating log files
> manually every week or so, this has never been a problem anyway. Cpu,
> disk and network are all available in abundance.
>
Are you using fastthread? Is mandatory since ruby leaks mem
*nix, Linux. No, not acts_as_ferret. I'm truncating log files
manually every week or so, this has never been a problem anyway. Cpu,
disk and network are all available in abundance.
I couldn't say it also happens with a single instance, but definitely
behind the load balancer. And then only
We'll probably need a bit more information here. Are you running on Windows
or *nix? Are you using acts_as_ferret? Are you letting Rails/Ruby rotate
log files? Does this occur with a single instance of Mongrel, or only
behind your load balancer? Do you snore at night? etc ;-)
On 2/2/07, joos
I'm a bit surprised I can't find anything about this in the mailing
list archives. Basically since Mongrel 1.0.1 I've had Mongrels fall
asleep without any real cause. A deep sleep, actually more like a
coma. The mongrel in question (I'm using a cluster of three) can not
be revived. A cluste
12 matches
Mail list logo
