Hi everyone,

I just tried to enable LDAP Authentication using the provided tutorial. It seems I made a few mistakes…

Acutually I’m receving the following HTTP Error as I’m using the new “applicationContext-spring-security.xml” file:

HTTP Error: 503

Problem accessing /opennms/index.jsp. Reason:

                Service_Unavailable

Powered by Jetty://

I have attached  you the file “output_with_new_file.log”. As you can see the Webserver isn’t starting.

When I’m using the “old” applicationContext-spring-security.xml file the Webserver is starting as you can see in the attached file “output_without_new_file.log”.

Therefore I guess my “applicationContext-spring-security.xml” file is a problem.

I attached you my “applicationContext-spring-security.xml” file (ldap.xml), maybe you could tell me if I have some errors in this file ?

Thanking you in anticipation

Alex

Alex,

I suspect the problem is your contextSource. You don’t need the <beans:property base=”…” /> entry.

You can adjust the logging level for JETTY, WEB and WEBAUTH in your log4j.properties to analyze where problems exist too.

Ron

Hi everyone,

I just tried to enable LDAP Authentication using the provided tutorial. It seems I made a few mistakes…

Acutually I’m receving the following HTTP Error as I’m using the new “applicationContext-spring-security.xml” file:

HTTP Error: 503

Problem accessing /opennms/index.jsp. Reason:

                Service_Unavailable

Powered by Jetty://

I have attached  you the file “output_with_new_file.log”. As you can see the Webserver isn’t starting.

When I’m using the “old” applicationContext-spring-security.xml file the Webserver is starting as you can see in the attached file “output_without_new_file.log”.

Therefore I guess my “applicationContext-spring-security.xml” file is a problem.

I attached you my “applicationContext-spring-security.xml” file (ldap.xml), maybe you could tell me if I have some errors in this file ?

Thanking you in anticipation

Alex

Hi Ron,

thanks fort he answer! I deleted the ybeans:property base=””/> entry from the applicationContext-spring-security.xml.

I set the logging level for JETTY, WEB, Spring and WEBAUTH to DEBUG and started opennms  first without my edited applicationContext-spring-security.xml file and then with my edited file. I compared the logs and found an error in the jetty log:

2011-10-05 07:27:50,114 ERROR [Main] log: Failed startup of context org.mortbay.jetty.webapp.WebAppContext <at> 1e33378{/opennms,/opt/opennms/jetty-webapps/opennms}

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

Also i found an error in the spring.log :

2011-10-05 07:27:50,111 ERROR [Main] ContextLoader: Context initialization failed

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

But I don’t get it right…. I didn’t edit Line 1 in the applicationContext-spring-security.xml file… therefore the error should also occur when using the normal applicationContext-spring-security.xml file.

I’m not quite sure what to do now.

Thank you in advance

Alex

Alex,

I suspect the problem is your contextSource. You don’t need the <beans:property base=”…” /> entry.

You can adjust the logging level for JETTY, WEB and WEBAUTH in your log4j.properties to analyze where problems exist too.

Ron

Hi everyone,

I just tried to enable LDAP Authentication using the provided tutorial. It seems I made a few mistakes…

Acutually I’m receving the following HTTP Error as I’m using the new “applicationContext-spring-security.xml” file:

HTTP Error: 503

Problem accessing /opennms/index.jsp. Reason:

                Service_Unavailable

Powered by Jetty://

I have attached  you the file “output_with_new_file.log”. As you can see the Webserver isn’t starting.

When I’m using the “old” applicationContext-spring-security.xml file the Webserver is starting as you can see in the attached file “output_without_new_file.log”.

Therefore I guess my “applicationContext-spring-security.xml” file is a problem.

I attached you my “applicationContext-spring-security.xml” file (ldap.xml), maybe you could tell me if I have some errors in this file ?

Thanking you in anticipation

Alex

This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you.

Hi everyone,

i corrected my applicationContext-spring-security.xml file. But now I’m receiving another jetty error. Maybe you could help me figure it out:

2011-10-05 11:00:33,170 DEBUG [Main] JettyServer: SPRING: thread.classLoader=java.net.FactoryURLClassLoader <at> 9ced8e

2011-10-05 11:00:33,224 DEBUG [Main] JettyServer: OpenNMS.JettyServer initializing.

2011-10-05 11:00:33,263 INFO  [Main] log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog

2011-10-05 11:00:33,265 WARN  [Main] JettyServer: adding context: /opennms -> /opt/opennms/jetty-webapps/opennms

