The difficulty with the core of OpenNMS is that these components need to run as root to be able to bind to low-numbered ports or generate network traffic that requires root: Here is an example of the error you will get if you try to startup OpenNMS as a non-root user: 2004-08-28 09:47:14,405 ERROR [main] Discovery: Failed to create ping manager: \ java.net.SocketException: System error creating ICMP socket (1, Operation not permitted)

There is none; all passwords are locked/scrambled by default; you set one yourself for those situations which call for it. You can set the root password by going to Knoppix Menu->Root Shell and typing "passwd", then entering a root password. In Version 5.0.1 you can also go to Knoppix Menu -> Configure -> Set password for root. There are several sections you can read dealing with this subject in KNOPPIX/README_Security.txt.

OpenNMS, the application, is the first enterprise-grade network management platform to be developed under the open-source model. The goal is for OpenNMS to be a truly distributed, scalable platform for all aspects of the FCAPS network management model, and to make this platform available to both open source and commercial applications. Data Collection - collecting, storing and reporting on network information as well as generating thresholds.

Let's assume that we want to send an alert when hrSystemProcesses exceeds 250. The numeric OID is .1.3.6.1.2.1.25.1.6 . In this case, said collection definition is listed in my "/opt/OpenNMS/etc/ datacollection-config.xml" file. So what we need to do firstly is edit: "/opt/OpenNMS/etc/thresholds.xml".

In the Debian packages of XFree86, some important variables affecting the startup of the X server are located in /etc/X11/Xwrapper.config. In this particular case, you must change the option allowed_users to either console or anybody. See Xwrapper.config(5) for more information and examples. First, a note on terminology: conffile is a Debian term for a configuration file that is shipped as part of a package's payload.

New versions of Linux (with the new threading model) can also use <user-name> , but using "/sbin/iptables" may be a better solution. The Linux iptables maps port 80 requests to port 8080. This way, your Resin instance can start up as a normal user and listen to port 8080 without needing to start as root.

The Root account is an internal change in the 2.2 code, introduced by the removal of the AccountGroup data structure. (Accounts are now their own grouping construct, but we still need a top-level "Root" account to take the place of the old top-level AccountGroup.) If you're planning on sticking with your 2.0 install for a while, then you can re-parent each child of the "Root" Account to be a top-level account, then remove the Root account.

The early versions of NcFTPd could run as "ftp" since the server did not support regular user logins (anonymous only). Current versions require that NcFTPd switch back and forth from root to user privileges, so it is not feasible to run except as root.

For a "normal" user to be able to use M11, it must be installed suid root. So, in the folder where M11 is installed enter (as root):

OpenNMS is mainly written in Java. The goal for OpenNMS 2.0 is to have a product that will install as a collection of .jar files. icmpd - The 1.4 Java API does not understand ICMP. Since ICMP echo requests ("pings") are the simplest way to test the responsiveness of an IP-based network device, no network management application will be complete without it. The goal is to separate the ICMP functions into their own daemon that OpenNMS will use if present and ignore if not.

Please note that we now keep up-to-date release notes on the web site and in the latest RPM packages, they may have information about installation on your particular distribution, or other last-minute things that went into the release. Before asking questions on the list, PLEASE check the release notes and this FAQ thoroughly for information pertaining to your issue.

We use SourceForge mailing lists. You can find links to subscribe as well as view archives on the web at our mailing lists page. Please note: when subscribing, remember the address you used, as you will need to send from that address or your post will be rejected. To unsubscribe, please do not send a message to the list or to the list administrator. Go to the list information page for the list you wish to leave, and enter in your e-mail address at the bottom and edit your options.

With OpenNMS 0.9, the concept of a "primary" SNMP interface was added to the database. By default the interface with the lowest IP address is designated as the primary interface for SNMP queries. Also by default, performance data is only collected for that interface. If you would like to collect data on all of the interfaces on the node, you need to make a change to the /opt/OpenNMS/etc/datacollection-config.

Then modify your notificationCommands.

First create a certificate keystore for tomcat by executing $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA Restart httpd, tomcat and opennms just to be sure and after what seemed too long, I was prompted for user name and password. It seems only the first time connecting is real slow, subsequent logins are quite speedy. I wanted to add a few comments to this. First, if you want to use a password other than "changeit", add the keystorePass attribute: <Connector className="org.apache.

OpenNMS already has configurations to use qpage (http://www.qpage.org). You can see them in $OPENNMS_HOME/etc/notificationCommands.xml. I set up users on onms, then setup the users (with the same name) in /etc/qpage.cf. That's pretty much all I had to do in onms. On the qpage side, you need to configure the pager-ids and the service. The key here is that the number used to send alpha pages is not the pager number but a different number talking something called TAP.

By default, net-snmp is configured only to allow a really small amount of information to be accessed by the default community name of "public". The easiest way to change this is to find a line like: view systemview included .1.3.6.1.2.1.1

You must setup the group and create the users. Also make sure that the pg_hba.conf file has the correct security permissions. And then just run psql interactively with these GRANTS for the group access.

In all other cases, such as running DenyHosts from cron then technically speaking, no. However, in order to run DenyHosts as non-root you must ensure that you have read-permissions on the /var/log/ sshd server logs. Alternatively, you can copy them to a directory where you do have read-permissions. Also, in order for DenyHosts to block hosts, it needs write permissions for the /etc/hosts.deny file. DenyHosts will gladly run without being able to update this file.