Zenoss install apache

Category : Articles. Navigation menu Personal tools Create account Log in. Namespaces Newsletter Discussion. Views Read View form View source View history. Navigation Main page Recent changes Random page. This page was last modified on 18 November , at Privacy policy About Zenoss Wiki Disclaimers. We always appreciate help in keeping the Zenoss FAQ and documentation in good shape.

If you would like to update something, please do. Want to share your thoughts about new features needed for Zenoss prosperity? Lets us know, send a note! Give us chance to fix it faster! You can find out about it here. No the minimum requirement is MySQL 5. We use a trigger to move events to the history database. MySQL 4 has no triggers and 5. For the first one, you need to find out what the name of your system's python dev package is and then install it.

This usually happens when you are reinstalling Zenoss and did not shutdown the ZEO instances from the previous installation. The solution is to either run. Before reinstalling Zenoss or re-attempting an install, be sure to run.

Doing so will avoid the issue encountered here. Zenoss uses a trigger to move create a historical archive of events. Near the top of the file add this line:. When the collectors start, they connect to ZenHub and request configuration information. This information is normally a list, but if an error occurs, the result will not be a list and the "iteration over non-sequence" error occurs. If you have just upgraded, the result is probably a result of a bad migration. Be sure to run zenmigrate after the code has been updated:.

If the problem persists, there has been a problem with the data migration. You may wish to revert to a backup before the upgrade, and try the migration again, or contact support about the problem.

The mib loader is called zenmib. Then run zenmib. They are not used when setting up the poller. This is something we will do in the future though.

RRDTemplates are bound to interfaces by the name of the interface type. The type of an interface can be seen in the detail screen of an interface.

Make sure that all oids listed are supported by your new interface! Event Mappings only apply to events with no eventClass. If your event has an eventClass when it comes in, mappings are not applied. If you need to be more specific, add the rule or regex i.

The eventClassKey is often the name of a process it's what is called the tag of a syslog message. If you want to process incoming events, where the eventClassKey is something that cannot be known or is blank, put "defaultmapping" into the 'Event Class Key' field of the mapping. The mapping will be used if no other 'Event Class Key' matchs and, of course, there is no eventClass on the event to begin with. You can make multiple event mappings that have the same 'Event Class Key', but different rules or regex.

You then need to put an order to these multiple mappings, in the sequence tab of the mapping. Make sure the that zopeusername and zopepassword are a valid username and password pair in your zope server and that the url is correct maybe your box name changed or zope is running on a different port? RRDTemplates are bound to objects by their name.

For a template to bind to a device it must be named "Device". Interfaces are different: they bind using the interface type as displayed on the interface detail screen. Check by seeing if you can retrieve the list of interfaces from a server:. Apache by default on most platforms listens on an a socket that supports both IPv4 and IPv6.

As a result we don't get it during an SNMP model of a device. This isn't true for portscan or SSH modeling.

To solve the problem you can force Apache to listen on an IPv4 socket only. In your configuration file set Listen to have a v4 address like this:. This article goes into more detail. It means that your web browser cannot fetch events from Zenoss. This is usually related to problems with MySQL. In an event list click on the right most event field the magnifying glass to see event details.

Within an event detail there are three tabs. Fields shows all the "standard" event fields. Details shows any extra fields that were added to the event. If the event is a trap the key value pairs from the event will be added here. The log tab list the things that have been done to the event, or user comments about the event. Zenoss gets route information for devices either from SNMP or making a direct connection to the device via telnet or ssh.

For more information about the output of the lsblk command, and about creating primary partitions, refer to the Zenoss Core Planning Guide. Replace Partition with the path of the target primary partition:. Replace Partition with the path of the primary partition used in the previous step:.

Creating a file system for backups To perform this procedure, you need a host with at least one unused primary partition, or a remote file server. The Control Center master host requires local or remote storage space for backups of Control Center data. This procedure includes steps to create an XFS file system on a primary partition, if necessary, and steps to mount a file system for backups.

For more information about primary partitions, refer to the Zenoss Core Planning Guide. Skip this step if you are using a remote file server. If the preceding commands return no result, perform the following substep. This step is required for installation but not for deployment. For more information, refer to the Zenoss Core Planning Guide. Proceed to the nextstep. Perform the following substep. By performing this step, log data persists and can be saved indefinitely, if you implement log file rotation practices.

For more information, refer to your operating system documentation. If the preceding commands return a result, SELinux is installed. The utility is used to verify ZooKeeper ensemble configurations. If you are installing a single-host deployment, skip this step. Currently, an unresolved issue associated with NTP prevents ntpd from restarting correctly after a reboot.

The following commands provide a workaround to ensure that it does. This procedure installs and configures Docker, and installs Control Center. Use insert key to change something and ESC key when ready e Save the file and close the text editor.

Type :wq to Write and Quit 3 Create a symbolic link for the Docker temporary directory. Docker uses its temporary directory to spool images. You can specify any directory that has a minimum of 10GB of unused space. Control Center includes a utility that simplifies the process of creating a device mapper thin pool.

In my case:. Replace Thin-Pool-Device with the name of the thin pool device created in the previous step I already did this for you :.

The initial startup takes up to a minute, and may fail. If the startup fails, repeat the previous command. Each time it starts, docker selects an IPv4 subnet for its virtual Ethernet bridge. The selection can change; this step ensures consistency.

Note Leave a blank space after the end of the thin pool device name, and make sure the double quote character " is at the end of the line. Currently, an unresolved issue prevents the NFS server from starting correctly.