[cobalt-users] RaQ3-All-System-4.0.1-9819.pkg --> unknown cron message

["Craig Napier" <craignapier@xxxxxxxxxxx>]

Hi Group,

I just got off the line with Cobalt and they had to go in and fix the 
database problem. Prior to calling, I had emailed (earlier in the night) and 
actually recv'd a reply just a few hours later. The tech gave me the 
instructions on how to fix the problem, but I'll share that when I gave it a 
try, I hosed it and had to call Cobalt. I got almost to the end of the 
instructions, and then encountered an error. Once the tech got into my box, 
he said it looked like I had simply commented out the wrong line. The line 
in question is the one:

> find create_table for quota and hash it out ( comment it out )

What's wild, I called support and the very guy that I spoke with (Pawel 
Zygadlo ? great guy and tech support!) was the guy who had just sent me the 
email message with the instructions. He went right in and fixed things right 
up...

I'll post his initial instructions here to the list because there's a whole 
archive full of people that have encountered this problem from time to 
time... If you decide to try this yourself (instead of calling Cobalt), do 
so at your own risk :-) --but-- I personally would call Cobalt because 
there's not a worse feeling in the world (besides being hacked) than seeing 
that you just "dumped" the entire backend database of your machine... IKES!! 
 But for those that want to try, here's his suggestions (good luck)..

==========================================
	Thank you for contacting SUn Microsystems Technical SUpport. If you know a 
little bit of linux here is what you need to do. Otherwise call us and have 
this done (800-266-4378). telnet to the box & become root

cd /home/pgsql
su postgres
edit pg_hba.conf
change crypt to trust
pg_dump cobalt > cobalt.dump
vi cobalt.dump
find create_table for quota and hash it out ( comment it out )
close
destroydb cobalt
createdb cobalt
psql cobalt < cobalt.dump
edit pg_hba.conf
change trust back to crypt
swatch

==========================================

I had no problems down to destroydb cobalt, then I lost it.. :-)  He later 
told me that I had commented out the wrong line in the cobalt.dump file. I 
had commented out a reference to "create_table" for quota towards the top of 
the file (didn't check to see if there were more) and he said the line I 
should have hashed out was towards the bottom. So just look at everything 
first to be sure you've got the correct line.. And keep that 800 handy just 
in case.  :-)

OH BTW -- ONE NOTE.. Have any of you having this problem recently made 
changes to your systems trying to turn-off IMAP? He asked me if I had 
recently made changes to swatch, and I had... I had recently edited 
/usr/admserv/cgi-bin/.cobalt/services/services.cgi to try and disable IMAP 
from being turned back on every 3-4 weeks. And I'm not sure it had anything 
to do with the issue, but when my CRON jobs would hang, it was swatch that 
was hanging... I don't know, just something to consider..  :-)

Cheers!
Craig
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com