Subject:
The mailing list for listmasters using Sympa
List archive
- From: "Keith A. Marrocco" <address@concealed>
- To: Olivier Salaun - CRU <address@concealed>
- Cc: address@concealed
- Subject: Re: [sympa-users] Re: [sympa-users] Task manager/bounced messages/Dynamic lists
- Date: Thu, 04 Mar 2004 12:20:53 -0600
It occurred to me that I don't have to define an Oracle database in
sympa.conf if there is a dynamic entry for extracting email addresses
from Oracle in each list definition. I commented out the db
definitions and restarted sympa and the task manager without any
recurrence of the problem.
Keith
Olivier Salaun - CRU wrote:
Hi Keith,
Keith A. Marrocco a écrit :
We are
converting our Sympa 3.4.4.3 installation to Sympa 4b2 on a separate
machine. Both instances are pointing to Oracle databases. We copied
the lists definitions and bounces over from the old machine to the new
machine.
Did you update your database structure according to the release_notes
(NEWS file) :
***** New 'user_attributes' field
in the 'subscriber_table'
***** If you are using MySQL, Sympa.pl will change the database
structure
***** at startup. If using Pg, Oracle or Sybase you should ALTER
the table
***** structure according to the provided create_db.x scripts.
***** You should update your database structure based on the
create_db.xxx scripts
***** unless you are using MySQL (Sympa tries to update the database
automatically at startup)
***** If you are upgrading from a previous Sympa version, you should
update
***** your sympa DB as follows :
***** ALTER TABLE subscriber_table CHANGE date_subscriber timestamp
with time zone NOT NULL;
***** ALTER TABLE subscriber_table CHANGE update_subscriber timestamp
with time zone;
Our lists
are comprised of about 20,500 lists that dynamically generate
addresses; we have absolutely nothing in the subscriber or user tables.
A typical definition is as follows:
include_sql_query
db_type Oracle
[...]
What is the 'user_data_source' ? include or include2 ?
We have
encountered a situation in the new installation while testing in which
the task manager is trying to expire bounce messages, but consumes all
available shared memory in our Oracle server in the process bringing
the entire RDBMS to its knees. Inspection on an isolated database
server revealed that the task manager is taking vast numbers of bounced
addresses and trying to update them simultaneously in the related
(empty) subscriber and user tables.
Can you provide your task_manager log entries ?
[...]
--
Olivier Salaun
Comite Reseau des Universites
|
Archive powered by MHonArc 2.6.19+.