Skip to Content.
Sympa Menu

en - Re: [sympa-users] list subscribers lost during migration

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Olivier Salaün - CRU <address@concealed>
  • To: Redmond Militante <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-users] list subscribers lost during migration
  • Date: Mon, 22 May 2006 14:22:03 +0200

You are in a strange situation because Sympa did the DB structure updates but did not update the DB entries afterward. It leads to your admin_table containing both entries with the robot field set and previous entries without it. Then the update process leeds to "Duplicate entry" errors.

The best way to bring you back to a healthy situation is to :
  1. Empty the admin_table since it will be automatically repopulated : DELETE * FROM admin_table
  2. Run the sympa upgrade process to populate the robot DB fields : sympa.pl --upgrade --from=4.x --to=5.2
  3. Restart all Sympa processes

To prevent these kinds of annoyances, next release of Sympa will prevent any processes to start before the upgrade process has been run.

Redmond Militante wrote:
I followed the steps below, it sympa.pl -d seems to run into an error when attempting to upgrade the database structure.

I am attaching the output of sympa.pl -d, including the error message.


[...] DBD::mysql::db do failed: Duplicate entry 'address@concealed' for key 1 at /home/sympa/bin/List.pm line 11307. Unable to execute SQL statement "UPDATE admin_table SET robot_admin='announce.uchicago.edu' WHERE (list_admin='achtest')" : Duplicate entry 'address@concealed' for key 1



Archive powered by MHonArc 2.6.19+.

Top of Page