RE: [cobalt-users] Raq3 with RunAway swatch

["Holstein, Regis \(TDS\)" <regis.holstein@xxxxxxxxxx>]

Hello,

As a matter of fact, I had the same problem 3 months ago - I called Cobalt
and it turned out to be my Postgres database that was corrupted.  They
rebuilt it, and it was fine. That was 3 months ago.  They told me that this
happens once in a while, but chances are fairly slim to have it again.  They
could not give me the exact reason (if any) for the corruption.

HOWEVER, 1 week ago, the same problem occured.  I called Cobalt again, and
said "it's probably the Postgres database, it happened 3 months ago".
After logging into the box via Telnet, the tech got back to me 20 sec after
and said "there you go, it's fixed".  I asked what did you do?  and he
replied "well, I just killed the process" ... duh!?...   I tried to
emphasize that this won't fix it, but he would just not listen and kept
saying my postgres was fine...

Of course, today I still had the same problem.  I called again, and this
time they told me my "admin" POP account was too big and was eating up all
the memory (!!??)...   they still did not even want to look at my postgres
database....   but that was the source of the problem 3 months ago, and I'm
pretty sure it still is.  Last time, it took them 1 minute to fix.

If only I knew how to rebuild the database myself, I would do it.

If anyone has some input, please let us know :-)

Thanks,

Regis J Holstein
TDS Communications
@Solutions for an E-Planet


> -----Original Message-----
> From: cobalt-users-admin@xxxxxxxxxxxxxxx
> [mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Dave
> Sent: 6 juin, 2001 21:35
> To: cobalt-users@xxxxxxxxxxxxxxx
> Subject: [cobalt-users] Raq3 with RunAway swatch
>
>
> Hello All,
>
> I have a mysterious rebooting going on.  It has happened twice in two
> weeks or so.  A check of logs revealed nothing.  I do not run ftp open,
> nor is there a full e-mail box anywhere <comments from another e-mail
> thread with similar rebooting from the security list> .  In fact the raq
> is lightly used- about 30 sites and only a few e-mail boxes.  I ran top
> for a bit and saw nothing- until just a few minutes ago when I saw
> swatch consuming 99% cpu and continually running.  Not that I know what
> I'm doing but I killed swatch only to see it come back and again utilize
> all cpu.  I rebooted ONpurpose and after a few minutes swatch is back
> eating all cpu.  I have all the latest patches except the kernel UPdate.
> It's a rather plain Raq3, no php or mysql- just running the standard
> with portsentry/logcheck.  Only one .cgi script that has been used since
> December with no problems.  Any ideas on a runaway swatch are greatly
> appreciated since the only solution I found in the archives was:
>
> "Since we thought swatch was important and a good watch dog we called
> cobalt and they fixed it. If you are looking to get it fixed, call
> cobalt and tell them that the Postgre database is corrupted and that
> they need to rebuild it"
>
> Thanks for your time,
> Dave~
>
> _______________________________________________
> cobalt-users mailing list
> cobalt-users@xxxxxxxxxxxxxxx
> To Subscribe or Unsubscribe, please go to:
> http://list.cobalt.com/mailman/listinfo/cobalt-users
>