RE: [cobalt-users] Why do I get 'No virtual host entry for site1' on Site Mgmt Save Changes

["Eric Arseneau" <eat@xxxxxxx>]

Thank you for an EXCELLENT description.  I went ahead and did what you said
and it fixed the problem.  Not only that, it also fixed my mail problem that
I was trying to fix before contacting the list.

I deleted all of my domains, except the root one, and added one of them
again.  The error went away and my mail works.

A question I would have to the rest of the list is
	"Is there an easier way than deleting all of the domains ?"

Maybe go into the db and tweak some values there ?  Anyone know the schema
or how to use the db ?

Thank you all for being so helpfull.

> -----Original Message-----
> From: Carrie Bartkowiak [mailto:admin@xxxxxxxxxxxxxxxxxx]
> Sent: Friday, January 26, 2001 1:06 PM
> To: eat@xxxxxxx
> Subject: RE: [cobalt-users] Why do I get 'No virtual host entry for
> site1' on Site Mgmt Save Changes
>
>
> ||>Every time I press the save changes button on the site
> ||>management screen of
> ||>one of my sites I get a "No virtual host entry for site1" error
> ||>displayed at
> ||>the bottom of my screen.  I have the latest updates installed.
>
> I think that this means that in /home/sites you have a "site1";
> but there's
> no matching domain associated with it in the PostgreSQL database the GUI
> uses.
>
> The backwards version of this happened to me once when I was
> messing with my
> groups file, I think. I didn't leave an extra line at the bottom or
> something, and somehow the GUI got the wrong number when checking to see
> what the next site# should be. So the next site *should* have been site11,
> but the GUI kept trying to make it site10. Since there was
> already a site10
> folder, it kept telling me "virtual host for site10 already exists". (Or
> something close to that.)
> Deleting site10 only fixed it until I tried to add another site,
> then it was
> giving me the error again. I checked my groups file and saw what
> I had done,
> put everything on the correct line, and was good to go.
>
> So check everything and see if there is a domain that matches site1
> (/home/sites/site1); you may want to take out the records of it if they do
> and make sure the site1 directory gets deleted, then try making it again.
> (Or just fix any file you may have changed that deals with site# folders.)
>
> Kinda a Cobalt standard - when in doubt, rip it out; then re-make it.  :)
>
> Carrie Bartkowiak
> Administrator, All @bout Choice
> admin@xxxxxxxxxxxxxxxxxx
> http://www.allaboutchoice.com
>
>