There are no syncml tables in horde 3.1, you probably upgraded from an 
earlier 3.2-cvs version and missed some sql upgrade.

Looks like the indizes for horde_syncml_map are severly broken in the 
old database. Probably something gone bad somewhere in one of the 
upgrade steps from 3.1 to 3.2-rcX.



mysql> show index from horde_syncml_map;

+------------------+------------+------------------------+--------------+--------------------+-----------+-------------+----------+--------+------+------------+---------+

| Table            | Non_unique | Key_name               | 
Seq_in_index | Column_name        | Collation | Cardinality | Sub_part 
| Packed | Null | Index_type | Comment |

+------------------+------------+------------------------+--------------+--------------------+-----------+-------------+----------+--------+------+------------+---------+

| horde_syncml_map |          1 | syncml_cuid_idx        |             
1 | syncml_syncpartner | A         |           5 |     NULL | NULL   | 
      | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_cuid_idx        |             
2 | syncml_db          | A         |          12 |     NULL | NULL   | 
      | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_cuid_idx        |             
3 | syncml_uid         | A         |          12 |     NULL | NULL   | 
      | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_cuid_idx        |             
4 | syncml_cuid        | A         |        3860 |     NULL | NULL   | 
YES  | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_suid_idx        |             
1 | syncml_syncpartner | A         |           5 |     NULL | NULL   | 
      | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_suid_idx        |             
2 | syncml_db          | A         |          12 |     NULL | NULL   | 
      | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_suid_idx        |             
3 | syncml_uid         | A         |          12 |     NULL | NULL   | 
      | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_suid_idx        |             
4 | syncml_suid        | A         |        1930 |     NULL | NULL   | 
YES  | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_syncpartner_idx |             
1 | syncml_syncpartner | A         |           5 |     NULL | NULL   | 
      | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_db_idx          |             
1 | syncml_db          | A         |           4 |     NULL | NULL   | 
      | BTREE      | NULL    |

| horde_syncml_map |          1 | syncml_uid_idx         |             
1 | syncml_uid         | A         |           2 |     NULL | NULL   | 
      | BTREE      | NULL    |

+------------------+------------+------------------------+--------------+--------------------+-----------+-------------+----------+--------+------+------------+---------+

11 rows in set (0.00 sec)



I did remove the horde_synml_map and horde_syncml_anchor tables, 
cleaned up addressbook and calender, and now the sync seem to work, at 
least with test account and VPA.



With the production VPA and my normal account, it doesn't like to add 
contacts now, but I will investigate that tomorrow.

I now have setup a fresh VPA to do the tests. I test now with the 
newest 3.2 rc packages.



First test:



I used an different account, I should get a fresh calendar and 
contacts database on horde side, but again contacts and calendar 
entries got tripled.



Second test:



I  created a completly fresh database on my test horde server. Now 
contacts and calendar entries seem to work as expect (did not get 
tripled, not even doubled)

syncronisation in both directions seem to work.



I didn't see a database error in /tmp/horde.log in the first test, but 
I will review the database more exactly in the next step.

Not yet, I will now setup a frsh VPA just for tests, as I'm somewhat 
relcutant to always kill my contacts/kalender entrys in my VPA.



Sincerly,

Klaus

Have you been able to run more tests? Can you try the latest RCs?

Ok, i did an "cvs co horde" on 2th May, and packed that over my 
testinstallation with 3.2rc3, I just didn't update the over apps.



From /tmp/horde.log I don't see any Database errors.



Further tests I could not do before next week, as I'm currently at 
CERN in Geneva and the UMTS costs for my Windows Mobile Device outside 
Germany are tremendous.

The log file you attached is not from the latest CVS version. Beside 
that, database errors are logged in the Horde log file, not the sync 
log file.

The data.txt Attachement regarding my last message

Sorry about my late response, I was very busy last weeks.



I tried now with latest CVS from Horde. Again I got the tripling. In 
the logs I can't see database errors. I use Funambol Client 6.5.14



Sincerly,

Klaus

Ping?

Thanks! I will test it during the next days.

Sincerly,

Klaus

Ping?

For some reason the sync anchors are not properly saved in the 
database, thus all elements on both the client and server are 
considered new on the other side.

Try the latest CVS code, database errors should be properly logged now.

One addition:



The same happens with events. A calendar entry created on the VPA 
get's tripled after the second sync again just on the VPA side.



One difference here: After removing the overdue events a sync does not 
remove the event on the Horde side.

Hello,



I did setup a test environment with Horde Webmail Edition 1.1rc1, and 
I'm trying to sync contacts between a Vodafone Compact VPA II and 
Horde using the Synthesis Client.



All works well when I create a Contact on the Horde side, but creating 
a contact on the VPA leads to a tripled contact on the VPA after 
syncing.



It happens this way:



First sync:



The contact will be created in Horde, but will be sent back 
immediately and is doubled on the VPA.



Second sync:



The contact will be again received from Horde and is tripled now!



Further sync's will not multiply the contact further.



When I try to remove the overdue contacts and sync again the contact 
is removed from horde.



When I modify the contact again on the VPA to get it synced again to 
horde, the same game happens again, the contact will be created 
correctly on Horde, but will be tripled after the second sync again.