Hi Aki,
We just installed 2.3.19, and are seeing a couple of users throwing the
"INBOX/dovecot.index reset, view is now inconsistent" and their replicator
status erroring out. Tried force-resync on the full mailbox, but to no
avail just yet. Not sure if this bug was supposedly fixed in 2.3.19?
T
Out of the blue my proxy installations started showing this:
dovecot: login: tried to change state 2 -> 2 (if you can't login at all, see
src/lib/fdpass.c)
Nobody can login.
Running 1.0.0 on the proxy and 1.0.2 on my storage boxes. Anybody have any
insights?
-c
My bad. someone deleted the 'masteruser' from the database. Go about your
business.
-c
On 7/25/07, Cassidy B. Larson <[EMAIL PROTECTED]> wrote:
Out of the blue my proxy installations started showing this:
dovecot: login: tried to change state 2 -> 2 (if you can't l
Seeing a few core dumps on my two proxy servers with dovecot-auth since
upgrading to 1.0.2.
Example:
Jul 30 13:36:51 alora kernel: pid 20234 (dovecot-auth), uid 0: exited on
signal 11 (core dumped)
Jul 30 13:36:51 alora dovecot: child 20234 (auth) killed with signal 11
Jul 29 19:17:08 marbella ke
the storage servers. I
suppose I could disable gssapi on the proxies, but figured I'd send this
your way just in case there was a looming issue. I believe gssapi did work
in the past, but can't quite remember.
-c
On 8/1/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:
>
> On
al SIGSEGV, Segmentation fault.
0x107712a8 in gss_delete_sec_context () from /usr/lib/libgssapi.so.8
---
On 8/1/07, Timo Sirainen <[EMAIL PROTECTED]> wrote:
>
> On Mon, 2007-07-30 at 14:06 -0600, Cassidy B. Larson wrote:
>
> > gdb /usr/local/li
Finally getting around to upgrading my setup to 2.3.x.
All of our front end proxies are fine on 2.3 connecting to a 2.2 backend
storage pair.
So the question is, if I stage the upgrade, will it break replication
between the two backend storage servers? My thought was to upgrade one to
2.3, and k
