On 03/01/2022 01:18, oliver.kr...@snoog.ch wrote:
Hi John,
You are right this was not a dovecot solr query. It is really strange
everything seems to work with Dovecot 2.3.4. E.g. search and
rebuilding index from scratch using doveadm. As soon as I use version
2.3.13 things are getting
Hi John,
You are right this was not a dovecot solr query. It is really strange
everything seems to work with Dovecot 2.3.4. E.g. search and rebuilding
index from scratch using doveadm. As soon as I use version 2.3.13
things are getting wild: dovecot crashed when I re-scan the index using
Hi John,
You are right this was not a dovecot solr query. It is really strange
everything seems to work with Dovecot 2.3.4. E.g. search and rebuilding
index from scratch using doveadm. As soon as I use version 2.3.13
things are getting wild: dovecot crashed when I re-scan the index using
On Mon, 2022-01-03 at 00:44 +0200, Aki Tuomi wrote:
> Maybe MySQL is not running, or perhaps something is blocking
> connecting to it? Check dmesg and (if on redhat based system)
> /var/log/audit/audit.log
When I ran systemctl status mysql, it tells me mariadb.service is
active and running.
>> mysql(localhost): Connect failed to database (postfix): Can't connect
>> to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
> Maybe MySQL is not running, or perhaps something is blocking connecting to
> it? Check dmesg and (if on redhat based system)
>
> On 02/01/2022 22:36 Ken Wright wrote:
>
>
> Dovecot has been giving me problems for the past week or so. Today the
> error log showed me this:
>
> Jan 2 13:33:39 grace dovecot: auth-worker(3250): Error:
> mysql(localhost): Connect failed to database (postfix): Can't connect
> to local
On 02/01/2022 12:13, oliver.kr...@snoog.ch wrote:
Here is what solr sends to dovecot, the offending uid in this exmaple
is '21'
{
"responseHeader":{
"status":0,
"QTime":1,
"params":{
"q":"body:Zeitserver"}},
"response":{"numFound":1,"start":0,"numFoundExact":true,"docs":[
Thank you, Lukas Matasovsky, for isolating this. I've had dovecot pinned
to the .16 version since I started getting that crash in the .17
version. But I've been too slack to do more than scan the mailing list
for fixes. Your investigation provided the solution that also worked for
me. Once
Dovecot has been giving me problems for the past week or so. Today the
error log showed me this:
Jan 2 13:33:39 grace dovecot: auth-worker(3250): Error:
mysql(localhost): Connect failed to database (postfix): Can't connect
to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
-
Hi Thomas,
> On 02/01/2022 17:20 Thomas Bellebaum wrote:
>
>
> Hello there and happy new year,
>
> I have a question/request regarding the Docker Image hosted at
> https://hub.docker.com/r/dovecot/dovecot.
> The Dockerfile itself declares two volumes:
>
> - `/etc/dovecot` for configuration
Hello there and happy new year,
I have a question/request regarding the Docker Image hosted at
https://hub.docker.com/r/dovecot/dovecot.
The Dockerfile itself declares two volumes:
- `/etc/dovecot` for configuration data
- `/srv/mail` for mail storage
It seems inconvenient in some cases to
Hi,
I have isolated the issue: after removing fts_squat dovecot seems to be
back to normal.
See also: https://doc.dovecot.org/configuration_manual/fts/squat/
Thank you for your support! You may close the issue. Cheers, Lukas
On Sun, Jan 2, 2022 at 12:03 PM Lukas Matasovsky
wrote:
> Hi,
>
> I
Hi,
I am just investigating on another server Debian, directly after upgrading
to dovecot .17:
Jan 2 11:55:10 judy dovecot: auth: Debug: auth client connected (pid=8682)
Jan 2 11:55:10 judy dovecot: auth: Debug: client in:
Here is what solr sends to dovecot, the offending uid in this exmaple is
'21'
{
"responseHeader":{
"status":0,
"QTime":1,
"params":{
"q":"body:Zeitserver"}},
"response":{"numFound":1,"start":0,"numFoundExact":true,"docs":[
{
"uid":[21],
14 matches
Mail list logo