2011-10-05 11:00:33,345 WARN  [Main] JettyServer: adding context: /opennms-remoting -> /opt/opennms/jetty-webapps/opennms-remoting

2011-10-05 11:00:33,345 WARN  [Main] JettyServer: adding context: / -> /opt/opennms/jetty-webapps/ROOT

2011-10-05 11:00:33,346 DEBUG [Main] JettyServer: OpenNMS.JettyServer initialization complete.

2011-10-05 11:00:33,347 DEBUG [Main] JettyServer: SPRING: context.classLoader= java.net.FactoryURLClassLoader <at> 9ced8e

2011-10-05 11:00:34,010 DEBUG [Main] JettyServer: OpenNMS.JettyServer starting.

2011-10-05 11:00:34,010 INFO  [Main] log: jetty-6.1.24

2011-10-05 11:00:44,453 ERROR [Main] log: Failed startup of context org.mortbay.jetty.webapp.WebAppContext <at> df3ac5{/opennms,/opt/opennms/jetty-webapps/opennms}

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ldapAuthProvider' defined in ServletContext resource [/WEB-INF/applicationContext-spring-security.xml]: Cannot resolve reference to bean 'ldapAuthoritiesPopulator' while setting constructor argument; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'ldapAuthoritiesPopulator' is defined

It’s clear to me that the error is the creation of the name “ldapAuthProvider”. But I don’t know whats wrong with it… heres a snippet of my applicationContext-spring-security.xml:

  <!-- LDAP Server -->

  <beans:bean id="contextSource" class="org.springframework.security.ldap.DefaultSpringSecurityContextSource">

    <beans:constructor-arg value="ldap server:389/dc=sO,dc=sC" />

    <beans:property name="userDn" value="cn=manager,dc=sO,dc=sC"/>

    <beans:property name="password" value="password"/>

  </beans:bean>

                        <!—define LDAP as Authentication Provider -->

                        <beans:bean id="ldapAuthProvider" class="org.springframework.security.providers.ldap.LdapAuthenticationProvider">

                                               <custom-authentication-provider />      <!-- this adds the ldap authentication method to the ProviderManager -->

                                               <beans:constructor-arg ref="ldapAuthenticator"/>

                                               <beans:constructor-arg ref="ldapAuthoritiesPopulator"/>

                        </beans:bean>

What did I do wrong ?

Thanks again

Alex

Hi Ron,

thanks fort he answer! I deleted the ybeans:property base=””/> entry from the applicationContext-spring-security.xml.

I set the logging level for JETTY, WEB, Spring and WEBAUTH to DEBUG and started opennms  first without my edited applicationContext-spring-security.xml file and then with my edited file. I compared the logs and found an error in the jetty log:

2011-10-05 07:27:50,114 ERROR [Main] log: Failed startup of context org.mortbay.jetty.webapp.WebAppContext <at> 1e33378{/opennms,/opt/opennms/jetty-webapps/opennms}

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

Also i found an error in the spring.log :

2011-10-05 07:27:50,111 ERROR [Main] ContextLoader: Context initialization failed

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

But I don’t get it right…. I didn’t edit Line 1 in the applicationContext-spring-security.xml file… therefore the error should also occur when using the normal applicationContext-spring-security.xml file.

I’m not quite sure what to do now.

Thank you in advance

Alex

Alex,

I suspect the problem is your contextSource. You don’t need the <beans:property base=”…” /> entry.

You can adjust the logging level for JETTY, WEB and WEBAUTH in your log4j.properties to analyze where problems exist too.

Ron

Hi everyone,

I just tried to enable LDAP Authentication using the provided tutorial. It seems I made a few mistakes…

Acutually I’m receving the following HTTP Error as I’m using the new “applicationContext-spring-security.xml” file:

HTTP Error: 503

Problem accessing /opennms/index.jsp. Reason:

                Service_Unavailable

Powered by Jetty://

I have attached  you the file “output_with_new_file.log”. As you can see the Webserver isn’t starting.

When I’m using the “old” applicationContext-spring-security.xml file the Webserver is starting as you can see in the attached file “output_without_new_file.log”.

Therefore I guess my “applicationContext-spring-security.xml” file is a problem.

I attached you my “applicationContext-spring-security.xml” file (ldap.xml), maybe you could tell me if I have some errors in this file ?

Thanking you in anticipation

Alex

This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you.

Alex,

