Date:  Sun, 1 Apr 2007 17:20:25 +0100
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:09411] Re: Question regarding web interface and yum updates on fresh x86_64 install of BQ
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200704011820.25702.bq (at mark) solarspeed.net>
In-Reply-To:  <460AB98C.5060004 (at mark) cyber-wizard.com>
References:  <460AB98C.5060004 (at mark) cyber-wizard.com>
X-Mail-Count: 09411

Hi Albert,

> I performed a BQ installation on an x86_64 platform, ran the command
> "yum update", and was unable to use the web interface. Has anyone else
> encountered this issue? I am attaching notes on the install below, as
> well as the capture of the commands issued when installing/updating the
> system and the end of the adm_error log just after the error occurred,
> before I shut the system down. (Only modification was removal of domain
> name from certificate CommonName error in adm_error notes.)

No promise that it will work, but this is  worth a try: 
Edit /etc/admserv/conf/httpd.conf and comment out the line shown below:

LoadModule unique_id_module modules/mod_unique_id.so

Next restart AdmServ:

/etc/init.d/admserv restart

Then try to connect to the GUI interface again. 

I've had some (rare!) cases where a box running on private IPs didn't want to 
run AdmServ - especially if the IP had no DNS record yet. I never fully 
understood what mod_unique_id had to do with that (as it's use for other 
purposes), but uncommenting it in the Apache configuration for AdmServ solved 
the issue.

-- 
With best regards,

Michael Stauber
http://www.solarspeed.net