[Prev][Next][Index][Thread]

# [SERVER] Crash on restart with 1.7.9p2 and MPL 1.4

- Date: Mon, 1 Jan 1996 11:05:49 PST
- From:
- Content-Type: text/plain; charset="us-ascii"

    Hi,

    I complied 1.7.9p2 and the MPL 1.4 on a Sparc20 (latest version of Solaris
    running), the compilation went fine, but:

    [60]tecfasun1% moo LambdaCore-25Dec95.db test3.db 1984 &
    %< snip %<
    Jan  1 19:52:55: LOADING: Reading forked and suspended tasks...
    Jan  1 19:52:55: LOADING: Reading list of formerly active connections...
    Jan  1 19:52:55: LOADING: LambdaCore-25Dec95.db done, will dump new database on
    test3.db
    Jan  1 19:52:55: *** PANIC: Caught signal 11
    Jan  1 19:52:55: PANIC-DUMPING on test3.db.PANIC ...
    Jan  1 19:53:03: PANIC-DUMPING on test3.db.PANIC finished

    [61]tecfasun1% moo test3.db.PANIC test4.db 1984 &
    %< snip %<
    Jan  1 19:53:38: LOADING: Reading forked and suspended tasks...
    Jan  1 19:53:38: LOADING: Reading list of formerly active connections...
    Jan  1 19:53:38: LOADING: test3.db.PANIC done, will dump new database on test4.d
    b

    No problem. If I connect, @dump-d, kill the process and restart the moo
    form the dump it will PANIC again... but restarting from the PANIC dump
    works fine...

    Could the conflic be between MPL and what 1.7.9 does when it deal with the
    formerly active connections ?

    TIA

    Richard

    P.S. Yes I tested my cmpiled version of 1.7.9p2 before applying the MPL
    patch and it worked just fine...

    ---
    "640K ought to be enough for anybody."
        -- Bill Gates, 1981

Follow-Ups:

- Re: [SERVER] Crash on restart with 1.7.9p2 and MPL 1.4

- From: Brad Roberts <braddr@puremagic.com>

- Prev: Re: [server] $server_options
- Next: Re: [SERVER] Crash on restart with 1.7.9p2 and MPL 1.4
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index