Index: [Article Count Order] [Thread]

Date:  Tue, 24 Oct 2006 00:27:23 +0200
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:07690] Re: Problems after yum update - further info
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200610240027.24398.bq (at mark) solarspeed.net>
In-Reply-To:  <00e201c6f6e5$7d968d00$03002c0a@WebHoster>
References:  <00e201c6f6e5$7d968d00$03002c0a@WebHoster>
X-Mail-Count: 07690

Hi Gavin,

> ok further tweaking tells me that this is possibly a CCE error/problem
>
> If I restart CCE I can do get disk info to come up but if I try to
> add/delete/suspend a site then it stops.
>
> Crucially I notice that if I restart CCE the firewall comes back on despite
> it being turned off suggesting that its not being stored somewhere. As well
> as a users vacation responder that I had turned off as it seemed to using
> 25% CPU twice over.
>
> Any ideas?

Generally that built in firewall is quite a hassle. I've seen the same issues 
you're having with it on several customer servers. I usually resorted to 
uninstall the respective RPMs. However, before doing so you should stop and 
disable the firewall through the GUI first of all and have to double check 
that the firewall rules are no longer active in memory.

Now as for CCE/GUI hanging or erroring out on add/delete/modify:

You need to check /var/log/messages for error and status messages. Just login 
by ssh as admin, "su -" to gain root access and do a "tail 
-f /var/log/messages". Then go to the GUI and try to make one of the changes 
that you know is not working (like adding a user).

/var/log/messages will show you what's being done and you will see all the 
various handlers doing their job. It will also tell you which handler failed 
if there is a problem. Based on the name of the handler one could then start 
to zero in on the source of the problem.

Common causes for errors during user/site add/delete/modify transactions are 
problems with the email aliasses / virtusertable (also includes Majordomo 
mapfiles). Especially if these files have been tampered with manually.

But there are also other problems that can arise, but 
checking /var/log/messages may provide the initial cues to get started on 
debugging the problem.

It will also show you the exact queries that were run against CCE, so one 
could use /usr/sausalito/bin/cceclient and try to run the same query manually 
against it for further diagnosis and more detailed error messages - provided 
that the problem is centered around a corruption of CODB (the database 
backend of CCE).

-- 

With best regards,

Michael Stauber