Hi !

I would really like your feedback and help on this matter.

I have installed OpenStack TenantView ZenPack and I am trying it to connect it with my OpenStack deployment.

Therefore on the "Devices" I select "OpenStack EndPoint (User)" and I put the same credentials I use to login to my dashboard for the Username and Password fields.

At the "AuthURL" field I am putting something of the form http://8.43.86.2:5000/v2.0

I leave empty the "ProjectID" and the "RegionName" fields.

Afterwards I press ADD and the JOB is added.

Unfortunately I am seeing the following error at the job log:

2016-11-18 09:17:59,414 INFO zen.Job: Job 5fc3341e-8886-4821-9467-c6d4f754dc44 (Products.ZenModel.ZDeviceLoader.DeviceCreationJob) received

2016-11-18 09:17:59,651 INFO zen.Job: Beginning job Add Device Products.ZenModel.ZDeviceLoader.DeviceCreationJob

2016-11-18 09:18:06,401 INFO zen.Job: Running Job Add Device Products.ZenModel.ZDeviceLoader.DeviceCreationJob

2016-11-18 09:18:06,401 INFO zen.Job: Spawning subprocess: /opt/zenoss/bin/zendisc run --now -d 8.43.86.2 --monitor localhost --deviceclass /Devices/OpenStack/User --prod_state 1000 --job 5fc3341e-8886-4821-9467-c6d4f754dc44

2016-11-18 09:18:21,426 INFO zen.ZenDisc: Connecting to localhost:8789

2016-11-18 09:18:21,434 INFO zen.ZenDisc: Connected to ZenHub

2016-11-18 09:18:21,636 INFO zen.ZenDisc: Looking for 8.43.86.2

2016-11-18 09:18:29,348 INFO zen.ZenDisc: Result: Discovered device 8.43.86.2.

2016-11-18 09:18:29,379 INFO zen.ZenDisc: skipping WMI-based collection, PySamba zenpack not installed

2016-11-18 09:18:29,732 INFO zen.ZenDisc: Python collection device 8.43.86.2

2016-11-18 09:18:29,732 INFO zen.ZenDisc: plugins: zenoss.OpenStack

2016-11-18 09:18:29,897 INFO zen.OpenStack: Requesting flavors

2016-11-18 09:18:30,478 ERROR zen.ZenDisc: Unable to fill collection slots: [Failure instance: Traceback (failure with no frames): <class 'novaclient.exceptions.AuthorizationFailure'>:

]

2016-11-18 09:21:29,608 WARNING zen.ZenDisc: Client 8.43.86.2 timeout

2016-11-18 09:21:29,609 INFO zen.ZenDisc: Scan time: 180.26 seconds

2016-11-18 09:21:29,621 INFO zen.ZenDisc: Daemon ZenDisc shutting down

2016-11-18 09:21:30,948 INFO zen.Job: Job 5fc3341e-8886-4821-9467-c6d4f754dc44 Finished with result 0

2016-11-18 09:21:30,951 INFO zen.Job: Job 5fc3341e-8886-4821-9467-c6d4f754dc44 finished with result 0

Looking forward for your help!!!

Thanks in  advance :)

