Hi Francis,
It looks very good so far. No more problems on both servers I updated
since you fixed it.
Thank you very much !
Fabio
--
users@sogo.nu
https://inverse.ca/sogo/lists
02.02.22, 15:26 +0100, Francis Lachapelle (flachape...@inverse.ca):
I've pushed a fix yesterday regarding this issue. Can you try the latest
nightly build?
I've installed the SOGo 5.5.0.20220203-1 packages from Inverse's nightly
repository for Debian Buster.
With this version, the problem wi
Hi Fabio
> On Feb 2, 2022, at 06:54, Fabio Ciuffani wrote:
>
> I write to let you and the other posters in this thread know that we
> experience the same issue with two SOGo servers. Some time ago, we upgraded
> them from 5.2 to 5.4 and started seeing these error messages in the logs :
>
> so
Good afternoon Mr. Lachapelle,
I write to let you and the other posters in this thread know that we
experience the same issue with two SOGo servers. Some time ago, we
upgraded them from 5.2 to 5.4 and started seeing these error messages in
the logs :
/sogod[26069:26069] EXCEPTION: NAME:NoMoreCon
Hi,
this will probably not come as a surprise: I'm still seeing the problem
with the exhaustion of DB connections on SOGo 5.5.0.
In the meantime I've migrated the DB to the combined 9-table-layout.
Makes no difference either.
Do you need additional logs?
As Cédric already asked: Should we f
Hi Francis,
Is there something new on your side about this? Should we fill a bug report?
Regards
Cédric Archambeau
Secrétariat National Solidaires Finances Publiques
Pôle Communication - Informatique
Le 26/11/2021 à 17:48, Francis Lachapelle (flachape...@inverse.ca) a écrit :
Cédric
I need t
26.11.21, 17:48 +0100: Francis Lachapelle (flachape...@inverse.ca):
The same happens to me with SOGo 5.3.0 and 5.4.0. Going back to 5.2.0
makes the problem disappear.
I see this on a very small SOGo setup with 4 users and 2-3 devices each
syncing via CalDAV/CardDAV. It takes roughly a day till
-requ...@sogo.nu On Behalf Of Florian Unger
Sent: Wednesday, December 1, 2021 01:29
To: users@sogo.nu
Subject: Re: [SOGo] PostgreSQL Idle connections from
These are the log file entries when sogo runs out of SQL connections:
sogo-mailcow_1 | Nov 30 20:53:18 679d32496afb sogod [67]
These are the log file entries when sogo runs out of SQL connections:
sogo-mailcow_1 | Nov 30 20:53:18 679d32496afb sogod [67]:
<0x0x5600edf67520[GCSChannelManager]> DBPOOL: reused cached DB channel!
(0x5600ee9aa2e0)
sogo-mailcow_1 | Nov 30 20:53:18 679d32496afb sogod [67]:
<0x0x56
I see a similar behaviour after upgrading to SOGO 5.2.0 with MySQL as
database.
After a few hours of client usage the Mysql database runs out of
available connections.
Greetings
Florian
On 26.11.2021 17:48, Francis Lachapelle (flachape...@inverse.ca) wrote:
Cédric
I need the debugging entrie
Cédric
I need the debugging entries during a busy period, until you reach the maximum
number of connections of your PostgreSQL server. I'm looking at entries such as:
- DBPOOL: create new DB channel
- DBPOOL: keeping channel
- DBPOOL: garbage collecting
Thanks,
Francis
> On Nov 26, 2021, a
Hi Francis,
Without postgre debug, tell me if you want it :
Nov 26 16:26:54 sogod [68388]: 185.215.13.175 "REPORT
/SOGo/dav/user.n...@domain.tld/Contacts/pg_addressbook_name/ HTTP/1.1"
207 1517/4915 0.064 27386 94% 0 - 16
Nov 26 16:26:54 sogod [68388]: <0x0x55bde5374dc0[GCSChannelManager]>
DB
Hi Cédric
> On Nov 26, 2021, at 06:29, Cédric Archambeau wrote:
>
> We have a problem with Postgresql connections from SOGo 5.3.0 since few days
> (last update monday 22 - community version).
> Or we had it before but didn't see it ;-)
>
> Connections stay idle, mainly with an adressbook (Post
13 matches
Mail list logo
