Here is the message from five months ago that helped me get this fixed on my
3.x system:
Forum: OpenACS QA
Thread: ad_schedule_proc seems to be failing
Author: Michael A. Cleverly
Posted: 2006-05-23 12:53:52.861061-07
Let me try and explain:
During AOLserver startup, if MaxOpen or MaxIdle is a
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
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
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
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 use temporary tables in Postgres 7.1 (via select foo into temporary table
bar). These are needed for a short time only. I expected they would
periodically be deleted. In looking at my vacuum results, it appears they
are persisting forever. I can't locate any instructions on how to remove
- Original Message -
From: Don Baccus dhogaza@pacifier.com
Enable PG logging and examine those logs, as well.
I've taken a break to play with some PG logging on my development machine
before doing the same on production -- getting some better instrumentation
will be like turning on the
to be a
shorter wait if I do a restart each day, but I'm loathe to risk making the
site unavailable for a long time even in the wee hours.
Any idea what could cause this? How to fix it? A year ago I did not
observe this behavior.
Dave Siktberg
--
AOLserver - http://www.aolserver.com/
To Remove
Hi
Nathan! These are six very strong-looking candidates - I wouldn't reject
any of them. But we have to choose, so here goes:
Dossy ShiobaraJeff HobbsScott GoodwinTom
Jackson
Oops
.. and I don't even live in Florida.
to helping the AOLserver
community as bestI can. We all will benefit from wider use of
AOLserver and from the agenda items you laid out for the rest of this
year.
Dave
Siktberg
Webility Corporation
structure changed, I dropped it. But it could well form a useful starting
point now. Take a look at it here (no off-page links work):
www.webility.md/aol-tcl-a.htm (not our AOLserver site)
I'll volunteer to take it further if y'all think it's worth it.
Dave Siktberg
decide to look further. That _is_ somewhat broke.
Dave Siktberg
Webility Corporation
3. Keep using the AOL listserv for most discussion, and use the SF
listserv for just tracker announcements.
My link to aolserver documentation ( www.aolserver.com/docs/devel/tcl/api/ )
no longer works - redirects to SourceForge which complains Invalid
Project. Anyone know where I should look now? (Or should I just download
the docs and reference them locally.)
Thanks! Dave
More ... The redirect is broken - goes to
http://sourceforge.net/projects/aolserverdocs/devel/tcl/api/ - note the
typo. When I corrected and went to aolserver/docs/... I got the home page.
Then clicked on Docs then on View Documentation, and I get a message saying
This project has no
October 2000. I'll send it to
anyone interested.
Can someone put it onto the OpenACS server? Any reason not to?
Dave Siktberg
Call me dumb, but I just went to the AOL documentation page and still
can't find anything on ns_cache. There are 4 ns_cache_
I looked in that tarball but not closely enough - though there are no files
named nscache* or ns_cache*, there is a directory named nscache, and the key
program file is named tclcache.c.
a copy of nscache1.1 is included in the openacs's aolserver distribution,
which is includes other aD
I am using nsv arrays to hold session data across multiple page accesses,
and to hold some relatively static widely-shared database data to avoid
unnecessary database reads. Probably at any point in time there will be
several hundred plus nsv arrays with a few K bytes in each, but I haven't
The OpenACS system implements a filter manager, ad_register_filter, that
sits on top of ns_register_filter and lets you set a priority number for
each filter you register with it. The master filter (registered with
ns_register_filter) applies each registered filter in turn in the order you
I am using the nsv facility to store session data between connections. I am
nervous that my tracking of each defined key may go awry, and I will wind up
with a garbage collection problem - key/value pairs that I am unaware of.
Is there a way to get a list of all keys defined for a given nsv
Try 'nsv_array names' instead of 'nsv_names'.
Thanks - that does it!
I notice that the current nsv documentation has some omissions and mistakes.
Namely:
1) The list of commands at the top omits nsv_names - returns names of
arrays matching a glob pattern. nsv_names * will return a list of
You might benefit from a look at the arsDigita Community System security
routines. In particular, ad-security.tcl implements a cookie-based
mechanism for session IDs, including extensions to handle https. The
session ID has several components, including a simple integer session number
and a
nsv docs are at http://www.aolserver.com/docs/devel/tcl/nsv-commands.adp
-Original Message-
From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf
Of Scott Laplante
Sent: Thursday, November 15, 2001 12:32 PM
To: [EMAIL PROTECTED]
Subject: [AOLSERVER] nsv docs
can someone point
Development of my first site is well underway, and I am starting to think
about production configuration issues. What's the best way to structure
things so I can isolate development work and the testing thereof from the
production system? To do orderly moveups from development to production?
I'm a relative newbie to AOLServer, but a developer for many years. All the
evidence I see (developing our website, lurking on this listserve and
others, reading Phil Greenspun's book, talking with aD developers, watching
people develop on other platforms) says to me this is a good choice for
26 matches
Mail list logo