#Avamar MIB Transform mib = re.search("snmp trap 1.3.6.1.4.1.15597.1.1.1.1.1", evt.summary) if mib: #Break down MIB to select only relevant portions for alerts time = getattr(evt,'1.3.6.1.4.1.15597.1.1.1.2.2') #Time of event classification = getattr(evt,'1.3.6.1.4.1.15597.1.1.1.2.3') #Class of event message = getattr(evt,'1.3.6.1.4.1.15597.1.1.1.2.5') #Message of event severity = getattr(evt,'1.3.6.1.4.1.15597.1.1.1.2.1') #Avamar error event number component = getattr(evt,'1.3.6.1.4.1.15597.1.1.1.2.4') #Component of event critical = [1,4602,22310,22629,22704,22716,30974,50001,50005,50006,50007,50011,50012,50014,50015,50034,50194] #Critical Alert Numbers error = [4603,22354,30010,30900,30901,30929,30931,30951,30958,30960,30968,30998,30999] #Error Alert Numbers warning = [4004,4202,4302,4700,4710,4720,4730,4740,4750,4760,4770,4773,4776,4779,4783,4789,22408,22409,22415, 22416,22605,22609,22614,22630,22631,22632,22635,22644,22646,22801,30975] #Warning Alert Numbers information = [54,56,4200,4201,4300,4301,4600,4601,21005,21006,21010,22207,22208,22209,22210,22211,22212,22213, 22214,22215,22216,22217,22218,22219,22220,22221,22237,22243,22301,22305,22308,22309,22312,22315, 22316,22317,22318,22319,22320,22321,22322,22323,22324,22325,22326,22327,22328,22329,22330,22331, 22332,22333,22334,22335,22336,22337,22338,22339,22340,22341,22342,22343,22344,22345,22346,22347, 22348,22349,22351,22352,22353,22355,22371,22372,22373,22382,22405,22406,22441,22512,22513,22519, 22520,22523,22527,22529,22533,22534,22535,22553,22555,22556,22608,22610,22612,22615,22624,22626, 22637,22639,22641,22800,22802,22803,22901,22902,22903,22916,22918,23025,23100,23101,23102,23103, 23104,23105,23106,23107,24002,24004,24005,24008,24010,30934,30935,30936,30937,30938,30939,30952, 30953,30954,30955,30956,30957,30967,30969,31015,31019,31072,31073,31074,31076,31078,31081,31082, 31084,31085,31087,31089,31090,31092,31093,31095,50193,50195,55000,55002,55004,55006,55010,55012, 55014,55016,55018,55020] #Information Alert Numbers if severity in critical: newSeverity = 5 #Set Zenoss Critical elif severity in error: newSeverity = 4 #Set Zenoss Error elif severity in warning: newSeverity = 3 #Set Zenoss Warning elif severity in information: newSeverity = 2 #Set Zenoss Informational evt.summary = "Avamar Alert" #Set summary to a readable conversion evt.message = time+''+message #Set message as the correct OID from trap evt.severity = newSeverity #Set severity to match source evt.component = component+''+classification #Set type as component

Hello everyone,

Our team conducted routine maintenance on our servers and we noticed that Zenoss never sent a notification when a specific server was down once we would reboot. We intentionally shut some servers down and have the same issue. I've used the ping and snmpwalk commands, which fail of course, but the device status is still listed as UP. There was another post in the community where someone had a similar issue and seemed to have been able to find the fix (http://www.zenoss.org/forum/4231). It states that the issue may have something to do with an IP address being changed which could have broken something within RabbitMQ. A link to a solution was posted ( http://community.zenoss.org/message/71139#71139 ), but the page is no longer available.

If someone could help me pinpoint this issue I'd appreciate it greatly.

Thanks

Hello,

unfortunately our Zenoss server is broken and i needed to set up a new one. Installed the latest Zenoss Core version according to the documentartion and everything looks good so far. When trying to restore the latest backup after some time i get the error message

"facade: service name already exists under parent"

and restore will abort. The problem is that we are now "blind" because we don't have any monitoring for our network which drives me crazy. Can someone perhaps can explain how to successfull restore all my data?

Any help is highly appreciated!

Thank you in advance,

Martin

Hello all,

Do you have any idea/suggestion how to replace the functionality from the current monitoring tool ( Maximum percentage of disk growth = 25% ) in Zenoss?

I've created a new threshold,  a predictive threshold,  using DataPoint=FreeMegaBytes_FreeMegabytes, EventClass= /Capacity but I’m not sure if it is possible to define somehow Maximum Value= 25%.

Thank you !

Is there, in Zenoss, any option to monitor the  CPU parameters mentioned above? If so, cand you please let me know how?

I have seen only ProcessorTotalUserTime, ProcessorTotalProcessorTime  and ProcessorTotalPrivilegedTime in Zenoss.

Thank you !

I've been transitioning from a Zenosscore 4.2.3 to a new server installation of 4.2.5. Right now, they are both running simultaniosly, 4.2.5 using WinRM. I've noticed that the Windows boxes are missing services here and there on 4.2.5 with WinRM.

