On Thu, 03 Jun 2004, Rob Siemborski wrote:
Why on earth were you killing processes at random?
As a test of the stability of the databases. A database should be able
to take the explosive failure of any reader or writer with, at worst, a
reconstruction. Consider the scenario when the machine
On Thu, 03 Jun 2004, Rob Siemborski wrote:
I'll also ask the obvious -- did you subsequently stop the server and run
recovery on the database?
Well, master couldn't prefork anything, citing an inability to read
mailboxes.db. As reconstruct -m is currently unavailable I used
reconstruct -p to
On Fri, 4 Jun 2004, Ian G Batten wrote:
On Thu, 03 Jun 2004, Rob Siemborski wrote:
I'll also ask the obvious -- did you subsequently stop the server and run
recovery on the database?
Well, master couldn't prefork anything, citing an inability to read
mailboxes.db. As reconstruct -m is currently
On Fri, 04 Jun 2004, Rob Siemborski wrote:
I ment ctl_cyrusdb -r.
I thought that was run automatically when master started?
ian
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
For what it's worth, I'm building a new server to replace my
long-standing Solaris 7 + Cyrus 1.6.22 server --- one hour of downtime
since 1999. I've used the gcc from the SFW collection, Cyrus 2.2.4 and
Solaris 10 build 55 (which is probably the current Solaris Express bits:
I'm a Platinum Beta
On Thu, 3 Jun 2004, Rob Siemborski wrote:
not seen any major problems, although a concerted dose of killing
processes at random while under load corrupted my skiplist mailboxes.db
file. For safety I've switched that to berkeley (Sun provide db4.1 in
SFW).
Why on earth were you killing
On Thu, 3 Jun 2004, Ian G Batten wrote:
For what it's worth, I'm building a new server to replace my
long-standing Solaris 7 + Cyrus 1.6.22 server --- one hour of downtime
since 1999. I've used the gcc from the SFW collection, Cyrus 2.2.4 and
Solaris 10 build 55 (which is probably the
Against my better judgement, I upgrade the hardware Sun 280R to Sun 440,
the OS from Solaris 8 to 9 and Cyrus IMAP 2.0.16, SASL 1.5.24 Postfix
1.1.13 to IMAP 2.2.5, SASL 2.1.18 Postfix 2.1.1.
I haven't created any new users on the new version yet. I did try going
from quotalegacy to skiplist
Igor Brezac wrote:
On Tue, 1 Jun 2004, Shawn Sivy wrote:
I'm having all kinds of problems with Cyrus IMAP 2.2.5 on Solaris 9.
System I/O errors, imap processing dying, IOERRORs.
Does anyone have suggestions on what could be the cause? Has anyone
gotten version 2.2.5 working on Solaris (SPARC)
On Wed, 2 Jun 2004, Shawn Sivy wrote:
Against my better judgement, I upgrade the hardware Sun 280R to Sun 440,
the OS from Solaris 8 to 9 and Cyrus IMAP 2.0.16, SASL 1.5.24 Postfix
1.1.13 to IMAP 2.2.5, SASL 2.1.18 Postfix 2.1.1.
I haven't created any new users on the new version yet. I
On Wed, 2 Jun 2004, Shawn Sivy wrote:
Igor Brezac wrote:
On Tue, 1 Jun 2004, Shawn Sivy wrote:
I'm having all kinds of problems with Cyrus IMAP 2.2.5 on Solaris 9.
System I/O errors, imap processing dying, IOERRORs.
Does anyone have suggestions on what could be the cause? Has
Igor Brezac wrote:
On Wed, 2 Jun 2004, Shawn Sivy wrote:
Igor Brezac wrote:
On Tue, 1 Jun 2004, Shawn Sivy wrote:
I'm having all kinds of problems with Cyrus IMAP 2.2.5 on Solaris 9.
System I/O errors, imap processing dying, IOERRORs.
Does anyone have suggestions on what could be
On Wed, 2 Jun 2004, Shawn Sivy wrote:
Have things improved since you restarted master?
You can use pfiles and pmap (and lsof) to check for open files and memory
usage. Try to use pfile against a running imapd process and see if a
number of open files increases.
What does ulimit -a say?
I wasn't able to get 2.2.3 to work eventhough I used the same build
options. Kept getting messages like ...
Jun 2 13:10:09 cyrus imap[3080]: [ID 884154 local6.error] unable to
tell master 1: Broken pipe
Jun 2 13:10:09 cyrus imap[3080]: [ID 884154 local6.error] unable to
tell master 2:
I'm having all kinds of problems with Cyrus IMAP 2.2.5 on Solaris 9.
System I/O errors, imap processing dying, IOERRORs.
Does anyone have suggestions on what could be the cause? Has anyone
gotten version 2.2.5 working on Solaris (SPARC) 9?
-Shawn
May 30 17:52:57 cyrus lmtpunix[14954]: [ID
Shawn Sivy wrote:
I'm having all kinds of problems with Cyrus IMAP 2.2.5 on Solaris 9.
System I/O errors, imap processing dying, IOERRORs.
Does anyone have suggestions on what could be the cause? Has anyone
gotten version 2.2.5 working on Solaris (SPARC) 9?
-Shawn
May 30 17:52:57 cyrus
I want to say that it takes a little while since I tried a couple things
that seemed to work, but the errors creep back in after a bit. I
recompiled with gcc instead of Sun's cc, which I thought fixed the
problem, but it didn't.
Off hand, could you tell whether the memory leak would most
Shawn Sivy wrote:
I want to say that it takes a little while since I tried a couple things
that seemed to work, but the errors creep back in after a bit. I
recompiled with gcc instead of Sun's cc, which I thought fixed the
problem, but it didn't.
Off hand, could you tell whether the memory
On Tue, 1 Jun 2004, Shawn Sivy wrote:
I'm having all kinds of problems with Cyrus IMAP 2.2.5 on Solaris 9.
System I/O errors, imap processing dying, IOERRORs.
Does anyone have suggestions on what could be the cause? Has anyone
gotten version 2.2.5 working on Solaris (SPARC) 9?
-Shawn
On a whim, I tried switching from quotalegacy to skiplist for the
quota_db config. I stopped and restarted the master, it created the
quotas.db file in the /var/imap directory, but I can't set any quotas
after the first one. After that trying to get the quota of the only
user or set another
I'm having all kinds of problems with Cyrus IMAP 2.2.5 on Solaris 9.
System I/O errors, imap processing dying, IOERRORs.
Does anyone have suggestions on what could be the cause? Has anyone
gotten version 2.2.5 working on Solaris (SPARC) 9?
-Shawn
May 30 17:52:57 cyrus lmtpunix[14954]:
21 matches
Mail list logo