The error is indicated quite clearly. There is no bean named ldapAuthoritiesPopulator defined inside applicationContext-spring-security.xml.

In the original xml file, you had a definition for UserGroupLdapAuthoritiesPopulator, yet apparently that is not so in your latest version of the file.

Ron

Hi everyone,

i corrected my applicationContext-spring-security.xml file. But now I’m receiving another jetty error. Maybe you could help me figure it out:

2011-10-05 11:00:33,170 DEBUG [Main] JettyServer: SPRING: thread.classLoader=java.net.FactoryURLClassLoader <at> 9ced8e

2011-10-05 11:00:33,224 DEBUG [Main] JettyServer: OpenNMS.JettyServer initializing.

2011-10-05 11:00:33,263 INFO  [Main] log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog

2011-10-05 11:00:33,265 WARN  [Main] JettyServer: adding context: /opennms -> /opt/opennms/jetty-webapps/opennms

2011-10-05 11:00:33,345 WARN  [Main] JettyServer: adding context: /opennms-remoting -> /opt/opennms/jetty-webapps/opennms-remoting

2011-10-05 11:00:33,345 WARN  [Main] JettyServer: adding context: / -> /opt/opennms/jetty-webapps/ROOT

2011-10-05 11:00:33,346 DEBUG [Main] JettyServer: OpenNMS.JettyServer initialization complete.

2011-10-05 11:00:33,347 DEBUG [Main] JettyServer: SPRING: context.classLoader= java.net.FactoryURLClassLoader <at> 9ced8e

2011-10-05 11:00:34,010 DEBUG [Main] JettyServer: OpenNMS.JettyServer starting.

2011-10-05 11:00:34,010 INFO  [Main] log: jetty-6.1.24

2011-10-05 11:00:44,453 ERROR [Main] log: Failed startup of context org.mortbay.jetty.webapp.WebAppContext <at> df3ac5{/opennms,/opt/opennms/jetty-webapps/opennms}

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ldapAuthProvider' defined in ServletContext resource [/WEB-INF/applicationContext-spring-security.xml]: Cannot resolve reference to bean 'ldapAuthoritiesPopulator' while setting constructor argument; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'ldapAuthoritiesPopulator' is defined

It’s clear to me that the error is the creation of the name “ldapAuthProvider”. But I don’t know whats wrong with it… heres a snippet of my applicationContext-spring-security.xml:

  <!-- LDAP Server -->

  <beans:bean id="contextSource" class="org.springframework.security.ldap.DefaultSpringSecurityContextSource">

    <beans:constructor-arg value="ldap server:389/dc=sO,dc=sC" />

    <beans:property name="userDn" value="cn=manager,dc=sO,dc=sC"/>

    <beans:property name="password" value="password"/>

  </beans:bean>

                        <!—define LDAP as Authentication Provider -->

                        <beans:bean id="ldapAuthProvider" class="org.springframework.security.providers.ldap.LdapAuthenticationProvider">

                                               <custom-authentication-provider />      <!-- this adds the ldap authentication method to the ProviderManager -->

                                               <beans:constructor-arg ref="ldapAuthenticator"/>

                                               <beans:constructor-arg ref="ldapAuthoritiesPopulator"/>

                        </beans:bean>

What did I do wrong ?

Thanks again

Alex

Hi Ron,

thanks fort he answer! I deleted the ybeans:property base=””/> entry from the applicationContext-spring-security.xml.

I set the logging level for JETTY, WEB, Spring and WEBAUTH to DEBUG and started opennms  first without my edited applicationContext-spring-security.xml file and then with my edited file. I compared the logs and found an error in the jetty log:

2011-10-05 07:27:50,114 ERROR [Main] log: Failed startup of context org.mortbay.jetty.webapp.WebAppContext <at> 1e33378{/opennms,/opt/opennms/jetty-webapps/opennms}

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

Also i found an error in the spring.log :

2011-10-05 07:27:50,111 ERROR [Main] ContextLoader: Context initialization failed

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

But I don’t get it right…. I didn’t edit Line 1 in the applicationContext-spring-security.xml file… therefore the error should also occur when using the normal applicationContext-spring-security.xml file.

I’m not quite sure what to do now.

Thank you in advance

Alex

Alex,

I suspect the problem is your contextSource. You don’t need the <beans:property base=”…” /> entry.

You can adjust the logging level for JETTY, WEB and WEBAUTH in your log4j.properties to analyze where problems exist too.

Ron

Hi everyone,

