Problems with omldapsync

[Derek]

Code: Select all

INPUT: Please enter an option (0):2
/opt/scalix/bin/omldapsync: eval: line 582: unexpected EOF while looking for matching `''
/opt/scalix/bin/omldapsync: eval: line 583: syntax error: unexpected end of file
2006-07-17 11:18:49 STATUS: LDAP dir sync import abcdc04 started ###############
2006-07-17 11:18:49 STATUS: load all records from abcdc04.corp.abc.com ...
2006-07-17 11:18:50 INFO: work dir is /var/opt/scalix/ldapsync/abcdc04/import
2006-07-17 11:18:50 STATUS: search source directory on abcdc04.corp.abc.com ...
2006-07-17 11:18:50 INFO: search base is cn=users,dc=corp,dc=abc,dc=com
2006-07-17 11:18:50 INFO: ... 1 entries to check
[...snipped...]
2006-07-17 11:18:52 STATUS: find delta and perform mapping ...
grep: delete.curr: No such file or directory
2006-07-17 11:18:52 INFO: ... 0 entries to delete
grep: add.curr: No such file or directory
2006-07-17 11:18:52 INFO: ... 0 entries to add
grep: modify.curr: No such file or directory
2006-07-17 11:18:52 INFO: ... 0 entries to modify
cp: cannot stat `modify.curr': No such file or directory
2006-07-17 11:18:52 STATUS: apply membdelete data against Scalix ...
/opt/scalix/bin/omldapsync: line 1440: member.curr: No such file or directory


Ran omcheck and it didn't report any permissions issues. Any ideas?

[NetoMeter]

Here is how I sync AD with Scalix - step2:
http://www.netometer.net/video/tutorial ... /index.php

Dean

[Derek]

This should probably just be a new post, but I have another question.

Right now, our AD is kind of a mess. I mean, it's not that bad, but there are inconsistencies between new and older users (with respect to when they were added to the system).

Part of the problem is that close to half of our users do not have complete fields for given name and surname. For all but a handful, the display name attribute is complete, however. So I wrote a script to go through and fix these entries in AD, easy enough and I don't even know Windows scripting.

I'm debating whether or not to fix these same users' DNs, as they're just "CN=SurName,DC=whatever....", but I don't know if that's necessary. And if that works for Scalix, I'm don't want to waste my time fixing something that's not truly broken.

So my question is, what does scalix need in terms of AD attributes? Our email format is going to be " [G] [S] <[G].[S]@domain.com>". What role, if any, does the DN play with omldapsync?

Thanks in advance

[Derek]

Heh, well I guess I'll answer my own questions in case others run into this.

My problem with omldapsync stemmed from a bad configuration file, not a bad configuration. Somehow one of the many commented lines in the sync.cfg got messed up...sloppy fingers I guess.

One of the lines starting with a "#" got changed to a "1" and it produced the errors as shown above. I didn't catch this until I looked at the file after I installed vim-enhanced, and then it was rather stupidly obvious.

From the best that I can tell, omldapsync and the (mostly) default sync.cfg don't care about the DN. However, it does yell if you are missing the first and last name (given and surnames in LDAP jargon).

For whatever reason, not until recently my company didn't fill in these fields, just the "Display Name".

I wrote a VBS to do the following:
- Derive the given and surname from the display name
- Create the "scalixEmailAddress" value
- Set the "scalixObject" to true
- Set the "scalixMailNode" (we only have one, at this time)
- Prompts you on each AD entry change

Should anyone think this could be useful for them, let me know and I'll post it.