Обсуждение: palloc failures...still...

Поиск
Список
Период
Сортировка

palloc failures...still...

От
The Hermit Hacker
Дата:
Morning everyone...

    After upgrading the server to -current, which is meant for
release on April 15th, I'm still receiving a palloc() failure, as shown
below.

    The server is a 486DX with 64Meg of RAM, and the able that is
being searched is *only* 5k records large...and the query below will
return *only* 1 of those records...

Apr 10 01:59:47 clio radiusd[22585]: query failed: select uniq_id from \
    radlog where uniq_id='237286618' and stop_time=0 and \
    term_server='isdn-1.trends.ca';
Apr 10 01:59:47 clio radiusd[22585]: query failed: FATAL 1:  palloc \
    failure: memory exhausted


    And, I'm still getting alot of:

FATAL 1:  btree: BTP_CHAIN flag was expected
FATAL 1:  btree: BTP_CHAIN flag was expected
FATAL 1:  btree: BTP_CHAIN flag was expected
FATAL 1:  btree: BTP_CHAIN flag was expected
FATAL 1:  btree: BTP_CHAIN flag was expected
FATAL 1:  btree: BTP_CHAIN flag was expected
FATAL 1:  btree: BTP_CHAIN flag was expected
FATAL 1:  btree: BTP_CHAIN flag was expected
FATAL 1:  btree: BTP_CHAIN flag was expected

Re: [HACKERS] palloc failures...still...

От
Bruce Momjian
Дата:
> Apr 10 01:59:47 clio radiusd[22585]: query failed: select uniq_id from \
>     radlog where uniq_id='237286618' and stop_time=0 and \
>     term_server='isdn-1.trends.ca';
> Apr 10 01:59:47 clio radiusd[22585]: query failed: FATAL 1:  palloc \
>     failure: memory exhausted
>
>
>     And, I'm still getting alot of:
>
> FATAL 1:  btree: BTP_CHAIN flag was expected
> FATAL 1:  btree: BTP_CHAIN flag was expected
> FATAL 1:  btree: BTP_CHAIN flag was expected
> FATAL 1:  btree: BTP_CHAIN flag was expected
> FATAL 1:  btree: BTP_CHAIN flag was expected
> FATAL 1:  btree: BTP_CHAIN flag was expected
> FATAL 1:  btree: BTP_CHAIN flag was expected
> FATAL 1:  btree: BTP_CHAIN flag was expected
> FATAL 1:  btree: BTP_CHAIN flag was expected
>

Man, Marc, you get the strangest errors.  Time for dump/restore to clean
up whatever strangeness you have in that database.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

Re: [HACKERS] palloc failures...still...

От
The Hermit Hacker
Дата:
On Fri, 10 Apr 1998, Bruce Momjian wrote:

> > Apr 10 01:59:47 clio radiusd[22585]: query failed: select uniq_id from \
> >     radlog where uniq_id='237286618' and stop_time=0 and \
> >     term_server='isdn-1.trends.ca';
> > Apr 10 01:59:47 clio radiusd[22585]: query failed: FATAL 1:  palloc \
> >     failure: memory exhausted
> >
> >
> >     And, I'm still getting alot of:
> >
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> > FATAL 1:  btree: BTP_CHAIN flag was expected
> >
>
> Man, Marc, you get the strangest errors.  Time for dump/restore to clean
> up whatever strangeness you have in that database.

    that is easier said then done :(  the last time I did do that, but
the problem creeped back again...but even ignoring the BTP_CHAIN error,
what about the palloc failure still?

    Guess I just found my "release trigger"...this database working
properly :)


Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org