For example, 4.2.3 WMI monitoring of server A shows 143 Windows Services. 4.2.5 with WinRM shows the same server with 141 services. Each one of my servers is like this, missing 1...2 or more services while using WinRM. Is this a bug in the ZenPack (I'm using the latest one)?

Hi all,

Using Zenoss 4.2.x, here.

We had an issue when some of our metrics weren't collected anymore. This resulted in gaps where SNMP datasources were directly graphed

On graphs where calculated perfomance datasources were used to calculate sums or ratios, instead of having NaNs the datapoints stayed at their last values for more than an hour (time to restore metrics).

This can be misleading as we can't know if the calculated metrics were really collected or simply stuck at their last values.

Any1 ever experienced this ?

Thank you,

Hi,

I am try to model the openstack (Provider View) in Zenoss 5.1.9

I have installed the openstack (Provider View) Version 2.3.1 and Tenant Veiw 1.2.3

Able to register the openstack icehouse and mitaka But in the model device I am getting this error

2016-11-25 09:11:13,117 INFO zen.ZenModeler: Connecting to localhost:8789 2016-11-25 09:11:13,171 INFO zen.ZenModeler: Connected to the zenhub/0 instance

2016-11-25 09:11:13,331 INFO zen.ZenModeler: Collecting for device icehouse

2016-11-25 09:11:13,386 ERROR zen.ZenModeler: Unable to fill collection slots: [Failure instance: Traceback (failure with no frames): : : Traceback (most recent call last): File "/opt/zenoss/Products/ZenHub/PBDaemon.py",

line 101, in inner return callable(*args, **kw) File "/opt/zenoss/Products/ZenHub/services/ModelerService.py",

line 80, in remote_getDeviceConfig device = self.getPerformanceMonitor().findDeviceByIdExact(name) File "/opt/zenoss/Products/ZenModel/PerformanceConf.py",

line 217, in findDeviceByIdExact dev = self.dmd.Devices.findDeviceByIdExact(deviceName) File "/opt/zenoss/Products/ZenModel/DeviceClass.py",

line 556, in findDeviceByIdExact if dev.id == devicename: AttributeError: 'Endpoint' object has no attribute 'id' ]

2016-11-25 09:11:13,386 INFO zen.ZenModeler: Scan time: 0.05 seconds

2016-11-25 09:11:13,387 INFO zen.ZenModeler: Daemon ZenModeler shutting down

016-11-25 09:11:13,392 INFO zen.publisher: publishing failed: Connection was closed cleanly.

Any idea what is the missing attribute id ? Thanks

I have a fresh install of Zenoss Core 5. Zensyslog is running on localhost according to the control centre and ps output:

root      8389  1.1  0.1 942240 23284 ?        Ssl  Nov24  12:27 /serviced/serviced-controller bruo30tac5kqapz0i0fctanbz 0 su - zenoss -c "/opt/zenoss/bin/zensyslog run -c --logfileonly --monitor localhost "
root      8540  0.0  0.0  77856  1932 ?        S    Nov24   0:00 su - zenoss -c /opt/zenoss/bin/zensyslog run -c --logfileonly --monitor localhost 
1337      8559  0.2  0.7 571700 150292 ?       Ssl  Nov24   2:18 /opt/zenoss/bin/python /opt/zenoss/Products/ZenEvents/zensyslog.py --configfile /opt/zenoss/etc/zensyslog.conf -c --logfileonly --monitor localhost --useFileDescriptor=13

However, nothing is listening on port 514 to accept incoming syslog.

Tried to install the LinuxMonitor zenpack on 4.2.5 zenoss. It failed. Now I can't remove the zenpack. When I try to remove the zenpack I get:

 zenpack --remove ZenPacks.zenoss.LinuxMonitor-2.1.0.egg
ERROR:zen.ZenMessaging:Error encountered while processing ZenPacks.zenoss.LinuxMonitor
Traceback (most recent call last):
  File "/opt/zenoss/Products/ZenMessaging/queuemessaging/schema.py", line 58, in _getZenPackSchemas
    pkg_path = zpkg.load().__path__[0]
  File "/opt/zenoss/lib/python/pkg_resources.py", line 1954, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.LinuxMonitor-2.1.0.egg/ZenPacks/zenoss/LinuxMonitor/__init__.py", line 24, in <module>
ImportError: cannot import name schema
ERROR:zen.ZenossStartup:Error encountered while processing ZenPacks.zenoss.LinuxMonitor
Traceback (most recent call last):
  File "/opt/zenoss/Products/ZenossStartup/__init__.py", line 27, in <module>
    pkg_path = zpkg.load().__path__[0]
  File "/opt/zenoss/lib/python/pkg_resources.py", line 1954, in load
    entry = __import__(self.module_name, globals(),globals(), ['__name__'])
  File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.LinuxMonitor-2.1.0.egg/ZenPacks/zenoss/LinuxMonitor/__init__.py", line 13, in <module>
ImportError: cannot import name zenpacklib
ERROR:zen.ZenPackCmd:zenpack command failed
Traceback (most recent call last):
  File "/opt/zenoss/Products/ZenUtils/zenpack.py", line 487, in <module>
    zp.run()
  File "/opt/zenoss/Products/ZenUtils/zenpack.py", line 143, in run
    self.connect()
  File "/opt/zenoss/Products/ZenUtils/ZenScriptBase.py", line 52, in connect
    setDescriptors(self.dmd)
  File "/opt/zenoss/Products/ZenRelations/ZenPropertyManager.py", line 663, in setDescriptors
    module = __import__(zpkg.module_name, globals(), locals(), fromlist)
  File "/opt/zenoss/ZenPacks/ZenPacks.zenoss.LinuxMonitor-2.1.0.egg/ZenPacks/zenoss/LinuxMonitor/__init__.py", line 13, in <module>
ImportError: cannot import name zenpacklib

zenhub will not start. The error is:

2016-11-28 17:19:19,184 INFO zen.Relations: Ignoring unresolvable object '<persistent broken ZenPacks.zenoss.LinuxMonitor.ZenPack instance '\x00\x00\x00\x00\x00\x01\xd2

Any suggestions would be appreciated. Thanks.

Had asked this in a similar thread, but figured I'd start my own as it doesn't relate to modelling the device.

When one of my monitiored Windows servers is rebooted, just as it has finished starting up there is an error generated in Zenoss.

"HTTP Unauthorized received on initial kerberos request. Check username and password"

This only occurs when the servers are rebooted, and only once. I can continue to model, and monitor the server without problems. 

I've run a packet capture as per the ZenPack recommendations, however I'm not capturing/seeing any error

I have create an script run via zencommand that pings the hosts in a low bandwith mode, the script returns the proper data and it has been working properly for a lot of time, but recently it seems that there's a timeout blocking the results to appear in zenoss.

This is what I see in the logs when zencommand is in debug mode, specially the bold part:

2016-12-01 13:47:15,656 DEBUG zen.zencommand: Datasource: slowping Received exit code: 0 Output:
"OK"
2016-12-01 13:47:15,656 DEBUG zen.zencommand: Process slowping/slowping stopped (0), 1.46 seconds elapsed
2016-12-01 13:47:15,657 DEBUG zen.collector.scheduler: Task CT-040 300 Local changing state from FETCH_DATA to PARSING_DATA
2016-12-01 13:47:15,657 DEBUG zen.collector.scheduler: Task CT-040 300 Local changing state from PARSING_DATA to STORE_PERF_DATA
2016-12-01 13:47:15,658 DEBUG zen.RRDUtil: /opt/zenoss/perf/Devices/CT-040/slowping_Up.rrd: 2.0, @ N
2016-12-01 13:47:15,658 DEBUG zen.zencommand: allowduplicateclears dropping clear event {'manager': 'zenoss.bassols-energia.es', 'eventKey': 'Timeout', 'device_guid': '2b4b4a5d-9012-4301-a6
77-14b4a73f0220', 'device': 'CT-040', 'eventClass': '/Status/Ping', 'summary': 'Datasource slowping/slowping command timed out', 'component': '', 'monitor': 'localhost', 'agent': 'zencomman
d', 'severity': 0}
2016-12-01 13:47:15,658 DEBUG zen.zencommand: allowduplicateclears dropping clear event {'severity': 0, 'component': '', 'eventClass': '/Status/Ping', 'summary': 'El host a verificar \xc3\x
a9s 10.64.192.141 --  ara: 2016-12-01 13:47:14.313606', 'manager': 'zenoss.bassols-energia.es', 'eventKey': 'slowping', 'agent': 'zencommand', 'device': 'CT-040', 'message': "OK", 'device_guid': '2b4b4a5d-9012-4301-a677-14b4a73f0220', 'performanceData': [' Up=2'], 'monitor': 'localhost'}
2016-12-01 13:47:15,658 DEBUG zen.zencommand: Collection time for CT-040 was 1.466059 seconds; cycle interval is 300 seconds.
2016-12-01 13:47:15,658 DEBUG zen.collector.scheduler: Task CT-040 300 Local finished, result: [(<Products.ZenRRD.zencommand.Cmd instance at 0x970c5a8>, ParsedResults
  events: [{'component': '',
  'device': 'CT-040',
  'eventClass': '/Status/Ping',
  'eventKey': 'Timeout',
  'severity': 0,
  'summary': 'Datasource slowping/slowping command timed out'},
 {'component': '',
  'device': 'CT-040',
  'eventClass': '/Status/Ping',
  'eventKey': 'slowping',
  'message': "OK",
  'performanceData': [' Up=2'],
  'severity': 0,
  'summary': 'OK'}]
  values: [(({}, 'Up'), 2.0)]})]
2016-12-01 13:47:15,662 DEBUG zen.collector.scheduler: Task CT-040 300 Local changing state from STORE_PERF_DATA to IDLE

I am really lost on the cause that makes this Timeout appear, any ideas?

I have a new Zenoss core 5 installation which is rather generic, other than installing check_nrpe for remote checks.  

I am having a problem enabling ldap authentication.  I am following these steps:  

http://wiki.zenoss.org/Enabling_LDAP_Authentication_in_Zenoss_Core_5

I was able to install the required python modules without error.  After restarting zope and logging in to <host>/zport/manage, I am forced to authenticate again when I click 'roleManager' under acl_users.  Authentication fails, however the credentails have been verified. 

Also, when I select 'Import/Export' under acl_users, I receieve the page titled:  A Zenoss error has occured.  I have used all combinations available, using a numerical value for the export id.  Selecting to download a local or save a remote file, using XML or not, always generates an error. 

What is the best solution to backup loaded MIBs and create event class, event maps and event transforms?

Zenbackup script does it?

Thanks for answer!

Nfekete

We just got done installing Zenoss Core 5.1.10, I followed the steps of enabling LDAP that i found on the wiki but it does not seem to be working. When i log into zope and go to roleManager there is no LDAP plugin. How do i resolve this?

wiki http://wiki.zenoss.org/Enabling_LDAP_Authentication_in_Zenoss_Core_5#Install_the_required_packages_using_easy_install

Can you change the Deployment-ID name in Control Center? Im on Core v5.1.10

On Core 5.1.10 I am unable to access the Advaced > Control Center tab via the web UI. i get three banner errors

Unable to reach Elatic - log viewing may be impacted Refresh browser

HTTP Error 401: Unauthorized

Error fetching daemons list: Unauthorized.

capture.jpg

Hi folks, I have instaled zenoss 4.2.5, I load all devices and I have a lot of events, so, I want to delete all events ( move events to history) and the User interface doesn't work, then, I use a simple script ( python script that use zenoss api) and it doesn't work either. I tray to truncata the table event_summury using  myslq but I can't

Cannot truncate a table referenced in a foreign key constraint (`zenoss_zep`.`event_trigger_signal_spool`, CONSTRAINT `fk_event_summary_uuid` FOREIGN KEY (`event_summary_uuid`) REFERENCES `zenoss_zep`.`event_summary` (`uuid`))

Any idea what I can do?

Thanks you!

In the CPU Utilization report,

• What does this cell mean - Forecasted % Util Exhaustion