I have problems with a Raq3i, 512MB.
When we got the server we installed PHP, Mysql, Neomail and the latest Webalizer. No patches have been applied for the last two month. There server was just perfect the first 3 month.
There are max. 35 sites on the server with a average server load of 0.00 - 0.5 and a monthly tranfer of max. 20gigs. There's enough space on the partitions and no domains have been added for at least 2 month.
Last month the server started rebooting twice a week and now it reboots nearly twice a day!!! :eek2:
I also noticed that I cannot access the Disk Usage from the control panel and the postgres database appears to have an error.
Support says the can rebuilt it but that's not the point.
What can i do without having the machine rebuilt? :(

Your postgres database can be rebuilt without your server being reset, Tera-byte got cobalt to fix it for me when i had a problem displaying diskpace in the control panel.

Your rebbots are happening either because of the kernal your using or you have a faulty switch on your RAQ.

I have rebuilt the postgres database on my own. Why paying for support? :D Looks like it works now. :o
Will see if the error comes back again. :rolleyes:

Another question:
What could cause a server error clicking on the "Disk Usage" in the administration panel?

What commands did you use to rebuild the postgres database?

Also if your server keeps rebooting check to make sure the fans are working properly. We had a RaQ3 that would reboot everyday. We found out the server was overheating. We replaced one of the fans and everything is working fine again.

Regards
Mike

I think you can use the "system & database verification and integrity check utility" avaible
here (ftp://ftp.cobaltnet.com/pub/users/duncan/raq3/meta-verify.pl) to repair the cobalts system database....

Originally posted by Michael
What commands did you use to rebuild the postgres database?

Also if your server keeps rebooting check to make sure the fans are working properly. We had a RaQ3 that would reboot everyday. We found out the server was overheating. We replaced one of the fans and everything is working fine again.

Regards
Mike


su to 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
/usr/local/sbin/swatch


Now up for +2 days and counting...:D