Borresen, John - 0442 - MITLL wrote:
Thanks, Quanah;
As requested:
That was clearly not the problem; if the syncprov module was missing your config would have caused slapd to fail to start. Also it was clearly present since you had it updating the contextCSN in your shutdown log. Quanah, you should have already seen that and not sent him on a wild goose chase.
And, one more time: DO NOT DIRECTLY ACCESS THE FILES IN THE CONFIG DIRECTORY.
Use the database administration tools. For your previous case, you should have simply used: slapcat -s olcDatabase={1}bdb,cn=config
Make sure the consumer is talking to the server you think it is. Show slapd -d7 output from the provider while the consumer is trying to connect.