LDAP Corruption After Profile Restore Home Page › Forums › Network Management › ZeroShell › LDAP Corruption After Profile Restore Tagged: LDAP SLAPD Profile This topic contains 4 replies, has 2 voices, and was last updated by Stephen Cook 2 months, 3 weeks ago. Viewing 5 posts - 1 through 5 (of 5 total) Author Posts February 7, 2019 at 8:33 pm #64796 Stephen CookParticipant I am attempting to move one of my ZS instances from a Raspberry Pi to a X86. I created a backup of the Profile, and then restored it to the X86 instance. When I reboot I get the following; Starting LDAP daemon… Recovering LDAP DB slapd: no process killed mv: cannot stat ‘__db.*’: No such file or directory db_recover: Ignoring log file: log.0000000001: unsupported log version 19 db_recover: Invalid log file: log.0000000001: Invalid argument db_recover: PANIC: Invalid argument db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery After ZS finished booting, I am unable to login to the web gui. Any assistance would be appreciated. Thank you, Stephen April 23, 2019 at 6:15 am #65081 lala siregarParticipant Stephen, what version of zeroshell did u use? April 23, 2019 at 2:25 pm #65082 Stephen CookParticipant Sorry, my bad! The Raspberry Pi was running 3.9.1a and the x86 was running 3.9.0. April 23, 2019 at 5:47 pm #65086 lala siregarParticipant Okay, ehmm I want to ask u about LDAP. Can LDAP (for user management) connect with Zeroshell 3.8.2 (for captive portal)? April 25, 2019 at 5:55 pm #65090 Stephen CookParticipant I’m afraid I don’t know. I haven’t used the captive portal yet, and haven’t used LDAP for anything at all. Author Posts Viewing 5 posts - 1 through 5 (of 5 total) You must be logged in to reply to this topic.