I just tried to enable LDAP Authentication using the provided tutorial. It seems I made a few mistakes…

Acutually I’m receving the following HTTP Error as I’m using the new “applicationContext-spring-security.xml” file:

HTTP Error: 503

Problem accessing /opennms/index.jsp. Reason:

                Service_Unavailable

Powered by Jetty://

I have attached  you the file “output_with_new_file.log”. As you can see the Webserver isn’t starting.

When I’m using the “old” applicationContext-spring-security.xml file the Webserver is starting as you can see in the attached file “output_without_new_file.log”.

Therefore I guess my “applicationContext-spring-security.xml” file is a problem.

I attached you my “applicationContext-spring-security.xml” file (ldap.xml), maybe you could tell me if I have some errors in this file ?

Thanking you in anticipation

Alex

This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you.

Hi Ron,

thanks for your reply. I was finally able to get LDAP Authentication running. First I had a few difficulties to understand the way the xml file work, but now I got it!

Thanks!

Alex

Alex,

The error is indicated quite clearly. There is no bean named ldapAuthoritiesPopulator defined inside applicationContext-spring-security.xml.

In the original xml file, you had a definition for UserGroupLdapAuthoritiesPopulator, yet apparently that is not so in your latest version of the file.

Ron

Hi everyone,

i corrected my applicationContext-spring-security.xml file. But now I’m receiving another jetty error. Maybe you could help me figure it out:

2011-10-05 11:00:33,170 DEBUG [Main] JettyServer: SPRING: thread.classLoader=java.net.FactoryURLClassLoader <at> 9ced8e

2011-10-05 11:00:33,224 DEBUG [Main] JettyServer: OpenNMS.JettyServer initializing.

2011-10-05 11:00:33,263 INFO  [Main] log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog

2011-10-05 11:00:33,265 WARN  [Main] JettyServer: adding context: /opennms -> /opt/opennms/jetty-webapps/opennms

2011-10-05 11:00:33,345 WARN  [Main] JettyServer: adding context: /opennms-remoting -> /opt/opennms/jetty-webapps/opennms-remoting

2011-10-05 11:00:33,345 WARN  [Main] JettyServer: adding context: / -> /opt/opennms/jetty-webapps/ROOT

2011-10-05 11:00:33,346 DEBUG [Main] JettyServer: OpenNMS.JettyServer initialization complete.

2011-10-05 11:00:33,347 DEBUG [Main] JettyServer: SPRING: context.classLoader= java.net.FactoryURLClassLoader <at> 9ced8e

2011-10-05 11:00:34,010 DEBUG [Main] JettyServer: OpenNMS.JettyServer starting.

2011-10-05 11:00:34,010 INFO  [Main] log: jetty-6.1.24

2011-10-05 11:00:44,453 ERROR [Main] log: Failed startup of context org.mortbay.jetty.webapp.WebAppContext <at> df3ac5{/opennms,/opt/opennms/jetty-webapps/opennms}

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ldapAuthProvider' defined in ServletContext resource [/WEB-INF/applicationContext-spring-security.xml]: Cannot resolve reference to bean 'ldapAuthoritiesPopulator' while setting constructor argument; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'ldapAuthoritiesPopulator' is defined

It’s clear to me that the error is the creation of the name “ldapAuthProvider”. But I don’t know whats wrong with it… heres a snippet of my applicationContext-spring-security.xml:

  <!-- LDAP Server -->

  <beans:bean id="contextSource" class="org.springframework.security.ldap.DefaultSpringSecurityContextSource">

    <beans:constructor-arg value="ldap server:389/dc=sO,dc=sC" />

    <beans:property name="userDn" value="cn=manager,dc=sO,dc=sC"/>

    <beans:property name="password" value="password"/>

  </beans:bean>

                        <!—define LDAP as Authentication Provider -->

                        <beans:bean id="ldapAuthProvider" class="org.springframework.security.providers.ldap.LdapAuthenticationProvider">

                                               <custom-authentication-provider />      <!-- this adds the ldap authentication method to the ProviderManager -->

                                               <beans:constructor-arg ref="ldapAuthenticator"/>

                                               <beans:constructor-arg ref="ldapAuthoritiesPopulator"/>

                        </beans:bean>

What did I do wrong ?

Thanks again

Alex

Hi Ron,

thanks fort he answer! I deleted the ybeans:property base=””/> entry from the applicationContext-spring-security.xml.

