3.0.1pre3 usrmgr fails with create user,
it did work with samba 3
backend = smbpasswd
Created attachment 273 [details]
the logs showed bug with entry
passdb backend = smbpasswd:/etc/samba/smbpasswd, guest
so i removed it but it didnt solved the problem
this conf works stable on suse 8.2 and samba 3 works stable since release,
the user creation now fails after upgrade to 3.0.1pre3
I need a level 10 debug log of the failure.
Created attachment 282 [details]
The lookup_name(moni) call sets the user rid to be 2004
but a later samr_open_user(rid == 2004) fails to match the
rid in the reverse directory (moni has a uid of 503).
This doesn't make sense. The generated RID should be 2006 for uid 503.
What account is uid == 502 ?
the user moni existed before in the system was deleted but not refreshed
with smbpasswd, this problem is not related to the bug.
i noticed that to late please ignore entries about this user.
i can delete users with this setup, create groups, add members to groups,
delete them from groups, and delete groups.
Adding users fails, this works very nice with the same smb.conf on samba
Created attachment 288 [details]
one more log level 10
one more log, only one action was made,
trying a create user from usrmgr,
all acounts are now valid,
Are you getting an error about "group name could not jbe found" ?
ignore comment #8.
I've not been able to reproduce this using your
configuation file. Also I don't see any call
to create a user in the second log file you sent.
Created attachment 290 [details]
failure shot usrmgr
I didnt found anything special in the samba logs too,
in syslog i can find entries for all actions like user delete, group delete
but there is no entry that samba tries to start the useradd command,
so it i guess the problem is the conversation from usermgr
add user script = /usr/sbin/useradd -m %u
/usr/sbin/useradd works nice from command line
the failure message
from usrmgr is "the wanted procedure was not found"
the next logs shows
actions like delete user
add user to group
delete user to group
create group , delete group
and serveral tries to create user ( which fails )
the smaba version is taken from ftp suse com people gd,
installed on suse 9.0
Created attachment 291 [details]
logs with several actions from usrmgr
Created attachment 293 [details]
more logs after the patch
I added the patch "RemoveUserForeignDomain " from bug 252 against current cvs
the rpms and reinstalled it but the problem stays
here more logs level 10
Created attachment 294 [details]
failure with make
After i did not trust my own rpm build process,
i tried make current cvs code with patch to compile traditional way
./configure etc, it does not compile to my system
In file included from include/includes.h:897,
include/proto.h:5720: error: parse error before
make: *** [dynconfig.o] Fehler 1
run 'make proto' and it should clear things up.
Created attachment 295 [details]
logs from working user add
I went more in a deeply test phase.
I rolled back to rpm from suse samba 3, at my setup (conf) user create
So i thought about the difference between the running system and the failure
The difference is:
If i use usrmgr is stored on a samba pdc share, and the win client
is a member of the samba domain user create works ( and all other funktions as
well ) it failes if i start usrgmgr stored on a win machine which is not member
of the samba domain.
It seems to me that this behavior is related to a permission or trust problem.
The logs show that it isnt enough to make a user create with a valid smb domain
user account ( which has admin rights ).
The create command must also started from a machine which is member of the
I am not sure if this behavior is by design of usrmgr or windows.
But in every case there should be an entry in the docs unless this behavior is
At last i can live with workaround , stored usrmgr on smb pdc share.
Maybe this isnt really a bug !!!
In 3.0.1pre3 usrmgr works as described as it did before to version 3.
But i will try the patch with a fresh debian install from the scratch
to see if the behavior changes.
What makes me really astonishing is that usrmgr lets me
delete users, groups in every case , cause this are
major operations ( root related too )
attached are log with the working logs,with serveral actions
( add delete usrmgr ) with version 3.0.1pre3 starting usrmgr from a domain
member machine called smbpc
ok. I'm moving this one to docs. But I still don't see any
CREATE_DOM_USER operation in the success logs.
Created attachment 300 [details]
user create log with usmgr from domain member machine
watch this !
[2003/12/05 00:25:24, 5] lib/username.c:Get_Pwnam_internals(251)
Get_Pwnam_internals didn't find user [tester]!
[2003/12/05 00:25:24, 3] rpc_server/srv_samr_nt.c:_samr_create_user(2311)
_samr_create_user: Running the command `/usr/sbin/useradd -m tester' gave 0
[2003/12/05 00:25:24, 5] lib/username.c:Get_Pwnam(288)
Finding user tester
updating qa contact
(In reply to comment #17)
> Created an attachment (id=300) 
> user create log with usmgr from domain member machine
> watch this !
> [2003/12/05 00:25:24, 5] lib/username.c:Get_Pwnam_internals(251)
> Get_Pwnam_internals didn't find user [tester]!
> [2003/12/05 00:25:24, 3] rpc_server/srv_samr_nt.c:_samr_create_user(2311)
> _samr_create_user: Running the command `/usr/sbin/useradd -m tester' gave 0
> [2003/12/05 00:25:24, 5] lib/username.c:Get_Pwnam(288)
> Finding user tester
Is this still an open issue or can it be closed?
- John T.
Reply received to close this bug.
sorry for the same, cleaning up the database to prevent unecessary reopens of bugs.