On 11/18/2015 09:34 PM, Hal Deadman wrote: > I have been working with an embedded server in Apache Directory Studio and > I can't find where errors are being logged. The apacheds.log in > > ~\.ApacheDirectoryStudio\.metadata\.plugins\org.apache.directory.studio.ldapservers\servers\18bece68-7767-419d-ae17-1e97a7544984\log > > is empty. > > Is there a way to configure logging so that I can see why the server > doesn't start? I can re-create the server and re-import the configuration > fairly easily but it would be nice if I could figure out why the server > isn't starting.
I would say you found a bug. I was able to reproduce. When creating a server there is a conf/log4j.properties file where logging is configured. When starting the server immediately after creation the "admin password" warning is logged to logs/apacheds.log. But, as soon as one changes the configuration via the config editor in Studio the conf/log4j.properties file is deleted and afterwards nothing is logged at all! Workaround would be create the server, save the log4j.properties file, and restore it after changes in configuration but before starting the server. Do you mind filing a bug? > On another topic, when I made my partition use Mavibot and did an LDIF > import of about 1000 users (and some groups), it was slow to the point of > being unusable. I have since switched to JDBM. Is that a known issue or > should I be able to import 1000 users reasonably quickly? I don't think I > ever got an entire import to work before I switched (had to resolve some > errors) but it was an order of magnitude slower in Mavibot. No idea here, but Mavibot experts should know...
