The mailing list for listmasters using Sympa

[Olivier Salaün - CRU <address@concealed>]

You're right,  your problem is probably related to database primary keys.

What RDBMS are you using ?
Note that Sympa can run with either MySQL, Pg, SQLite, Oracle or Sybase 
; but Sympa does not perform automatic update of your database structure 
(while upgrading) with all RDBMS. The automatic updates are performed 
only with MySQL or SQLite. If you are using another RDBMS, you probably 
need to DROp and reCREATE your indexes and primary keys according to the 
latest create_db.XX script. We need to mention that in the release notes.

Patrick von der Hagen wrote:
> yesterday I considered my problems to be solved, but today I 
> discovered a new one: I had this list "testenvonvper" at the first 
> host, created a new robot and chose to use that list to create a 
> conflict. The same local_part both at lists.uni-karlsruhe.de and 
> lists.newdomain.
> Most things work fine, however those lists had different sets of 
> owners when I started testing. When I decided "one user whould be in 
> both sets of owners", things got complicated.
>
> Owner is in first list: fine.
> Adding owner to second list: INTERNAL SERVER ERROR (edit_list) - 
> Failed to include list admins
> Removing owner from first list: fine
> Adding owner to second list: fine
> Adding owner to first list: INTERNAL SERVER ERROR (edit_list) - Failed 
> to include list admins
>
> syslog says:
> Nov  9 12:31:57 listserv wwsympa[27741]: Unable to execute SQL 
> statement "INSERT INTO admin_table (user_admin, comment_admin, 
> list_admin, robot_admin, date_admin, update_admin, 
> reception_admin,subscribed_admin,included_admin,include_sources_admin, 
> role_admin, info_admin, profile_admin) VALUES 
> ('address@concealed', NULL, 'testenvonverp', 
> 'lists.uni-karlsruhe.de', FROM_UNIXTIME(1163071917), 
> FROM_UNIXTIME(1163071917), 'mail', 1, 0, NULL, 'owner', NULL, 
> 'normal')" : Duplicate entry 
> 'address@concealed' for key 1
>
>
> Probably some index/primary-key/etc.-issue?
> Upgraded sympa 5.2.1 to sympa 5.2.3, but the problem remains.
>
> Any ideas?