I've upgraded from 1.1.X to 1.2.0, but when looking at console, version
1.1.X still there.
On one server, which doesn't have memborOf plugin in list (1.1.0 install),
still without it, even after upgrade.
How do I upgrade schemas? How do I upgrade the available plugins?
I have a search problem with Fedora DS 1.1.3.
My directory has an extended schema on the objectClass "inetOrgPerson".
It contains 350000 inetOrgPerson objects.
When I proceed a search with that kind of filter (cn=smith*) or
(uid=25698*) the response comes 1 minute later with a error code 11.
Indexes on cn and uid attribute are on equality, presence and
substring. I have recreated (plus reindexed) this attribute.
I put the look-through-limit to infinity though I don't have the errror
code 11 anymore but I have to wait a very long time the response.
In the log, I found "etime=77 notes=U" which means that the search does
not use the indexes.
I have done the same requests with a "native" schema : it works
perfectly. So, it is my extended schema which causes the problem.
Can the Fedora DS (or 389 DS) deal with extended schema ?
Does anybody met this problem ? Is there a solution for forcing FDS to
use the indexes ?
Ce message est protégé par les règles relatives au secret des correspondances. Il est donc établi à destination exclusive de son destinataire. Celui-ci peut donc contenir des informations confidentielles. La divulgation de ces informations est à ce titre rigoureusement interdite. Si vous avez reçu ce message par erreur, merci de le renvoyer à l'expéditeur dont l'adresse e-mail figure ci-dessus et de détruire le message ainsi que toute pièce jointe.
This message is protected by the secrecy of correspondence rules. Therefore, this message is intended solely for the attention of the addressee. This message may contain privileged or confidential information, as such the disclosure of these informations is strictly forbidden. If, by mistake, you have received this message, please return this message to the addressser whose e-mail address is written above and destroy this message and all files attached.
as a new member of this maillist, first of all I'd like to say hello to everybody :).
I have problem with replication on my three Fedora Directory Servers. All three have replication agreements (multiple master model), but in admin console I have following informations:
- with directory1: Incremental update has failed and requires administrator actionSystem error. Error Code: -1
- with directory2: Incremental update has failed and requires administrator actionSystem error. Error Code: -1
- with directory: Incremental update succeeded
- with directory2: Incremental update succeeded
- with directory: Incremental update succeeded
- with directory1: Incremental update succeeded
The problem is, that most of changes are made on server called "directory", but they didn't propagate to others two servers. I have googled for "Incremental update has failed and requires administrator actionSystem error", but results didn't gave me literally nothing. And because I'm not an experienced FDS user, I ask You for some clue(s) on what's going on and how to solve my problem.
Of course I can post more detailed info, but I don't know (yet) which information can have any value for You.
"Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada exclusivamente a seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, por gentileza, reenviá-la ao emitente, esclarecendo o equívoco."
"This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a government company established under Brazilian law (5.615/70) -- is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you're not the addressee, please send it back, elucidating the failure."
We have a setup where we are running 2 servers behind a load balancer
(for HA purposes), where each of these servers is bulk-initialized
daily (via ldif2db.pl) with a large set of data fed to us via batch
extracts from various administrative systems. Up till now, there has
been no need to configure replication between these 2 servers, as all
of the data is read-only. However, we now have a requirement to
update some of the directory data in a "real-time" fashion (e.g., when
particular events fire in our PeopleSoft system we want to update the
directory)--hence, the need for MMR. The batch extracts will still be
our "checkpoints", so we will want to load them in once-per-day, as we
So, the question is: what would be the "recommended" approach for a
scenario like this? How do we (can we?) make MMR coexist peacefully
with frequent bulk initializations?
Senior Enterprise Systems Architect
The University of Arizona, UITS
+1 520 626 5981
where can i find info about pros and cons of posixGroup vs groupOfUniqueNames?
im planning a fresh new directory service and im not sure about what
object to be used for groups.
jabber id: muzzol(a)jabber.dk
No atribueixis qualitats humanes als ordinadors.
No els hi agrada.
"El gobierno español sólo habla con terroristas, homosexuales y
catalanes, a ver cuando se decide a hablar con gente normal"
bomb terrorism bush aznar teletubbies