dhogaza@PACIFIER.COM wrote:
I have three servers running identical installations of
AOLserver/3.3.1+ad13. On two (development and production, very low and
relatively low traffic volumes respectively) all scheduled procs have
stopped firing.
My God, it sounds to me like you're all being
dhogaza@PACIFIER.COM wrote:
My God, it sounds to me like you're all being bit by the Y2.006K
problem! :)
That answer is closer than you think (at least if everyone is having the
same problem I was) ... actually it's Y2.038K
Yes, indeed, I suspect everyone here on the list is aware of the
Zachary Shaw wrote:
before may 13th nanosleep was in the form
[pid 614] nanosleep({0, 34478}, unfinished ...
after the 12th there were nanosleeps in the form
[pid 614] nanosleep({9, 934211000}, unfinished ...
This looks like a blatant clue -- to someone who understands
In addition to the below, there are at least two of us over at
openacs.org reporting that scheduled procs stopped firing over the
weekend. I have one site left on 3.3+ad13 and the other guy says he
has 3.2+ad12.
This site hasn't been upgraded because the client didn't want to
upgrade,
By the way, one more thing: I have three sites running on this
server - staging, live and an old keepalive instance. The live site
is the only one exhibiting the scheduled proc problem; it's also the
only one that gets any significant traffic. So I'm thinking it's
some kind of overflow
Janine,
Are these completely unrelated installs wrt Guan's sites?
I seem to have forgotten exactly why it is difficult or time consuming to
upgrade from 3.x to 4.x. Does anyone have a summary of the problems?
tom jackson
On Tuesday 16 May 2006 00:10, Janine Sisk wrote:
In addition to the
I realized after I sent this last night that the other two sites are
probably still working because they haven't been restarted in quite a
while. The live site gets restarted fairly frequently, so it started
exhibiting the problem right away.
janine
On May 16, 2006, at 12:18 AM, Janine
Tom,
Janine's sites are completely unrelated with mine. And I've seen this
problem on three different unrelated sets of servers.
Our upgrade from 3.x to 4.x was not that painful, the most time-
consuming part was rewriting approximately 35 configuration files for
the tons of services we
Janine Sisk wrote:
In addition to the below, there are at least two of us over at
openacs.org reporting that scheduled procs stopped firing over the
weekend. I have one site left on 3.3+ad13 and the other guy says he
has 3.2+ad12.
I have three servers running identical installations of
[EMAIL PROTECTED] wrote:
Janine,
Are these completely unrelated installs wrt Guan's sites?
I seem to have forgotten exactly why it is difficult or time consuming to
upgrade from 3.x to 4.x. Does anyone have a summary of the problems?
tom jackson
On Tuesday 16 May 2006 00:10, Janine Sisk
On May 16, 2006, at 8:04 AM, Nathan Folkman wrote:
It's been a while, and I'm still on my first cup of coffee, but I
think your biggest hurdle is probably going to be the loss of
ns_share in favor of nsv. Also 4.x requires Tcl 8.x. Hope that
helps!
Ugh. You're absolutely right - this
On 16 May 2006, at 17:04 , Janine Sisk wrote:
On May 16, 2006, at 6:57 AM, Tom Jackson wrote:
Are these completely unrelated installs wrt Guan's sites?
Yes. I also am not seeing the memory problems he is; it seems
that 3.2/3.3 and 3.4 are exhibiting different weirdnesses.
I've seen
[EMAIL PROTECTED] wrote:
On May 16, 2006, at 8:04 AM, Nathan Folkman wrote:
It's been a while, and I'm still on my first cup of coffee, but I
think your biggest hurdle is probably going to be the loss of
ns_share in favor of nsv. Also 4.x requires Tcl 8.x. Hope that
helps!
Ugh. You're
I have three servers running identical installations of
AOLserver/3.3.1+ad13. On two (development and production, very low and
relatively low traffic volumes respectively) all scheduled procs have
stopped firing.
My God, it sounds to me like you're all being bit by the Y2.006K problem! :)
Dave Siktberg david.siktberg at WEBILITY.MD writes:
restarting AOL Server last night around 11PM EDT. Scheduled procs on both
were working fine up until the restart -- then none. Scheduled procs are
On a development box, I just started up clones of my
AOLserver/3.3.1+ad13/OpenACS 3.2.5
Ha! ns_share continues to live on, although I wouldn't recommend using
it, especially in high-load environments... nsv is where it's at! ;-)
$TOP/aolserver/nsd/tclshare.c
AOLserver/4.5.0a (aolserver4_5) for osx built on May 2 2006 at 10:57:19
CVS Tag: $Name: $
server1:nscp 1 ns_share
wrong #
Could this be an OS problem?
In case this provides a clue, the dmesg entries for my two servers that have
the problem are ...
Linux version 2.4.7-10 ([EMAIL PROTECTED]) (gcc version
2.96 2731 (Red Hat Linux 7.1 2.96-98)) #1 Thu Sep 6 17:27:27 EDT 2001
Linux version 2.4.20-18.7bigmem
[listserv etiquette question: the topic of this thread no longer matches the
title - should we change it to scheduled proc failures?]
Progress report - Smoking gun found
When I set my development server's system clock via the date command to
2006-05-12 21:28 and restart AOLServer, scheduled
I've experienced this problem over the weekend on half a dozen
servers in three different locations:
After starting up, AOLserver (mostly 3.4.2, also a 3.5.11) begins
allocating a lot of virtual memory. When I follow the process in top,
the virtual memory counter (but not real memory)
19 matches
Mail list logo