I set the logging level for JETTY, WEB, Spring and WEBAUTH to DEBUG and started opennms  first without my edited applicationContext-spring-security.xml file and then with my edited file. I compared the logs and found an error in the jetty log:

2011-10-05 07:27:50,114 ERROR [Main] log: Failed startup of context org.mortbay.jetty.webapp.WebAppContext <at> 1e33378{/opennms,/opt/opennms/jetty-webapps/opennms}

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

Also i found an error in the spring.log :

2011-10-05 07:27:50,111 ERROR [Main] ContextLoader: Context initialization failed

org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 1 in XML document from ServletContext resource [/WEB-INF/applicationContext-spring-security.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The processing instruction target matching "[xX][mM][lL]" is not allowed.

But I don’t get it right…. I didn’t edit Line 1 in the applicationContext-spring-security.xml file… therefore the error should also occur when using the normal applicationContext-spring-security.xml file.

I’m not quite sure what to do now.

Thank you in advance

Alex

Alex,

I suspect the problem is your contextSource. You don’t need the <beans:property base=”…” /> entry.

You can adjust the logging level for JETTY, WEB and WEBAUTH in your log4j.properties to analyze where problems exist too.

Ron

Hi everyone,

I just tried to enable LDAP Authentication using the provided tutorial. It seems I made a few mistakes…

Acutually I’m receving the following HTTP Error as I’m using the new “applicationContext-spring-security.xml” file:

HTTP Error: 503

Problem accessing /opennms/index.jsp. Reason:

                Service_Unavailable

Powered by Jetty://

I have attached  you the file “output_with_new_file.log”. As you can see the Webserver isn’t starting.

When I’m using the “old” applicationContext-spring-security.xml file the Webserver is starting as you can see in the attached file “output_without_new_file.log”.

Therefore I guess my “applicationContext-spring-security.xml” file is a problem.

I attached you my “applicationContext-spring-security.xml” file (ldap.xml), maybe you could tell me if I have some errors in this file ?

Thanking you in anticipation

Alex

This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you.

This e-mail message is being sent solely for use by the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by phone or reply by e-mail, delete the original message and destroy all copies. Thank you.

Hi everyone,

ldap auth is currently working correctly, but as I today stopped the opennms service and tried to restart it I receive the following error:

Starting OpenNMS: Started OpenNMS, but it stopped running: for details see /opt/opennms/logs/daemon/output.log

I took a look at the log file, but there seems to be nothing wrong:

Do 6. Okt 06:49:42 CEST 2011

begin ulimit settings:

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 32764

max locked memory       (kbytes, -l) 32

max memory size         (kbytes, -m) unlimited

open files                      (-n) 10240

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 8192

cpu time               (seconds, -t) unlimited

max user processes              (-u) 32764

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

end ulimit settings

Executing command: /opt/opennms/bin/runjava -r  -- -Djava.endorsed.dirs=/opt/opennms/lib/endorsed   -Dopennms.home=/opt/opennms -Dcom.sun.management.jmxremote.port=18980 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Xmx256m -Djava.net.preferIPv4Stack=true  -XX:MaxPermSize=128m -jar /opt/opennms/lib/opennms_bootstrap.jar  start 

Anyone got an idea whats wrong?

Greetings

Alex

Again hi everyone,

I can’t describe what happened…but i just tried the command again ( well i tried now over 20 times…) and opennms starts….

Greets

Alex

Hi everyone,

ldap auth is currently working correctly, but as I today stopped the opennms service and tried to restart it I receive the following error:

Starting OpenNMS: Started OpenNMS, but it stopped running: for details see /opt/opennms/logs/daemon/output.log

I took a look at the log file, but there seems to be nothing wrong:

Do 6. Okt 06:49:42 CEST 2011

begin ulimit settings:

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 32764

max locked memory       (kbytes, -l) 32

max memory size         (kbytes, -m) unlimited

open files                      (-n) 10240

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 8192

cpu time               (seconds, -t) unlimited

max user processes              (-u) 32764

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

end ulimit settings

Executing command: /opt/opennms/bin/runjava -r  -- -Djava.endorsed.dirs=/opt/opennms/lib/endorsed   -Dopennms.home=/opt/opennms -Dcom.sun.management.jmxremote.port=18980 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Xmx256m -Djava.net.preferIPv4Stack=true  -XX:MaxPermSize=128m -jar /opt/opennms/lib/opennms_bootstrap.jar  start 

Anyone got an idea whats wrong?

Greetings

Alex