On 25/11/16 12:02, Martin Babinsky wrote:
On 11/25/2016 12:48 PM, lejeczek wrote:
On 25/11/16 07:52, Martin Babinsky wrote:
On 11/24/2016 07:30 PM, lejeczek wrote:
On 24/11/16 17:14, lejeczek wrote:
I see this:
2 ranges matched
Range name: xx.id_range
First Posix ID of the range: 1952400000
Number of IDs in the range: 200000
First RID of the corresponding RID range: 0
Domain SID of the trusted domain:
Range type: Active Directory domain range
Range name: xx.xx.xx.xx.x_id_range
First Posix ID of the range: 1875000000
Number of IDs in the range: 200000
First RID of the corresponding RID range: 1000
First RID of the secondary RID range: 100000000
Range type: local domain range
Number of entries returned 2
some time ago when I first set up IPA I migrated users
ldap backend. Since then until today there was no new
users I needed
to add but now I do.
First on the list range I think it is a remnant of AD
trust which does
not exists any more (should it be removed?).
I'm not sure how to read those ranges info, one thing
I notice is that
UIDs from migration are probably between 500 & 2000
and now if I
supply uid manually to user-add and gid (which is old
users group) then creation of new user succeeds.
Is this normal, expected?
ok, solution(ldapmodify) to the problem:
but could some experts shed more light on it - I see
that some time
ago(after migration/import) I actually created manually
$ id netdevadmin
today, after ldapmodify I create a new user but uids
seem to come from
(what?) a different range??
$ id appmgr
uid=3501(appmgr) gid=3501(appmgr) groups=3501(appmgr)
what's is happening?
You are seeing this because you probably set s too low
(5000 or so)
and, as tha name of the attribute implies, it sets the
for the range assigned by the plugin.
By default, the local IPA ID ranges are set to huge
numbers (on my
test VMs I have dnaMaxValue 241799999) to aviod
UIDs/GIDs of local users which are typically in the
thousands/tens of thousands).
However, the changes done directly in the DNA plugin
not reflected in ID range objects, that's why you may
disparity between ID range characteristics and actual
can you guess what changed those dnaMaxValue after initial
setup/installation (soon after I created
was assigned by IPA)? It certainly was not me.
Well, you wrote:
> ok, solution(ldapmodify) to the problem:
so I guess you indeed changed the value by running
well, I did but only now, hoping to fix:
ipa: ERROR: Operations error: Allocation of a new value for
range cn=posix ids,cn=distributed numeric assignment
plugin,cn=plugins,cn=config failed! Unable to proceed.
and before I did, those values were:
# Posix IDs, Distributed Numeric Assignment Plugin, plugins,
dn: cn=Posix IDs,cn=Distributed Numeric Assignment
cn: Posix IDs
so, would you say what should be the value of dnaMaxValue in
case of that rage my IPA shows?
I general, I would not meddle with DNA plugin settings
unless something is seriously wrong (like a replica that
did not receive any DNA range block before the master was
decomissioned, se ), and even then I would be extra
careful to set the DNA plugin ranges to correspond to the
actual IPA ID ranges to avoid any UID/GID collisions
(which can get nasty very quickly).
Should I worry about these disparities? Should I be setting
dnaMaxValue(and any relavent) to correspond to idrange(s)?
Lastly, I see my IPA has two ranges, one is from AD trust
which has been
removed, is it ok to leave/keep that range?
The leftover range from AD does no harm, you can safely
remove it just to avoid confusion.
Manage your subscription for the Freeipa-users mailing list:
Go to http://freeipa.org for more info on the project