Hi,
Thanks to all who responded with my situation below. Here is what I think
happened.
Sometime late Saturday evening a server started having soft failures on a
memory card. However as a result of the failures syslog messages were
generated that were both stored locally and forwarded onto
On Mon, Mar 10, 2003 at 03:13:30PM -0500, Jim Howell wrote:
> Hi,
> I have an interesting problem. Over the weekend our syslog forwarder went
> beserk generating over 300,000 messages to about 6 people. This morning
> our three new Cyrus systems went belly up, (yes that is a technical ter
At 03:39 PM 3/10/2003 -0500, Lawrence Greenfield wrote:
Date: Mon, 10 Mar 2003 15:13:30 -0500
From: Jim Howell <[EMAIL PROTECTED]>
[...]
This is all with Cyrus 2.1.11 on a V880 with 32GB of memory with
Solaris 8
and, Sendmail 8.12.8. Anyone seen this before? Thanks.
What sort of dat
Hi,
Good idea, but no I didn't run out of inodes.
Jim
At 09:30 PM 3/10/2003 +0100, Nils Vogels wrote:
On Mon, Mar 10, 2003 at 03:13:30PM -0500, Jim Howell wrote:
>
> Now I'm been running older versions of Cyrus (1.5.19) for years at 300,000
> messages a day with no trouble. I don't believe
Date: Mon, 10 Mar 2003 15:13:30 -0500
From: Jim Howell <[EMAIL PROTECTED]>
[...]
This is all with Cyrus 2.1.11 on a V880 with 32GB of memory with Solaris 8
and, Sendmail 8.12.8. Anyone seen this before? Thanks.
What sort of database backend are you using? (cyradm version should help
On Mon, Mar 10, 2003 at 03:13:30PM -0500, Jim Howell wrote:
>
> Now I'm been running older versions of Cyrus (1.5.19) for years at 300,000
> messages a day with no trouble. I don't believe space is really an issue,
> here is a df -k from one of the systems.
Did you by any chance run out of inod
Hi,
I have an interesting problem. Over the weekend our syslog forwarder went
beserk generating over 300,000 messages to about 6 people. This morning
our three new Cyrus systems went belly up, (yes that is a technical term),
actually the master daemon seemed to eventually freeze up. The only
