Matthew Toseland [EMAIL PROTECTED] writes:
Well, surprisingly enough, that indicates an error. :)
Did you have 100% CPU usage throughout that period? That is the usual
cause...
I don't know about the CPU load. Next time it happens I'll look at the load and
tell you.
Regards,
Jan
Matthew Toseland [EMAIL PROTECTED] writes:
Hmmm. If you get a big one, you're probably getting repeated error
messages... it would be interesting to know what they say.
Well, I also get a large log file (about 100 MB/hour) with the log level set to
Error. The repeated error is Consecutive
Well, surprisingly enough, that indicates an error. :)
Did you have 100% CPU usage throughout that period? That is the usual
cause...
On Wed, Jul 27, 2005 at 01:41:16PM +, Jan Janssen wrote:
Matthew Toseland [EMAIL PROTECTED] writes:
Hmmm. If you get a big one, you're probably
Matthew Toseland [EMAIL PROTECTED] writes:
Newer builds default to logOverwrite=true. This means your logfile
should be wiped every time you restart the node. Is the below still a
problem? How long is your node usually up for? And is there a line in
your config file overriding logOverwrite?
Hmmm. If you get a big one, you're probably getting repeated error
messages... it would be interesting to know what they say.
On Sat, Jul 23, 2005 at 11:00:15PM +, DiamondIce wrote:
Matthew Toseland [EMAIL PROTECTED] writes:
Newer builds default to logOverwrite=true. This means your
