Re: some issues with sogo 5.7.1 in 7.2

Le Wed, Nov 30, 2022 at 12:38:26AM +0100, Giovanni Bechis a écrit :
> On Mon, Nov 28, 2022 at 02:57:07PM +0100, Landry Breuil wrote:
> > Hi,
> >
> > finally upgraded my work sogo instance, hit two distinct issues
> > unrelated to the WOPort one, both seen when trying to login:
> >
> > [GCSSessionsFolder
> > writeRecordForEntryWithID:value:creationDate:lastSeenDate:]: cannot
> > write record: <PostgreSQL72Exception: 0x313372437c8>
> > NAME:PostgreSQL72FatalError REASON:fatal pgsql error
> > (channel=<0x0x31374da1608[PostgreSQL72Channel]:
> > connection=<0x0x3135d728468[PGConnection]:
> > connection=0x0x313651c3800>>): ERROR: value too long for type character
> > varying(255)
> >
> > found https://bugs.sogo.nu/view.php?id=5491 - from what i can see,
> > https://github.com/Alinto/sogo/blob/master/Scripts/sql-update-5.5.1_to_5.6.0.sh
> > isnt packaged in /usr/local/share/doc/sogo/. Maybe the PLIST should be
> > updated ? anyway, solved it locally with psql:
> >
> > sogo=> ALTER TABLE sogo_sessions_folder ALTER COLUMN c_value TYPE
> > VARCHAR(4096);
> >
> > but also 'upstream sent too big header while reading response header
> > from upstream' in nginx error logs, cf
> > https://www.sogo.nu/support/faq/errors-in-nginx-regarding-header-too-big.html#/faq
> >
> > i already had some proxy buffers config in nginx (coming from the
> > pkg-readme), had to bump them and could login just fine.
> >
> > so .. maybe also update the pkg-readme with the values recommended
> > upstream ?
> >
> this diff works for me with Mariadb (nginx part untested).

It reads good to me, you've tested running the
sql-update-5.5.1_to_5.6.0.sh script ?

> ok ? What about 7.2 ?

7.2 could benefit from it imo.

Landry