LFCS · Question #164
An administrator is adding several LDIF files to the directory with slapadd, and the new entries are not displayed when ldapsearch is used. Assuming that there is no database corruption, what is the…
The correct answer is A. Stop the slapd process and add the files again with slapadd. If slapadd entries are not visible after addition, the slapd process must be stopped before running slapadd again, and then restarted for the new entries to be correctly recognized.
Question
Options
- AStop the slapd process and add the files again with slapadd.
- BRun slaprefresh_all.
- CRun ldaprefresh_all.
- DStop the slapd process, run slapindex, and then correct the entries using slap_vacuum.
How the community answered
(59 responses)- A71% (42)
- B3% (2)
- C8% (5)
- D17% (10)
Why each option
If `slapadd` entries are not visible after addition, the `slapd` process must be stopped before running `slapadd` again, and then restarted for the new entries to be correctly recognized.
`slapadd` is designed for offline database manipulation, meaning the `slapd` server process must not be running when it is executed. If `slapd` is active, any changes made by `slapadd` will not be reflected in the live directory service until the server is properly shut down and then restarted, allowing it to re-initialize its database cache with the new data.
`slaprefresh_all` is not a recognized OpenLDAP command for refreshing the database after an offline addition.
`ldaprefresh_all` is not a standard OpenLDAP command; no such utility exists to refresh a running LDAP server's database in this manner.
While `slapindex` can rebuild indexes, `slap_vacuum` is not a standard OpenLDAP tool, and the core problem with `slapadd` is its requirement for the server to be offline, rather than an indexing or defragmentation issue.
Concept tested: OpenLDAP slapadd usage
Topics
Community Discussion
No community discussion yet for this question.