I just realised version you are on (1.2.x) doesn't have auditfail logs, so you'll need to get the original entry that the persons input was so we can see what's going wrong. We mean we need to see the ldif that they tried to apply - any application, gui, cli, they will all eventually try to emit and apply an ldif to the directory if they are attempting a change. That's what we'll need to see. Hope that helps, > On 30 Aug 2020, at 21:03, Thaddeus Brown <thadbrownsc@xxxxxxxxx> wrote: > > Okay. How would I turn on auditing? Also I am not sure about the entry? I am reaching out to the person who made it to see what the input was? I am assuming you mean if entered in from a GUI, command line or application what fields did they input or type in? > > On Fri, Aug 28, 2020 at 8:20 PM William Brown <wbrown@xxxxxxx> wrote: > You can also turn on the audit and auditerror logs to see more about the failing entry and the results too. :) > > But as mark said, can we see the entry you are trying to add? > > > On 29 Aug 2020, at 01:20, Mark Reynolds <mreynolds@xxxxxxxxxx> wrote: > > > > Something about the entry you are adding is incorrect. Can you provide the entry so we can look it over? Looks like you have an attribute "c" with an invalid value(missing value?), but we need to see the entry to confirm... > > > > On 8/28/20 11:08 AM, Thad wrote: > >> I am working with rh 9.1/389 1.2.11.15 and getting a syntax error. I am still in newbie phase of working with directory server so not sure how to determine the the syntax error and where to look to determine what the user did wrong. Any help figuring it out (and links to tutorials) would be appreciated. > >> > >> Output from log file: > >> > >> [27/Aug/2020:16:14:49 -0400] conn=1969 TLS1.0 128-bit AES > >> [27/Aug/2020:16:14:49 -0400] conn=1969 op=0 BIND dn="uid=mboone1,o=OUR Employees,o=OUR.com" method=128 version=3 > >> [27/Aug/2020:16:14:49 -0400] conn=1969 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn="uid=mboone1,o=our employees,o=OUR.com" > >> [27/Aug/2020:16:14:49 -0400] conn=1969 op=1 ADD dn="uid=eboone,o=OUR Employees,o=OUR.com" > >> [27/Aug/2020:16:14:49 -0400] conn=1969 op=1 RESULT err=21 tag=105 nentries=0 etime=0 - c: value #0 invalid per syntax > >> [27/Aug/2020:16:14:49 -0400] conn=1969 op=2 UNBIND > >> [27/Aug/2020:16:14:49 -0400] conn=1969 op=2 fd=67 closed - U1 > >> _______________________________________________ > >> 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > >> To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > >> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > >> List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx > > > > -- > > > > 389 Directory Server Development Team > > _______________________________________________ > > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx > > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx > > — > Sincerely, > > William Brown > > Senior Software Engineer, 389 Directory Server > SUSE Labs > — Sincerely, William Brown Senior Software Engineer, 389 Directory Server SUSE Labs _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
