[SOGo] Any experiences with TbSync w/ CalDAV & CardDAV Provider?
Hi! As most Linux distros began to roll out Thunderbird 78 recently and given the fact that sogo-connector for this version was (and perhaps is) a little bit problematic to use (to say it politely) I started to experiment with the TbSync and CalDAV & CardDAV Provider Thunderbird add-ons. See https://github.com/jobisoft/TbSync and https://github.com/jobisoft/DAV-4-TbSync/ So far the results are encouraging: the add-ons seem to work fine with SOGo for both calendar and contacts. Given the SOGo DAV base-URL, the add-ons find the user's calendar and address-book subscriptions automatically. Synchronisation seems to work fine in both directions. With TbSync users have to configure the SOGo account themselves. Users have to provide the correct SOGo CalDAV and CardDAV URLs as well as username and password in the TbSync admin GUI. After that, TbSync automatically detects all calendars and address books the user has subscribed to in SOGo. It even detects the colors assigned to each calendar. For a smaller organization with only a few users this is IMHO way easier for the admin as it is with the sogo-connector concept, where the admin has to provide a customized sogo-connector XPI file (we had that dicussion on this list a few weeks ago...) I did limited testing with a few calendars and address-books, though and can't say anything about large-scale installations. Therefore I'd like to ask if anyone can share good or bad experiences with these Thunderbird add-ons: Did you try these add-ons as alternative to sogo-connector? For how many users / calendars / address books? Are you happy with it? Did you find any problems? Thanks! - andreas -- Andreas Haumer | mailto:andr...@xss.co.at *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 OpenPGP_signature Description: OpenPGP digital signature
[SOGo] Duplicate key issue on Ubuntu 20.04 with PostgreSQL
Hi. I am setting up SOGo on my fresh Ubuntu 20.04 server. While going through the set up I found this in the logs: — Dec 05 22:44:28 sogod [60235]: <0x0x558239378840[WOWatchDog]> child spawned with pid 60248 Dec 05 22:44:28 sogod [60248]: |SOGo| table 'sogo_user_profile' successfully created! Dec 05 22:44:28 sogod [60247]: |SOGo| table 'sogo_user_profile' creation failed! Reason: NAME:PostgreSQL72FatalError REASON:fatal pgsql error (channel=<0x0x558239420900[PostgreSQL72Channel]: connection=<0x0x5582394a8e30[PGConnection]: connection=0x0x558239466bb0>>): ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index" DETAIL: Key (typname, typnamespace)=(sogo_user_profile, 2200) already exists. Dec 05 22:44:28 sogod [60246]: |SOGo| table 'sogo_user_profile' creation failed! Reason: NAME:PostgreSQL72FatalError REASON:fatal pgsql error (channel=<0x0x558239420900[PostgreSQL72Channel]: connection=<0x0x5582393aea50[PGConnection]: connection=0x0x558239466bb0>>): ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index" DETAIL: Key (typname, typnamespace)=(sogo_user_profile, 2200) already exists. — Googling for it didn’t help much. I found one entry where stoping sogo, deleting the table in question (here sogo_user_profile) and then starting sogo again might help. But this only reproduces above entry. The PostgreSQL logs are not really helpful either: — 2020-12-05 22:44:28.722 CET [60249] sogo@sogo ERROR: duplicate key value violates unique constraint "pg_type_typname_nsp_index" 2020-12-05 22:44:28.722 CET [60249] sogo@sogo DETAIL: Key (typname, typnamespace)=(sogo_user_profile, 2200) already exists. 2020-12-05 22:44:28.722 CET [60249] sogo@sogo STATEMENT: -- -- (C) 2004-2005 SKYRIX Software AG -- (C) 2006-2007 Inverse inc. -- CREATE TABLE sogo_user_profile ( c_uid VARCHAR(255) NOT NULL PRIMARY KEY, c_defaults TEXT, c_settings TEXT ); — Any ideas? Thanks, Holger -- users@sogo.nu https://inverse.ca/sogo/lists
