General discussion on installation and configuration of SOGo

Text archives Help


[SOGo] sogo 4. ERROR: value too long for type character varying(255) (not contacts quick tables c_mail problem)


Chronological Thread 
  • From: "\" \"" ( ) < >
  • To:
  • Subject: [SOGo] sogo 4. ERROR: value too long for type character varying(255) (not contacts quick tables c_mail problem)
  • Date: Fri, 7 Jun 2019 17:36:22 +0200
  • Dmarc-filter: OpenDMARC Filter v1.2.0 mail.inverse.ca BD9B21DE514E

Dear Sogo-users,

I have the below error message regularly. It's about 2 different
contacts. Evidently, I cannot find them in the database to see what is
wrong, as they are never synchronized.

I recently upgraded from 3.1.3-1 to 4.0.7, then ran
"sql-update-3.2.10_to_4.0.0.sh" without errors

I'm currently at 4.0.7.20190607-1

I found that previously, the field c_mail in public.sogoXYZ_quick must
be extended to TEXT.

This is the case in my database. e.g. latest DB-dump:
CREATE TABLE public.sogoXYZUSER_quick (
c_name character varying(255) NOT NULL,
c_givenname character varying(255),
c_cn character varying(255),
c_sn character varying(255),
c_screenname character varying(255),
c_l character varying(255),
c_mail text,
c_o character varying(255),
c_ou character varying(255),
c_telephonenumber character varying(255),
c_categories character varying(255),
c_component character varying(10) NOT NULL,
c_hascertificate integer DEFAULT 0
);

Did I miss some database-schema upgrades? In the manual, there is no
mentioning what (else) to do when upgrading from 3.1.x
I looked at sql-update-3.0.0-to-combined.sh , but it doesn't seem to
alter a field from varchar to something bigger.

Is this fixable on the server? or should I tell the user to change the
offending contact, so it can get synced?



The error message is:

...
Jun 07 16:16:23 sogod [23065]:
<0x556d84027610[SOGoContactGCSEntry]:e33b9c73-6ff6-447a-b93b-a3e00be43be5.vcf>
TODO: implement if-none-match for etag: '*'
Jun 07 16:16:23 sogod [23065]: <0x0x556d83ff2460[GCSFolder]>
ERROR(-[GCSFolder
writeContent:fromComponent:container:toName:baseVersion:]): cannot
insert content : <PostgreSQL72Exception: 0x556d83b9e410>
NAME:PostgreSQL72FatalError REASON:fatal pgsql error
(channel=<0x0x556d840d5290[PostgreSQL72Channel]:
connection=<0x0x556d84000780[PGConnection]:
connection=0x0x556d840fb820>>): ERROR: value too long for type
character varying(255)

Jun 07 16:16:23 sogod [23065]: [ERROR]
<0x556d84027610[SOGoContactGCSEntry]:e33b9c73-6ff6-447a-b93b-a3e00be43be5.vcf>
write failed: <PostgreSQL72Exception: 0x556d83b9e410>
NAME:PostgreSQL72FatalError REASON:fatal pgsql error
(channel=<0x0x556d840d5290[PostgreSQL72Channel]:
connection=<0x0x556d84000780[PGConnection]:
connection=0x0x556d840fb820>>): ERROR: value too long for type
character varying(255)

Jun 07 16:16:23 sogod [23065]: XXX.XXX.XXX.XX, XX.XX.XX.XX "PUT
/SOGo/dav/USERNAME/Contacts/personal/e33b9c73-6ff6-447a-b93b-a3e00be43be5.vcf
HTTP/1.1" 500 367/1280 0.014 - - 0
...


  • [SOGo] sogo 4. ERROR: value too long for type character varying(255) (not contacts quick tables c_mail problem), " ", 06/07/2019

Archive powered by MHonArc 2.6.18.

Top of page