I have an odd situation where I have 3 separate Zenoss installs which all originated from the same install and was then built via zenrestore.
My question is whether there is a way to have multiple websites as a device, but not have issues with having the same IPs. I have websites/vhosts being monitored via HttpMonitor (in 2 of my 3 installations) with that have the same IP, but I can't seem to find the different setting in the 3rd. The details... I'm using the HttpMonitor zenpack to monitor websites, and at one of my sites (only at 1 of the 3 am I not using using HttpMonitor to actively monitor our websites). On that server I wrote a script to log in to one of the servers in our webpool and parse logs to get the number of requests and average page load time for each vhost. I created a template for it and in my /WWW/$cluster_name class I also have the HttpMonitor template in this class. I have this working for one vhost, but I am not allowed to add another website/vhost within the same cluster because they all have the same IP. The odd thing is that I have all the vhosts (many with the same IP) in my other installs using HttpMonitor - yet I can't have multiple sites with the same IP in this other server. I am also setting my discovery protocol to "None" and adding it to the class I setup when adding the site. I noticed that when looking at the file in the Zenpacks, that there are different files in the Zenpack, yet I'm running the same Zenoss version (2.3.3) and Zenpack version (2.0.0). Files in Zenpack (non working install): Code: /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/__init__.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/migrate/ConvertHttpMonitorDataSources.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/migrate/BaseClass.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/migrate/__init__.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/datasources/__init__.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/datasources/HttpMonitorDataSource.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/skins/HttpMonitor/editHttpMonitorDataSource.pt Files in Zenpack (working install): Code: /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/__init__.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/skins/HttpMonitor/editHttpMonitorDataSource.pt /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/migrate/ConvertHttpMonitorDataSources.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/migrate/__init__.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/migrate/BaseClass.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/datasources/__init__.py /opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.0.0-py2.4.egg/ZenPacks/zenoss/HttpMonitor/datasources/HttpMonitorDataSource.py Thoughts? -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=35798#35798 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
