Something extremely odd happened to me recently.

one of my cobalts decided it wanted to delete the siteadmin GUI, thats the first odd thing...

then it decided it was going to delete all email alias servers on the cobalt raq.

so I had to go into each domain seperatly and enter the email alias servers for each to get email to work again.........

and the GUI rackshack had to rebuild.

What the hell would cause such a error?

Hy,

perhaps an Hacker or some script which has to much rights. Perhaps a user with the wrong rights on the system ?

Have you updated your bind and proftpd packages and installed all patches from cobalt ? What did the logfiles say what happened ? There specialy

/var/log/messages
/var/log/maillog
the httpd error log
/root/.bash_history

Make sure for first you have installed all cobalt patches and are not using telnet as admin/root. Telnet has no encryption so everybody can read your password (if somebody wants to). Use ssh instead of telnet.

Greetings
Oliver

P.S. If you have installed all cobalt patches you're not save anyhow. One of our boxes was opened 2 weeks ago, this box has all cobalt patches installed and was running portsentry and logcheck and a simple firewall.

we have all updates, and we use SSH

its not a hacker.... it was a raq error... something to do with the server itself, possibly a conflict with another raq script

Hmmm,

have you updated perl ? This could be a reason why the GUI goes bad.

Perhaps the server crashed while something was updated through the GUI and all was deleted but never restored because the GUI was broken ?

No i think thats all very unthinkable. What do you mean when you said : "a conflict with another raq script" ? Which other RAQ Scripts ? Did you use selfmade scripts on your server ?

Greetings
Olly

The problems are related to Postgres, and typically happen
when your server crashes, is shut down improperly or loses
power. The Postgres database and the system files go out
of sync, resulting in the problems you experienced.

There is a meta-verify script you should run if you notice any
"anomolies" like this. Then there is a fixsite script that will
rebuild the siteadmin pages you require.

Unfortunately, neither will resolve the email server alias
problem. This is a known limitation, and the only solution
(as you discovered) is to correct each site manually.

This happend to one of our development boxes. A power failure killed of the server in the middle of the night and the machine failed to shutdown properly while running on the UPS. The GUI was hosed but we used the fixsite tools and everything came back up.