[BlueOnyx:02757] Re: UNKNOWN ERROR DURING CREATE

[Michael Stauber]

Hi Jason,

> If I try to add a user I get this error "UNKNOWN ERROR DURING CREATE"
>
> Messages log shows
>
> Oct 29 16:21:40 server10107 cced(smd)[26262]: client 6:[48:31650]: CREATE
>  "User" "fullName" "=" "Mathew" "ftpDisabled" "=" "0" "capLevels" "=" ""
> "sortName" "=" "" "emailDisabled" "=" "0" "volume" "=" "/home"
> "description" "=" "" "name" "=" "sr_mathew" "password" "=" xxx
> "stylePreference" "=" "BlueOnyx" "site" "=" "site18" "enabled" "=" "1"
> "localePreference" "=" "browser" Oct 29 16:21:40 server10107
> cced(smd)[26262]: client 6:[48:31650]: CREATE User failed (-7)
>
> I have tried dbrecover and cced.init restart and no joy.

dbrecover has no effect on BlueOnyx, as our PAM doesn't use the Berkley DB 
backend.

There are two common reasons for "Unknown error during create":


1.)  User database is locked.

Whenever the user database is written to, the lockfile /etc/passwd.lock is 
created to make sure only one process has write access to the user database. 
After that process is done, the database is unlocked again by removing said 
lockfile. Should that process terminate prematurely, the lockfile may remain 
behind. Which is undesireable.

However, there is a cronjob that checks for stale lockfiles every 15 minutes 
and which runs this script:

	/usr/sausalito/sbin/remove_passwd_lock.sh

That script will delete /etc/passwd.lock if that file is older than one 
minute. So if that is/was your problem, then it'll go away by itself after no 
more than 15 minutes at the most. To speed it up you can run the above script 
manually.


2.) Problems with Sendmail's virtual user table:

If the GUI is unable to add or modify the virtusertable and cannot rehash it 
without errors, it'll also generate an "Unknown error during create".

To check this, rehash the virtusertable manually from the command line:

makemap hash /etc/mail/virtusertable.db < /etc/mail/virtusertable

If that doesn't go through without an error, then you must edit the 
conflicting lines in /etc/mail/virtusertable and then re-hash again. The 
command usually tells you in which lines of /etc/mail/virtusertable the errors 
are.

-- 
With best regards

Michael Stauber