Unknown syslog message

Rainer von Bongartz — Fri, 08 Mar 2002 08:42:34 GMT

I received the following syslog messages and cant't image where it comes from

Mar 6 15:53:48 neptun syslog: Failed to write log, error -5956 (The device for
storing the file is full.): [06/Mar/2002:15:53:47 +0100] - Serious Error---Faile
d in deadlock detect (aborted at 0x0), err=-30989 (DB_RUNRECOVERY: Fatal error,
run database recovery

Any ideas what this means or from which system this message comes ???

Regards
Rainer

Re: Unknown syslog message

Steve Steel — Fri, 08 Mar 2002 08:48:49 GMT

Hi

See

http://www.sleepycat.com/update/2.5.9/if.2.5.9.html

Are you running berkeley

Berkeley DB Environment failures:
There exists a class of errors that Berkeley DB considers fatal to an entire Berkeley DB environment. An example of this type of error is a log write failure due to the disk being out of free space. The only way to recover from these failures is for the application to exit, run recovery of the Berkeley DB environment, and re-enter DB. (It is not strictly necessary that the application exit, although that is the only way to recover system resources, e.g., file descriptors and memory, currently allocated by Berkeley DB.)

In previous Berkeley DB releases, the only way an application could determine that a fatal error had occurred was to monitor Berkeley DB function return values, looking for unexpected ones, such as ENOSPC, or EPERM (which has historically been returned by Berkeley DB to indicate a potential underlying database corruption).

As of this release, we have added a new error return value, DB_RUNRECOVERY. This error can be returned by any Berkeley DB interface. If a fatal error occurs, DB_RUNRECOVERY will then be returned from all subsequent DB calls made by any threads or processes participating in the DB environment.

steve steel

topic Unknown syslog message in Operating System - HP-UX

Unknown syslog message

Re: Unknown syslog message