headers
norcaldave | 1 Aug 2007 03:54
Favicon

Re: Problem with auto-discovery

Im using the VM appliance and when i run zendisc from prompt or auto discover from the web page it always
returns with 0 active IPS. I should be lots of discovered IP's.

------------------------
Dave Alfred

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9375#9375

-------------------- m2f --------------------
Permalink | Reply | 9 comments |
headers
Kevin Alexander | 1 Aug 2007 04:04

Repeated Critical alerts that a server is up

I have installed Zenoss 2.0.3 VMware appliance on a workstation that is part of a small Windows network.  There are four servers that have Windows Server 2003 installed; one of them is in a DMZ and not in the main network (SERVER_05).  I keep getting critical alerts that this server is “up”.  If I remove SERVER_05 from Zenoss I get critical alerts that one of the other servers is “up”.  I get a corresponding message that clears the alert that the server is “up”, but I never get an alert that a server is down.  Here is an example of the alert message.

 

 

Device: SERVER_05
Component:
Severity: Critical
Time: 2007/07/31 21:17:25.000
Message:
SERVER_05 ip 192.168.1.5 is up
Event Detail
Acknowledge
Delete
Device Events

 

 

 

Thanks for any advice that you have.

 

 

Kevin Alexander

kalexander <at> datacoreeng.com

_______________________________________________
zenoss-users mailing list
zenoss-users <at> zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users
Permalink | Reply | 0 comments |
headers
paulkoan | 1 Aug 2007 05:28

Cumulative interface counters

Hello,

I have zenoss 2.0.3 installed on a gentoo server, and it is currently monitoring various other devices,
including another server.

The interface counters in the OS graphs for the server provide me with the average usage per second over
various time periods.

What I would like is to see the cumulative byte counts through the interfaces (assuming that snmp
connectivity is not lost to the server).  Preferably maintaining a count even if the monitored server is
rebooted.  I would also like to be able to reset the counters in zenoss periodically.

I would also like the moon on a stick :)

Is this possible with Zenoss somehow?  If so, could someone point me to the right part of the documentation - I
am new to zenoss and cannot figure it out.

Many thanks,

Paul

------------------------
Paul

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9383#9383

-------------------- m2f --------------------
Permalink | Reply | 1 comment |
headers
jcims | 1 Aug 2007 05:35
Picon
Favicon

Re: Problem with auto-discovery


dschrock wrote:
> zendisc does not work in 2.0.3.  It appears to ping the network, but that is about it.

It looks like they broke it when moving away from a 'sudo' requirement.  There is a 'zensocket' setuid binary
that appears to open a socket and then drop privs to zenoss user.

dschrock wrote:
> Never run these apps as root.

Good advice, but the docs for 1.x say you must run zendisc as root in order to open the icmp socket.  I think
zensocket is the way they get around that in 2.x.  

I did some traces, no icmp packets are generated by zendisc, so it's probably a permissions issue... 
Meanwhile i'm going to look at building the zenoss xml file format manually and import the nodes.

------------------------
J Cims

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9384#9384

-------------------- m2f --------------------
Permalink | Reply | 8 comments |
headers
redone | 1 Aug 2007 06:08

Modeling problem

I'm hitting what looks like possibly a python path problem when I attempt to model a system:

[Failure instance: Traceback (failure with no frames): exceptions.AttributeError: 'AgentProxy'
object has no attribute 'walk' ]

Any one have any info on what it is, and how to get past it?

Thanks!

------------------------
Mark Morgan

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9385#9385

-------------------- m2f --------------------
Permalink | Reply | 6 comments |
headers
anouar | 1 Aug 2007 11:31
Picon
Favicon

a simple question please?

hi everybody, i'm a newer user of zenoss, i want monitoring a huge network of 150 servers and lot of actif
element (routeurs, switchs).
Is zenoss able to monitor and display a good and visible map?
can i install zenoss on a debian?
thanks in advance

------------------------
ben mansour anouar

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9389#9389

-------------------- m2f --------------------
Permalink | Reply | 1 comment |
headers
Barry Stephen (YDD08) Derwent Shared Services | 1 Aug 2007 11:59
Picon

RE: Re: lots of up/cleared reports

Marcel, I am having the same problem, I am also using the vmware
appliance running 2.0.3, sorry I don't know why this is happening.

I have not seen this strange behavior before on previous vmware images.
I think there must be something wrong with the vmware image.
I don't understand why I am constantly getting a severity 5 event saying
the device is up which is then cleared by a severity 0 event that says
the exact same thing. This is affecting multiple devices that I know are
responding to ping perfectly.

The only thing I see in the event log for zenping is that it says the
device network is not in the topology, but I can see the subnet in
Networks:
2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'DCDOM01' network
'172.26.20.0/24' not in topology

Very frustrating - is anyone else experiencing the same problems with
the 2.0.3 vmware image?

Can anyone from development investigate, I can provide whatever info is
required?

Thanks
Steve

