<p>Sorry I did not see the last time that error is in schema. I don't know how you did it but you break it. You don't need to panic. Because when you install a dirsrv instance the setup script copies the schema from somewhere... I don't remember from where... it was somewhere in /var or /usr... here are some ideas to get the good copy:<br>
- Red Hat docs will have this info also you can use find command to find this file. <br>
- Installing other dirsrv instance for a moment will create a good copy of this file in its directory. There can be many dirsrv servers on the system. You need to specify diferent port and DN.<br>
- you can read setup-ds and find from where it copies schema files.</p>
<p>I'm traweling at the moment and I cannot give you more details at the moment. I am writing from my phone. I hope this will help.<br></p>
<p>Greg.</p>
<div class="gmail_quote">11 sty 2013 21:06, "Doug Tucker" <<a href="mailto:tuckerd@lyle.smu.edu">tuckerd@lyle.smu.edu</a>> napisa³(a):<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I was excited to see this reply, thanks so much. Unfortunately, I copied that to the dse.ldif and the results are the same. It won't start and with the same error.<br>
<br>
Sincerely,<br>
<br>
Doug Tucker<br>
<br>
On 01/11/2013 11:14 AM, Grzegorz Dwornicki wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
For the record dirsrv creates file in its directory with the last good configuration. I believe it was called dse.ldif.startok<br>
<br>
Greg.<br>
<br>
11 sty 2013 18:06, "Chandan Kumar" <<a href="mailto:chandank.kumar@gmail.com" target="_blank">chandank.kumar@gmail.com</a> <mailto:<a href="mailto:chandank.kumar@gmail.com" target="_blank">chandank.kumar@gmail.<u></u>com</a>>> napisa³(a):<br>
<br>
You may not need to re-install it. If you could just replace the<br>
file that you changed, I hope you took a backup before<br>
experimenting with the file. Same thing happened with me too, I<br>
restored the directory server from the bakcup files.<br>
<br>
On Friday, January 11, 2013, Doug Tucker wrote:<br>
<br>
Well, I give up. I can find nothing in the docs or on google<br>
to get me around this. I'm see no way other than to uninstall<br>
389 and reinstall from scatch so no need to respond to this.<br>
<br>
Sincerely,<br>
<br>
Doug Tucker<br>
<br>
On 01/10/2013 11:19 AM, Doug Tucker wrote:<br>
<br>
So I've gone from bad to worse. Googling and googling and<br>
no response on my auth issue from the list yesterday, I<br>
coudn't stand doing nothing. The only thing I saw that<br>
made me curious was some thread where a guy could not auth<br>
and he changed the password hash to something else and it<br>
worked. I looked at our current password hash in openldap<br>
and it was ssha. For the life of me I could not find how<br>
to see what the current one was in 389. The only thing I<br>
could find in the docs was how to set a password policy<br>
which allowed you to set the hash. So I did so according<br>
to the documentation on the Users cn. The only thing I<br>
did was turn it on, and make sure password hash was set to<br>
ssha. I left the rest default which was no expiration,<br>
etc. I saved, and tried to restart according to the docs,<br>
it woudn't restart. I shut down with the init script<br>
instead, and tried to start, and now I get this:<br>
<br>
[root@lyleauth1 schema]# /etc/init.d/dirsrv start<br>
Starting dirsrv:<br>
lyleauth1...[09/Jan/2013:16:<u></u>23:05 -0600]<br>
dse_read_one_file - The entry cn=schema in file<br>
/etc/dirsrv/slapd-lyleauth1/<u></u>schema/99user.ldif (lineno: 1)<br>
is invalid, error code 21 (Invalid syntax) - attribute<br>
type olcOverlay: Missing parent attribute syntax OID<br>
[09/Jan/2013:16:23:05 -0600] dse - Please edit the file to<br>
correct the reported problems and then restart the server.<br>
[FAILED]<br>
*** Warning: 1 instance(s) failed to start<br>
<br>
Looking at the time stamp on that file, it is: Dec 20<br>
16:36 99user.ldif . So what I did yesterday did not touch<br>
it. Anyone have any idea how to fix this?<br>
<br>
<br>
--<br>
389 users mailing list<br>
<a href="mailto:389-users@lists.fedoraproject.org" target="_blank">389-users@lists.fedoraproject.<u></u>org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/389-users" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/389-users</a><br>
<br>
<br>
<br>
-- <br>
--<br>
<a href="http://about.me/chandank" target="_blank">http://about.me/chandank</a><br>
<br>
<br>
--<br>
389 users mailing list<br>
<a href="mailto:389-users@lists.fedoraproject.org" target="_blank">389-users@lists.fedoraproject.<u></u>org</a><br>
<mailto:<a href="mailto:389-users@lists.fedoraproject.org" target="_blank">389-users@lists.<u></u>fedoraproject.org</a>><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/389-users" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/389-users</a><br>
<br>
<br>
<br>
--<br>
389 users mailing list<br>
<a href="mailto:389-users@lists.fedoraproject.org" target="_blank">389-users@lists.fedoraproject.<u></u>org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/389-users" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/389-users</a><br>
</blockquote>
<br>
--<br>
389 users mailing list<br>
<a href="mailto:389-users@lists.fedoraproject.org" target="_blank">389-users@lists.fedoraproject.<u></u>org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/389-users" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/389-users</a></blockquote></div>