When I monitor a Linux server, I find a label "link" in the page of overview. But I don't know how to use it and what's meaning? In my plain understanding, I think that it mean the link is a relation between two servers. Does it really?
------
James
↧
About the label "link" of the device overview
↧
send systems with event commands
Hi!
I need some help.
We have an event command now that executes on some events that sends ${evt/evid} and ${dev/id} to a bash script. This works good, but now we need to also send the Systems that the host is connected to also, but I can't find out how to do this.
Can anybody help me with this?
↧
↧
Autodeploy script stops silently, without errors
I try to install Zenoss 4.2.3 using the core-autodeploy script on a Centos 6.4 x64 (virtual) machine.
The Centos installation is a "basic server" installed from full DVD with nothing done apart from removing mysql-libs which was present for some reason.
When I run the core-autodeploy script it stops silently, without an error or anything after the zenoss rpm is downloaded and the gpg key is imported.
Output:
[root@zenoss-test zenoss-core-autodeploy-3200e76]# ./core-autodeploy.sh
Ensuring Zenoss RPMs are not already present
Disabling SELinux...
Attempting to remove existing OpenJDK...
Downloading zenoss_core-4.2.3.el6.x86_64.rpm...
--2013-03-20 10:52:27-- http://downloads.sourceforge.net/project/zenoss/zenoss-4.2/zenoss-4.2.3/zenoss_core-4.2.3.el6.x86_64.rpm
Resolving downloads.sourceforge.net... 216.34.181.59
Connecting to downloads.sourceforge.net|216.34.181.59|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://ignum.dl.sourceforge.net/project/zenoss/zenoss-4.2/zenoss-4.2.3/zenoss_core-4.2.3.el6.x86_64.rpm [following]
--2013-03-20 10:52:27-- http://ignum.dl.sourceforge.net/project/zenoss/zenoss-4.2/zenoss-4.2.3/zenoss_core-4.2.3.el6.x86_64.rpm
Resolving ignum.dl.sourceforge.net... 62.109.128.11, 2001:1ab0:7e1f:1:230:48ff:fed1:9c0a
Connecting to ignum.dl.sourceforge.net|62.109.128.11|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 121641133 (116M) [application/octet-stream]
Saving to: âzenoss_core-4.2.3.el6.x86_64.rpmâ
100%[=========================================================================>] 121,641,133 1.98M/s in 2m 30s
2013-03-20 10:54:57 (793 KB/s) - âzenoss_core-4.2.3.el6.x86_64.rpmâ
Importing Zenoss GPG Key
[root@zenoss-test zenoss-core-autodeploy-3200e76]#
Does anyone have an idea?
↧
zenoss 4 32 bits appliance
Hi
how can I get an 32 bits zenoss appliance
I need it in version 4 because I work in ipv6
and thanks
↧
Zenoss reports: SNMP agent down (solved)
Hello,
I seem to be having a problem with Zenoss reporting that the SNMP agent is down on a couple of Cisco devices, I have searched this site for answers, but nothing I have found seems to resolve my issue.
As the "zenoss" user, if I run from the command line: 'zenperfsnmp run' I see an error like below:
<date> WARNING: zen.zenperfsnmp: hostx.domain.org SNMP agent down
But, if I run (again as "zenoss" user): 'zenperfsnmp run -d hostx.domain.org', it runs successfully.
Running Zenoss core (zenoss-3.1.0-1031.el5) on CentOS x86_64.
Thanks,
Mike
Update: The issue ended up being the following:
Two of the Cisco routers I had on the network had the same snmp engineID. I changed the engineID on one of the routers, the problem no longer occurs.
↧
↧
Missing critical disk usage thresholds in Zenoss 4
We are using Zenoss 2.5 in our production environment and Zenoss 4 in testing environment as possible replacement. One thing that I'm really missing in version 4 is critical disk usage thresholds, which are 95% by default in version 2. The great benefit of Zenoss in comparison with other monitoring solutions is that modeling process initializes reasonable defaults for all device components, so there is almost no need in customization after adding new device. With critical disk usage thresholds I was always sure that I won't miss any partition overuse. I understand that I can add them in existing filesystem templates, but I just wonder why they ain't there by default and if I'm missing some improvement here. Thanks.
↧
Is there a way to control snmpwalk command source IP?
I recently upgraded my Zenoss install to a high availability configuration and ran into a small issue. I have a few SNMP monitored devices that only let me enter in a single allowed host for my SNMP reads. Does anybody know if there is a way to make Zenoss originate its snmpwalk type commands from a specific ip if its on a multihomed machine? I'd like them to originate from the virtual ip.
↧
Command timeouts on device
Hellow,
I am using zenoss 3 and getting below email alerts.
Any one kindly advice me.
Command timed out on device Exch: '/usr/local/zenoss/zenoss/ZenPacks/ZenPacks.Nova.Windows.SNMPPerfMonitorSimple-1.6-py2.6.egg/ZenPacks/Nova/Windows/SNMPPerfMonitorSimple/libexec/winmem.sh "10.0.0.5" "Test"'
Regards,
Arshad
↧
Problems with "ZenPacks.ZenSystems.Juniper" - Code 126 for ipSecVPN extensions
Hi,
I'm using the virtual appliance of zenoss 3.2.1.
I got a problem in setting up the "Juniper ZenPack". I installed the ZenPack in the zenoss UI, then I added the device by chosing the "Network\Router\Firewall\Juniper" section. First I thought everthing is fine, some data is shown (Interfaces, IP services, Juniper Power Supply, Juniper Fan, File Systems).
But then the following three errors came up for the ipSecVPN extensions of the ZenPack.
Error 1:
Cmd: /opt/zenoss/ZenPacks/ZenPacks.ZenSystems.Juniper-1.2-py2.6.egg/ZenPacks/ZenSystems/Juniper/lib/ipSecVlanP1Count.sh 192.168.0.1 v2c public - Code: 126 - Msg: Command invoked cannot execute, permissions problem or command is not an executable
Error 2:
Cmd: /opt/zenoss/ZenPacks/ZenPacks.ZenSystems.Juniper-1.2-py2.6.egg/ZenPacks/ZenSystems/Juniper/lib/ipSecVlanP2Count.sh 192.168.0.1 v2c public - Code: 126 - Msg: Command invoked cannot execute, permissions problem or command is not an executable
Error 3:
Cmd: /opt/zenoss/ZenPacks/ZenPacks.ZenSystems.Juniper-1.2-py2.6.egg/ZenPacks/ZenSystems/Juniper/lib/ipSecSrcNatStatsTableCount.sh 192.168.0.1 v2c public - Code: 126 - Msg: Command invoked cannot execute, permissions problem or command is not an executable
When I execute the commands on the shell, there were no errors, the following output was shown:
Shell 1:
IPSec VPN Phase 1 table count - status OK | ipSecVPNP1Count=1
Shell 2:
IPSec VPN Phase 2 table count - status OK | ipSecVPNP2Count=4
Shell 3:
IPSec NAT table count - status OK | ipSecNATCount=1
I executed them as root and as zenoss user.
So has somebody an idea what could be the problem?
Thanks for your help
- mrjetter -
↧
↧
code and numbers instead of text
Hi everyone
I just installed Zenoss 4.2.3 on a clean CentOS 6.3 Linux
Everything worked fine, and I added some devices to my dev installation
Something strange I noticed
- If I add a device using its IP, zenoss stores it with ID as device name, and everytime I receive a mail of an event regarding this device, I see it's IP instead of name. I found on the forum the solution is to edit the device properties and using the rename command, change the device name from IP to something easier to read, and that works
- When an event is cleared, i read cleared by letters&numbers (something I think is an UUID). Using an older version of Zenoss, I haven't noticed this "problem" (for example if the event was "clearing" an high threshold of the device server1, in the field cleared by, I read "cleared by server1". In this new version of zenoss the same message appear as "cleared by '00505688-5fde-b25b-11e2-79681942bd6f'"
- The severity level in the event is displayed as 1 2 3 etc instead of critical, debug etc
I haven't noticed any error message installing Zenoss, but it seems there are problems converting codevalue to descriptive text
Is there something I can check/fix?
Thanks
↧
How configure "Model Device..." by remote collector?
hi, all
How configure "Model Device..." by remote collector?
I am working with zenoss in distributed environment in cloudstack.
My cloudstack network has two subnets , 192.168.1.x and 192.168.2.x .
The zenoss master in machine A with ip 192.168.1.2 ; and zenoss collector in machine B( two nics ) with 192.168.1.1 , another ip in machine B is 192.168.2.1 .
Now , I use distributed collector ZenPack to add zenoss collector to zenoss master , and I want use zenoss to monitor devices in 192.168.1.x subnet.
Such as , I want zenoss monitor one linux box with ip : 192.168.2.2 , so I add 192.168.2.2 to zenoss by assign REMOTE collector
After add that device , I change the device class to "/Server/Cmd" and I had configured the username/password properties.
When I click the menu : "Model Device ..." , I watch log files and find that : zenoss not use remote collector , but still use the localhost zenmodeler process !
That is not what expected in a distributed environment , because master (192.168.1.1) can not talk to the linux box (192.168.2.2).
How can do configure for zenoss master use remote collector instead of "localhost zenmodeler"?
Thanks in advance .
↧
Zenoss Community Newsletter
Hey all,
Next Month (April), we'll be starting a quarterly community newsletter. First and most important, we will be taking input/submissions from the community, and that actually starts now!
err...
ok fine now.
We're going to have an event schedule, articles on free and commercial zenpacks, and the folks that write them, tips and tricks but I want to know what else you're intrested in, and I'm providing some (non-mandatory totally optional) suggestions, and am interested in yours.
Thought leadership stuff you can show your boss
Notes from me on what I'm doing
roadmap/product direction information from our engineering folks in their mountain lair
howtos
So anyway, what do you want to know about what it is we're doing, what do we want to know about what you're doing?
↧
extdirect Direct request failed: severity: TemplateRouter.getThresholds
Hi,
I just upgraded to Zenoss 4.2.3, and I cannot add any threshold on my Linux Devices, I get "AttributeError: severity" in the WebUI, and this in the event.log file :
2013-03-25T15:32:35 INFO extdirect Direct request failed: severity: TemplateRouter.getThresholds [{'uid': '/zport/dmd/Devices/Server/SSH/Linux/rrdTemplates/Device'}]
------
2013-03-25T15:32:35 INFO extdirect DirectRouter suppressed the following exception (Response cee4b1bd-c9a3-40fd-abce-83b0a8aedc6b):
Traceback (most recent call last): File "/opt/zenoss/Products/ZenUtils/extdirect/router.py", line 179, in _processDirectRequest response.result = _targetfn(**data) File "/opt/zenoss/Products/Zuul/routers/template.py", line 165, in getThresholds return DirectResponse.succeed(data=Zuul.marshal(thresholds)) File "/opt/zenoss/Products/Zuul/__init__.py", line 128, in marshal marshalled_list.append(marshal(o, keys, marshallerName, objs)) File "/opt/zenoss/Products/Zuul/__init__.py", line 101, in marshal return marshal(marshaller.marshal(keys), File "/opt/zenoss/Products/Zuul/marshalling.py", line 76, in marshal data = _marshalImplicitly(self._obj) File "/opt/zenoss/Products/Zuul/marshalling.py", line 39, in _marshalImplicitly for key in getPublicProperties(obj): File "/opt/zenoss/Products/Zuul/marshalling.py", line 28, in getPublicProperties if not key.startswith('_') and not callable(getattr(obj, key)) File "/opt/zenoss/Products/Zuul/infos/template.py", line 517, in _getSeverity return self._object.severity
AttributeError: severity↧
↧
WMI Test in the "Commands" section
Maybe It has been discussed before and I just missed it, but is there anyway to add a WMI test command in the "Commands" bar on Zenoss? Simillar to the SNMPWalk command just so that I can test connectivity of the WMI features of Windows and Zenoss? I find it odd that there isn't an option already to do that.
Using Zenoss 4.2.3
↧
API for adding/managing maintenance windows
I'm writing a script to allow us to schedule maintenance windows from the command line instead of using the web gui. I have a working script that runs on the Zenoss server, but I would really like to be able to run the script on any system rather than give users access to log into to the server. However, it doesn't look like the functions to do this are exposed through either the REST or JSON APIs. Does anyone have a way to do this?
↧
Command ping failed by distributed collector
hi, all
I use zenoss in distributed environment , in which , zenoss master is ip 192.168.1.1 and zenoss collector ip is : 192.168.1.2.
Zenoss collector have two nics whith two ip : 192.168.1.2 and 10.1.1.1
I want zenoss monitor devices in network 10.1.1.x , such as one linux box with ip : 10.1.1.5
I install and configed zenoss collector successfully by Distributed ZenPack 2.0 .
After add 10.1.1.5 linux box to device list , I want "Ping" the linux box through "Command" menu at the left bottom panel .
The error list was: Can not ping to 10.1.1.5.
Why zenoss not use collector to ping 10.1.1.5 instead of by using itself?
Thanks in advance .
↧
OpenStack Zenpack cannot connect to OpenStack
Hi there,
I just installed the OpenStack ZenPack in Zenoss 4.2 (Zenpack 1.1.4). And I cannot make it work against Openstack. To be honest I am not sure how to populate the configuration parameters.
I am trying to make it work against a working installation of OpenStack Folsom.
So far I am taking values as the ones I have in novarc:
Username: admin
API Key: userpassword (I am using the user password as in novarc. I think the password should work as API Key in here).
Project ID: I tried blank, then I tried the hexadecimal ID, then I tried the name ("Default").
AuthURL: I have tried everything in here too. I tried keystone URL http://192.168.0.17:5000/v2.0 and I tried nova url http://192.168.0.17:8774/v2/ProjectIDinHexadecimal
Region: I tried empty and with the Region name.
None of the above worked. I am getting 404, 401 or time outs errors whatever I do.
What are the expected values? I noticed in the AuthURL v1 appears in the samples. But is v2 of the protocol supported? I think folsom uses it by default.
I am quite desperated about it, not really know what else to try. The log errors in the zenoss job are not very verbose neither.
Kind regards.
↧
↧
Issues about the source ZenPacks
I downlaod the source ZenPacks form the link https://github.com/zenoss/ZenPacks.zenoss.OpenStack. And I see the document from the link http://community.zenoss.org/docs/DOC-3154. So my understanding is that I can install the ZenPack with the command "zenpack --link --install ZenPacks.zenoss.OpenStack". But at last, although there is no error messages, I can't see the ZenPack from the GUI. Can anyone tell me what' wrong?
thanks!!!
-----
James
↧
Can I create a user that can only create events?
Can I create a user that only has access to createEvents, but no UI access?
I want to create some code that our developers can use to send events, but I want to prevent them from using that username and password from getting too much access ot Zenoss administrative functions.
↧
Managing user roles in Zenoss
Hi guys,
we need to create a user role that alows certain users to change monitoring ( Production/Preproduction and so on ) but we also need to avoid this user to change other configuration.
Any idea?
I've found a beta ZenPack but unfortunately it doesnt work.
Thanks in advance for any suggestions
Simone
↧