Reputation: 1
there is a Proxmox 8 installed manually on clean Debian 12 (packages up to date).
We want to run a basic LDAP for numer of apps thus there was an idea to deploy it directly on host and I've executed a basic command:
apt-get install apacheds
It also installed some additional dependencies with default-jre-headless as well.
However apacheds was not starting due to error:
systemctl status apacheds
× apacheds.service - Apache Directory Server
Loaded: loaded (/lib/systemd/system/apacheds.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Mon 2024-05-20 22:02:06 CEST; 1min 20s ago
Duration: 134ms
Process: 351775 ExecStart=/bin/sh -c exec ${JAVA_HOME}/bin/java ${JAVA_OPTS} -Dapacheds.controls=${ADS_CONTROLS} >
Main PID: 351775 (code=exited, status=1/FAILURE)
May 20 22:02:06 lab30 systemd[1]: Started apacheds.service - Apache Directory Server.
May 20 22:02:06 lab30 sh[351775]: Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
May 20 22:02:06 lab30 sh[351775]: at org.apache.directory.server.UberjarMain.<clinit>(UberjarMain.java:48)
May 20 22:02:06 lab30 sh[351775]: Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
May 20 22:02:06 lab30 sh[351775]: at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
May 20 22:02:06 lab30 sh[351775]: at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
May 20 22:02:06 lab30 sh[351775]: at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:525)
May 20 22:02:06 lab30 sh[351775]: ... 1 more
May 20 22:02:06 lab30 systemd[1]: apacheds.service: Main process exited, code=exited, status=1/FAILURE
May 20 22:02:06 lab30 systemd[1]: apacheds.service: Failed with result 'exit-code'.
After that I've manually installed the full JRE with command: apt-get install default-jre and also manually exported the system-wide: JAVA_HOME=/usr/lib/jvm/default-java
But apacheds error stays the same and LDAP is not even starting. Nor any other idea so far didn't help resolved the apacheds starting problem and honestly speaking I don't know what to do next while this is all on original packages from built-in repositories and that should work right after installation out of the box and it's a bit suprising that we're having such issues nowadays on Debian 12.
Cheers, K.
Upvotes: 0
Views: 105