#87 bogofilter-0.93.1 crashes Red Hat 7.3 system

closed-works-for-me
nobody
None
5
2004-11-12
2004-11-12
No

I've been using bogofilter through many versions with
no problems. However, I've encountered a serious
problem when trying to upgrade from 0.92.8 to 0.93.1.

Running `make check' will freeze roughly one time in
two, and what's more will bring down the entire system
so that pressing the reset button is the only solution.

It does not happen at the same place in the check
procedure every time. For example, in one case the last
message was "PASS: t.lock1". Next time, the problems
began after "PASS: t.abort".

The machine in question is a Red Hat 7.3 system; kernel
2.4.20-37.7.legacy, db version 3.3.11. The directory in
which I was building bogofilter is NFS mounted. lockd
is running and HAVE_FCNTL_H is defined in config.h.

What seems to happen is that bogoutil goes into
uninterruptible sleep at some point during the test
procedure. The load on the machine rises to crazy
levels (more than 30); problems develop with NFS and
locking; and after a while the system freezes up. The
only thing I can see in /var/log/messages that looks
relevant are that things like "kernel: lockd: cannot
[un]monitor xxx.xxx.xx.xx" start to appear; but this is
probably a symptom rather than a cause.

I'm aware this report is somewhat vague. Unfortunately,
the only machines I can test this on are the main and
backup servers at work (which is where bogofilter runs
when invoked from procmail). Understandably, I won't be
too popular if I keep crashing these! I can probably
crash the backup server once more though if there is a
useful test that can be run.

If of any use, I can provide the system logs from the
time of the problem; and I also have the bogofilter
build tree in the state it was left during two separate
crashes (checks.xxxx.yyyy directories left around).

The same procedure on a Fedora Core 2 system seems to
work fine. However, I did notice that the test
"t.lock3" failed on one occasion (out of about 10).

Discussion

  • Matthias Andree

    Matthias Andree - 2004-11-12

    Logged In: YES
    user_id=2788

    Bogofilter does not support databases on NFS storage, please
    use local file systems; you can pass a directory for "make
    check" like this:

    make check BF_TESTDIR=/var/tmp

    This assumes /var/tmp is a local file system.

    t.lock* test failures with the error "retry count exceeded,
    giving up" or something to that extent are expected errors,
    just re-run the tests.

    If the problem persists even if the tests are run in a local
    directory, please re-open this bug.

    Note: if bogofilter's "make check" manages to freeze your
    machine so you need to press the reset button, that's
    probably a kernel bug or hardware problem.

     
  • Matthias Andree

    Matthias Andree - 2004-11-12
    • status: open --> closed-works-for-me
     
  • Glenn Morris

    Glenn Morris - 2004-11-12

    Logged In: YES
    user_id=638715

    [not sure if this is how I'm supposed to respond]

    > Bogofilter does not support databases on NFS storage,
    > please use local file systems;

    I'm confused. Is this a separate issue from "Can I share
    wordlists over NFS?" mentioned in the FAQ? Is it still OK
    for me to run bogofilter when wordlist.db is located on an
    NFS mounted directory?

    > make check BF_TESTDIR=/var/tmp

    I'll try that, but may not be able to do so till next week.

    > Note: if bogofilter's "make check" manages to freeze your
    > machine so you need to press the reset button, that's
    > probably a kernel bug or hardware problem.

    Sure - running a program as a normal user should not be able
    to crash the system!

     
  • Glenn Morris

    Glenn Morris - 2004-11-12

    Logged In: YES
    user_id=638715

    > make check BF_TESTDIR=/var/tmp

    OK, with this `make check' worked fine.

    I'm still unsure as to whether I can actually use recent versions of bogofilter any more though. When I invoke bogofilter from procmail, both the bogofilter executable and wordlist.db are accessed via NFS. Is this OK? The FAQ suggests yes, but this issue suggests no. Also, I'm somewhat surprised that I have never encountered this problem with any previous version of bogofilter, and yet have it almost every time with the latest version.

     
  • Matthias Andree

    Matthias Andree - 2004-11-18

    Logged In: YES
    user_id=2788

    bogofilter 0.93.* is different from bogofilter 0.92.* and
    older, because 0.93.* use the Berkeley DB Transactional Data
    Store (for robustness), which uses a "database environment"
    that does not work via NFS. The .db itself should be fine,
    but we don't currently support database files residing in a
    different directory than the environment. See:
    http://www.sleepycat.com/docs/ref/env/remote.html

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks