Hi Dan,
> Has there been any resolution to this issue? Trying to create a site
> failed:
>
> Jun 6 07:24:13 admin cced(smd)[23501]: client 6:[48:10454]: CREATE failed
> Jun 6 07:26:36 admin cced(smd)[23583]: client 0:[48:10469]: AUTHKEY to
> user "" failed
> Jun 6 07:26:51 admin sendmail: sm-client shutdown failed
> Jun 6 07:27:59 admin cced(smd)[23994]: handler
> handlers/base/disk/modquota.pl failed
> Jun 6 07:28:00 admin cced(smd)[23994]: client 6:[48:10469]: CREATE failed
> Jun 6 07:29:09 admin cced(smd)[24339]: handler
> handlers/base/disk/modquota.pl failed
> Jun 6 07:29:10 admin cced(smd)[24339]: client 6:[48:10455]: CREATE failed
>
> Then I get "Unable to get the GID for site70. site70 does not appear to
> exist on the system. "
>
> Is http://www.nuonce.net/support/viewthread.php?tid=1893 the only answer to
> this problem?
Yes and no.
Cause here can be one of two problems:
1.) In the past there was already a site with the group name "site70" on the
server and it got deleted. Unfortunately some files belonging to users of
that group or some files belonging to the group "site70" itself were not
deleted when the site was erased.
Now when you try to create a site and it assigns "site70" as group name, it
first tries to create the webspace (group directory for "site70"), but that
directory may already be present from the previous site with that group name.
There it then runs into an error and anything else destined to happen past
that point during site creation fails.
This case is pretty rare, but can't be ruled out. If this is indeed the
problem, then you need to walk through /home/.sites/ and have to find the
directory which the old site70 belonged to and have to remove it manually.
2.) The more likely cause: Your user and/or group info stored in the PAM
database is corrupted and the group "site70" cannot be created.
In that case one of the easiest solutions would be to convert the box from PAM
to Shadow, as outlined in the forum posting whose URL you posted.
If you're uncomfortable to do the conversion "by hand", then please read this:
http://www.solarspeed.net/otrs/public.pl?Action=PublicFAQ&CategoryID=3&ItemID=38
It offers a much simpler way of converting the system.
Follow the instructions outlined in "YUM based upgrade (recommended) ", which
are really very simple. Once the updates have all been installed, login to
the GUI and click on "Server Management" / "System Settings" / "User
Database".
On that page will be a button, which you can click to perform the conversion
from PAM to Shadow. It does all in one go.
You may of course ask: "But what about all the warning on top of that article,
saying it's Beta?"
Well, it is beta. It's code that i not yet officially released by BlueQuartz,
but it's based on RPMs from the latest SVN code.
Is it tested? Yes. I use it myself and around 250-300 BlueQuartz servers run
it already. Yes, it had some bugs early on, but they've been ironed out
already.
> Or:
> http://bluequartz.org/ml/archive/coba-e/6400/6445.html
> Also a little over my head.
That should already be fixed in the new code as well.
--
With best regards,
Michael Stauber