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
On 2006.05.17, Zachary Shaw [EMAIL PROTECTED] wrote:
We're experiancing a similar issue at Brandeis University, but we get
no error, our scheduled procs just hang. [...] we're running aolserver
3.3.1 ad13 [...] if I set the system date to may 12th or earilier all
the procs will run. otherwise
1) ns_info patchlevel
3.3 apparently didn't have patchlevel, as that gave me an error. The
output of ns_version is 3.3.1+ad13
2) uname -a
Linux x.furfly.com 2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST
2006 i686 i686 i386 GNU/Linux
3) glibc version
$ rpm -qa | grep glibc
We just decided to move everything left on 3.3ad13 to 4.0, but to help
those who need it:
Can we get everyone who's experiencing this problem to provide a few
things:
1) ns_info patchlevel
I think you mean info patchlevel
I've got 8.3.2
2) uname -a
Linux servername 2.4.21-4.EL #1 Fri
My info patchlevel is also 8.3.2.
janine
On May 17, 2006, at 2:12 PM, Titi Ala'ilima wrote:
We just decided to move everything left on 3.3ad13 to 4.0, but to
help those who need it:
Can we get everyone who's experiencing this problem to provide a few
things:
1) ns_info patchlevel
I
On 2006.05.17, Titi Ala'ilima [EMAIL PROTECTED] wrote:
We just decided to move everything left on 3.3ad13 to 4.0, but to help
those who need it:
So, you're seeing this problem even on AOLserver 4.0? What version of
OpenACS?
Can we get everyone who's experiencing this problem to provide a
On May 17, 2006, at 2:35 PM, Dossy Shiobara wrote:
On 2006.05.17, Titi Ala'ilima [EMAIL PROTECTED] wrote:
Janine, could you give us your info patchlevel too? Same with
everyone else who is seing this problem and is reporting information.
8.3.2 also.
janine
--
AOLserver -
Dossy Shiobara wrote:
No, I meant ns_info patchlevel -- to get the full version of
AOLserverthat's running -- but yes, I should have asked for info
patchleveltoo, to find out what version of Tcl is being used.
patchlevel appears not to be a switch to ns_info in
AOLserver/3.3.1+ad13 (as
On 17 May 2006, at 23:35 , Dossy Shiobara wrote:
On 2006.05.17, Titi Ala'ilima [EMAIL PROTECTED] wrote:
We just decided to move everything left on 3.3ad13 to 4.0, but to
help
those who need it:
So, you're seeing this problem even on AOLserver 4.0? What version of
OpenACS?
I don't think
On 17 May 2006, at 21:34, Dossy Shiobara wrote:
Dave Siktberg seems to have narrowed it down to 2006-05-12 21:25.
In what timezone? It sound like that could equate to Sat May 13
02:27:28 BST 2006, or 1147483648 seconds since epoch, which makes it
*exactly* 1,000,000,000 seconds until expiry
SERVER #1 exhibiting the problem
% info patchlevel
8.3.3
$ rpm -qa | grep glibc
glibc-2.2.4-13
glibc-common-2.2.4-13
glibc-devel-2.2.4-13
$ uname -a
Linux opus 2.4.7-10 #1 Thu Sep 6 17:27:27 EDT 2001 i686 unknown
ns_info version: 3.3.1+ad13
--
AOLserver - http://www.aolserver.com/
To
So, you're seeing this problem even on AOLserver 4.0? What version of
OpenACS?
I don't think anyone has seen this problem on AOLserver 4.0.
Right, I think he meant they're fleeing to AOLserver 4.x to get rid of the
problem, and was just posting his current system info so others might be
able
It seems, as if all problems are in tcl 8.3.*.
it should be possible to compile aolserver 3.* with e.g. tcl 8.4.13.
Seems worth a try.
-gustaf
Dave Siktberg schrieb:
SERVER #1 exhibiting the problem
% info patchlevel
8.3.3
$ rpm -qa | grep glibc
glibc-2.2.4-13
glibc-common-2.2.4-13
Great detective work! I assumed the watershed time would have this kind of
characteristic.
My timezone is Eastern Daylight, BTW.
Dave Siktberg seems to have narrowed it down to 2006-05-12 21:25.
In what timezone? It sound like that could equate to Sat May 13
02:27:28 BST 2006, or 1147483648
Sorry, I meant instead of waiting for a fix to the problem, we're moving sites
to 4.0. But I contributed this info to add to the body of data on the 3.x
problem.
--- [EMAIL PROTECTED] wrote:
From: Dossy Shiobara [EMAIL PROTECTED]
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER]
Quoting Gustaf Neumann [EMAIL PROTECTED]:
It seems, as if all problems are in tcl 8.3.*.
it should be possible to compile aolserver 3.* with e.g. tcl 8.4.13.
But just a data point from the not happening here side. I have
AOLserver 3.3.1+ad13 servers that are all running fine - both the ones
16 matches
Mail list logo
