Hi Michael,
First off - Thanks :)
On the server that had a similar problem as the first one only this time it
was:
"Could not get oid for user test"
I actually did the following and found 2 sites with the same user:
find /home/.sites/ -name test
/home/.sites/123/site19/.users/17/test
/home/.sites/132/site21/.users/17/test
I Deleted them and was able to create sites again.
So maybe I it got fixed somehow when the db got recovered on the first
server $Bc`(B“ I don$Bc`QU(B know!!!
Thomas
---------------------------------------
----- Original Message -----
From: "Michael Stauber" <bq (at mark) solarspeed.net>
To: <coba-e (at mark) bluequartz.org>
Sent: Wednesday, May 21, 2008 5:49 PM
Subject: [coba-e:13009] Re: Error creating new site
> Hi Thomas,
>
>> I keep getting this error when trying to create a new site
>>
>> CCE Error:305 WARN "[[base-disk.couldNotGetId,target=site87,id=GID]]"
>
> This problem is not directly related to PAM, Saslauth and/or dbrecover.
> The
> error message is generated by the Perl module Disk.pm, which belongs to
> the
> module base-disk.mod.
>
> See:
>
> http://bluequartz.org/trac/browser/5100R/trunk/ui/base-disk.mod/glue/handlers/Disk.pm#L63
>
> It's generated by line 63 of that code.
>
> When a user or site (group) is created, this handler attempts to set the
> disk
> quota for the site and user in question. In your case it was not possible
> to
> set a disk quota for the group named "site87", because the group doesn't
> exist. And at this point of site creation it SHOULD exist.
>
> The most likely cause for this:
>
> You already once had a site87 on your server, which you deleted. But
> during
> deletion something went wrong and some files and/or directories of that
> old
> site87 were not removed from the system.
>
> Now during creation of a new site the newly needed directories and/or
> files
> cannot be created, because some of the old ones are still in the same
> place.
>
> So you'd need to go through /home/.sites/ and would need to find the old
> files
> and/or directories that belong to the deleted site87 and have to delete
> them
> manually. Afterwards you should be able to create a new site.
>
> This may not work (because group "site87" may not exist as a group on the
> system level), but try to run a search like this for files that belong to
> it:
>
> find /home/.sites/ -group site87
>
> If that turns up anything, you may want to delete it and try again.
>
> If the group doesn't exist on the system level, you can still search for
> it by
> the numerical orphaned group ID, although that's a bit more obscure to
> find.
> Especially if your server hasn't been converted from PAM to Shadow yet.
>
> Well, see if you can find the left over directories and files and if not,
> let
> us know and we figure something out.
>
> --
> With best regards,
>
> Michael Stauber
>
>
>