Disables PolllerBackend , however when trying to restart opennms jetty log troughs an exception "cannot bind to port 1099" basically webUI Una/vailable , to workaround move the folder /opt/opennms/jetty-webapps/opennms-remoting and restart opennms , spoke to RangerRick on IRC according to RangerRick: backend=null should be added
Environment
CentOS 5.5 x64 , Any Hardware
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Seth Leger August 19, 2013 at 11:13 AM
I added two system properties that will allow you to reconfigure the server and registry ports for the remote poller RMI to avoid conflicts. The properties can be configured inside opennms.properties. Here are the relevent lines which also show the default values:
Marking as fixed. commit dce97d258e1ff81fe6bb71ddef3ef9b1c98916f7
David Hustace February 9, 2011 at 5:07 PM
You can change the RMI IP address that OpenNMS RMI service binds. What we really need is a property to enable/disable the RMI service (should be disabled by default now that we have HTTP base Remoting)..
User would like to disable the poller backend usualy the motivation comes from the fact that port 1099 is already binded with other JAVA RMI Service , Performing : http://www.opennms.org/wiki/FAQ-Troubleshooting#Q:_OpenNMS_doesn.27t_startup_with_the_error_with_the_.22pollerBackEnd.22:_.22Port_already_in_use:_1099.22
Disables PolllerBackend , however when trying to restart opennms jetty log troughs an exception "cannot bind to port 1099" basically webUI Una/vailable , to workaround move the folder /opt/opennms/jetty-webapps/opennms-remoting and restart opennms , spoke to RangerRick on IRC according to RangerRick: backend=null should be added