This is my zenping log:
2007-07-30 17:58:05 INFO zen.ZenPing: building pingtree from
localhost.localdomain 2007-07-30 17:58:05 WARNING zen.ZenStatus: device
'DCDOM01' network '172.26.20.0/24' not in topology 2007-07-30 17:58:05
WARNING zen.ZenStatus: device 'DCCLA01' network '172.26.10.0/24' not in
topology 2007-07-30 17:58:05 WARNING zen.ZenStatus: device 'DCCLA02'
network '172.26.10.0/24' not in topology 2007-07-30 17:58:05 WARNING
zen.ZenStatus: device 'dcswc01.xdss.blah.uk'
network '172.26.9.0/24' not in topology
2007-07-30 17:58:05 WARNING zen.ZenStatus: device 'DCDOM02' network
'172.26.20.0/24' not in topology 2007-07-30 17:58:05 WARNING
zen.ZenStatus: device 'fw-dss-ns5-vc.n3.xdss.blah.uk' network
'10.197.169.0/26' not in topology 2007-07-30 17:58:45 INFO zen.ZenPing:
Finished pinging 9 jobs in 0.02 seconds 2007-07-30 17:59:45 INFO
zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds 2007-07-30 18:00:45
INFO zen.ZenPing: Finished pinging 7 jobs in 0.02 seconds 2007-07-30
18:01:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds
2007-07-30 18:02:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02
seconds 2007-07-30 18:03:45 INFO zen.ZenPing: Finished pinging 10 jobs
in 0.03 seconds 2007-07-30 18:04:45 INFO zen.ZenPing: Finished pinging 8
jobs in 0.02 seconds 2007-07-30 18:05:45 INFO zen.ZenPing: Finished
pinging 9 jobs in 0.02 seconds 2007-07-30 18:06:45 INFO zen.ZenPing:
Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:07:45 INFO
zen.ZenPing: Finished pinging 10 jobs in 0.03 seconds 2007-07-30
18:08:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds
2007-07-30 18:09:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03
seconds 2007-07-30 18:10:45 INFO zen.ZenPing: Finished pinging 10 jobs
in 0.02 seconds 2007-07-30 18:11:45 INFO zen.ZenPing: Finished pinging
10 jobs in 0.02 seconds 2007-07-30 18:12:45 INFO zen.ZenPing: Finished
pinging 9 jobs in 0.03 seconds 2007-07-30 18:13:45 INFO zen.ZenPing:
Finished pinging 9 jobs in 0.03 seconds 2007-07-30 18:14:45 INFO
zen.ZenPing: Finished pinging 8 jobs in 0.03 seconds 2007-07-30 18:15:45
INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30
18:16:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03 seconds
2007-07-30 18:17:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02
seconds 2007-07-30 18:18:05 INFO zen.ZenPing: building pingtree from
localhost.localdomain 2007-07-30 18:18:05 WARNING zen.ZenStatus: device
'DCDOM01' network '172.26.20.0/24' not in topology 2007-07-30 18:18:05
WARNING zen.ZenStatus: device 'DCCLA01' network '172.26.10.0/24' not in
topology 2007-07-30 18:18:05 WARNING zen.ZenStatus: device 'DCCLA02'
network '172.26.10.0/24' not in topology 2007-07-30 18:18:05 WARNING
zen.ZenStatus: device 'dcswc01.xdss.blah.uk'
network '172.26.9.0/24' not in topology
2007-07-30 18:18:05 WARNING zen.ZenStatus: device 'DCDOM02' network
'172.26.20.0/24' not in topology 2007-07-30 18:18:05 WARNING
zen.ZenStatus: device 'fw-dss-ns5-vc.n3.xdss.blah.uk' network
'10.197.169.0/26' not in topology 2007-07-30 18:18:45 INFO zen.ZenPing:
Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:19:45 INFO
zen.ZenPing: Finished pinging 10 jobs in 0.03 seconds 2007-07-30
18:20:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds
2007-07-30 18:21:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03
seconds 2007-07-30 18:22:45 INFO zen.ZenPing: Finished pinging 7 jobs in
0.02 seconds 2007-07-30 18:23:45 INFO zen.ZenPing: Finished pinging 9
jobs in 0.02 seconds 2007-07-30 18:24:45 INFO zen.ZenPing: Finished
pinging 7 jobs in 0.03 seconds 2007-07-30 18:25:45 INFO zen.ZenPing:
Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:26:45 INFO
zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:27:45
INFO zen.ZenPing: Finished pinging 7 jobs in 0.02 seconds 2007-07-30
18:28:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds
2007-07-30 18:29:45 INFO zen.ZenPing: Finished pinging 9 jobs in 0.03
seconds 2007-07-30 18:30:45 INFO zen.ZenPing: Finished pinging 9 jobs in
0.02 seconds 2007-07-30 18:31:45 INFO zen.ZenPing: Finished pinging 9
jobs in 0.02 seconds 2007-07-30 18:32:45 WARNING zen.ZenPing: DCCLA01 ip
172.26.10.3 is up 2007-07-30 18:32:45 INFO zen.ZenPing: Finished pinging
10 jobs in 0.04 seconds 2007-07-30 18:33:45 INFO zen.ZenPing: Finished
pinging 8 jobs in 0.03 seconds 2007-07-30 18:34:45 INFO zen.ZenPing:
Finished pinging 8 jobs in 0.02 seconds 2007-07-30 18:35:45 WARNING
zen.ZenPing: DCDOM01 ip 172.26.20.1 is up 2007-07-30 18:35:45 INFO
zen.ZenPing: Finished pinging 9 jobs in 0.02 seconds 2007-07-30 18:36:45
WARNING zen.ZenPing: DCDOM01 ip 172.26.20.1 is up 2007-07-30 18:36:45
INFO zen.ZenPing: Finished pinging 8 jobs in 0.02 seconds 2007-07-30
18:37:45 WARNING zen.ZenPing: DCDOM01 ip 172.26.20.1 is up 2007-07-30
18:37:45 INFO zen.ZenPing: Finished pinging 8 jobs in 0.03 seconds
2007-07-30 18:38:05 INFO zen.ZenPing: building pingtree from
localhost.localdomain 2007-07-30 18:38:05 WARNING zen.ZenStatus: device
'DCDOM01' network '172.26.20.0/24' not in topology 2007-07-30 18:38:05
WARNING zen.ZenStatus: device 'DCCLA01' network '172.26.10.0/24' not in
topology 2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'DCCLA02'
network '172.26.10.0/24' not in topology 2007-07-30 18:38:05 WARNING
zen.ZenStatus: device 'dcswc01.xdss.blah.uk'
network '172.26.9.0/24' not in topology
2007-07-30 18:38:05 WARNING zen.ZenStatus: device 'DCDOM02' network
'172.26.20.0/24' not in topology 2007-07-30 18:38:05 WARNING
zen.ZenStatus: device 'fw-dss-ns5-vc.n3.xdss.blah.uk' network
'10.197.169.0/26' not in topology

