Re: [cobalt-users] All kinds of fun errors - RaQ3i

["ISOC Administrator" <admin@xxxxxxxx>]

The PostGreSQL database is corrupt. I had the same internal server error
on mine and called support on it and they fixed it remotely for me.


----- Original Message -----
From: "David" <david_dean@xxxxxxx>
To: "Cobalt User Group" <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Wednesday, July 19, 2000 4:47 PM
Subject: [cobalt-users] All kinds of fun errors - RaQ3i


> Hello Group,
>
> I've discovered a few little issues/errors with our RaQ3i this afternoon
and
> was wondering if anyone could shed some light on the possible causes.
>
> Two days ago while attempting to check disk space via the main admin panel
> (site usage >> disk), the "DISK SPACE" option returned an internal server
> error when selected. -- so then while checking the messages in the "admin"
> mail spool I noticed the following regarding "vacuum cleaners"...
>
> *******************************
> META vacuum - FAIL: ERROR:  Can't create lock file.  Is another vacuum
cleaner
> running?
>         If not, you may remove the pg_vlock file in the
> /home/pgsql/base/cobalt directory
>
> NOTICE:  Index pg_attribute_relid_attnum_index: NUMBER OF INDEX' TUPLES
(574)
> IS NOT THE SAME AS HEAP' (561)
> NOTICE:  Index pg_attribute_relid_attnam_index: NUMBER OF INDEX' TUPLES
(574)
> IS NOT THE SAME AS HEAP' (561)
> NOTICE:  Index pg_attribute_attrelid_index: NUMBER OF INDEX' TUPLES (574)
IS
> NOT THE SAME AS HEAP' (561)
> NOTICE:  Index pg_attribute_relid_attnum_index: NUMBER OF INDEX' TUPLES
(574)
> IS NOT THE SAME AS HEAP' (561)
> NOTICE:  Index pg_attribute_relid_attnam_index: NUMBER OF INDEX' TUPLES
(574)
> IS NOT THE SAME AS HEAP' (561)
> NOTICE:  Message from PostgreSQL backend:
>         The Postmaster has informed me that some other backend died
abnormally
> and possibly corrupted shared memory.
>         I have rolled back the current transaction and am going to
terminate
> your database system connection and exit.
>         Please reconnect to the database system and repeat your query.
> META vacuum - FAIL: pqReadData() -- backend closed the channel
unexpectedly.
>         This probably means the backend terminated abnormally
>         before or while processing the request.
> *******************************
>
> ---THEN--- I noticed that any domain I have listed in my virtusertable
> regarding domains that I have mirrored on the system, is no longer working
> (e.g., you can't send mail to a mirrored domain and have the mail
delivered to
> the master domain as noted in the edit portion of the virtusertable). All
my
> edits for mirrored domains in virtusertable is under the section that
reads:
>
> # Put custom additions below (Do not change/remove this line).
>
> and follow the proper format of:
>
> ## mirrored.com --> main_domain.com ##
> @mirrored.com        %1@xxxxxxxxxxxxxxx
>
> If you send mail to xxx@xxxxxxxxxxxx instead of it being delivered to
> main_doamin.com (the way it use to be), it now just bounces back to the
sender
> stating: "relaying denied".
>
> Does anyone have any idea what's going on.. and/or what could have caused
> these new little issues? It seems it's something new every week. Man I
sure
> miss that old beige web server I traded in on this RaQ3i. It had a Celeron
266
> with 64 megs RAM and it held up without so much as a reboot for over last
two
> years... I'd just like to see one solid month of service off this RaQ3
without
> any new problems or issues (with it's 256 RAM)... <argh>...
>
> -David
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
>
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>