-----Original Message-----
From: zenoss-users-bounces <at> zenoss.org
[mailto:zenoss-users-bounces <at> zenoss.org] On Behalf Of Mars
Sent: 31 July 2007 11:55
To: zenoss-users <at> zenoss.org
Subject: [zenoss-users] Re: lots of up/cleared reports

No one?
So everybody is getting perfect reports (without lots of ip is up
messages)?
It surely must be something very simple but I can't find it.
I've now turned off Zenoss because all the mail I'm getting from Zenoss.

------------------------
 Marcel Engels

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9339#9339

-------------------- m2f --------------------

_______________________________________________
zenoss-users mailing list
zenoss-users <at> zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users

DISCLAIMER - This email and any file transmitted with it are confidential and intended solely for the use of
the individual or entity to whom they are addressed.  Any views or opinions expressed are those of the
author and do not represent the views of Derwent Shared Services, unless otherwise explicitly stated.
The information contained in this email may be subject to public disclosure under the Freedom of
Information Act 2000. Unless the information is legally exempt from disclosure, the confidentiality of
this email cannot be guaranteed.

Derwent Shared Services is an NHS Shared Services Organisation.
Permalink | Reply | 0 comments |
headers
F350 | 1 Aug 2007 15:32
Picon

Re: a simple question please?

Hi,

You can install Zenoss on Debian. Here is a small guide: http://www.zenoss.com/community/docs/howtos/installing-zenoss-on-debian-sarge/
Sadly there is no network mapping in Zenoss, i'm waiting for this feature. Is this already in the roadmap ?

regards

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9392#9392

-------------------- m2f --------------------
Permalink | Reply | 0 comments |
headers
jcims | 1 Aug 2007 15:36
Picon
Favicon

Re: AttributeError: 'module' object has no attribute disassemble


pmcfadin wrote:
> 
> AttributeError: 'module' object has no attribute 'disassemble'
> 

Are you using the vmware image or a standalone install?  There is another thread here about zendisc not
working.  After some troubleshooting i found a similar error that is logged from Ping.py in the sendPacket method

10.1.1.10 sendto error Packet instance has no attribute 'assemble'

i wonder if the version of python is wrong.  strace shows icmp being imported from here:

2550  open("/usr/lib/python2.4/site-packages/icmp.py", O_RDONLY|O_LARGEFILE) = 5

------------------------
 J Cims

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9393#9393

-------------------- m2f --------------------
Permalink | Reply | 6 comments |
headers
jcims | 1 Aug 2007 15:39
Picon
Favicon

Re: Problem with auto-discovery

More information:

I am new to Zenoss, so i don't know how the debugging/logging works, but i added some print statements to the
Products/ZenState/Ping.py script and see there is an exception being thrown in sendPacket()

ipaddress sendto error Packet instance has no attribute 'assemble'

icmp is being imported from here according to strace:

2550  open("/usr/lib/python2.4/site-packages/icmp.py", O_RDONLY|O_LARGEFILE) = 5

This is using the rPath vmware image...which could be an important detail.  could other folks indicate what
type of install they are using?

Thanks!

------------------------
 J Cims

-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9394#9394

-------------------- m2f --------------------
Permalink | Reply | 7 comments |

Gmane