Archived community.zenoss.org | full text search
Skip navigation
Currently Being Moderated

Dev chat 12/10/2009

VERSION 1 
Created on: Dec 10, 2009 1:24 PM by Matt Ray - Last Modified:  Dec 10, 2009 1:25 PM by Matt Ray
mrayzenoss has changed the topic to: Zenoss Developers are here, Zenoss QA is in #zenoss-testing (10:00:32 AM)
10:01:16 AM mrayzenoss: my wingman is out sick this morning, hopefully some of the other Zenoss devs will be around to cover for him
10:01:53 AM mrayzenoss: we're doing a new Zenoss QA Test day in #zenoss-testing today, they should be regularly scheduled starting next year
10:02:24 AM mrayzenoss: every 2 weeks, just like this session, only they're all day and focused on a single area of testing.  Today we're focusing on the Event Console
10:02:38 AM zenethian: (which is awesome)
iancmcc [n=__ian__@69-165-165-135.dsl.teksavvy.com] entered the room. (10:03:54 AM)
mode (+o zenethian ) by ChanServ (10:04:14 AM)
10:04:46 AM zenethian: 09:59 -!- iancmcc [n=__ian__@69-165-165-135.dsl.teksavvy.com] has joined #zenoss
10:04:46 AM zenethian: 09:59 -!- mode/#zenoss [+o zenethian] by ChanServ
10:04:49 AM zenethian: argh
10:04:56 AM zenethian: stupid copy and paste
10:04:59 AM cgibbons: don't let ian in, crap too late
10:05:11 AM zenethian: we can always kick him out, he doesn't have ops. 
mode (+o iancmcc ) by zenethian (10:05:18 AM)
10:06:53 AM zenethian: I remember back in the day when we used to have to packet people and ride netsplits to get ops.
10:07:18 AM zenethian: Uphill in the snow, even.
10:07:24 AM ckrough: with no shoes
devnet left the room (quit: Connection timed out). (10:09:20 AM)
ckrough left the room (quit: "leaving"). (10:21:17 AM)
10:25:01 AM jb: hey rmatte
10:25:02 AM jb: you here?
10:27:07 AM gwb2351: so is this the open time to bug developers about stuff?
10:27:44 AM zenethian: Sure.    Feel free
10:28:41 AM jb: anybody here used jane's mass import script?
10:29:25 AM Jane_Curry: I would appreciate input on this - there were some update issues reported back at 2.3
10:29:39 AM jb: oh speaking of the devil
10:29:42 AM Jane_Curry: Anyone got more current experience?
10:29:50 AM jb: Jane_Curry: i'm trying to use it right now..
10:30:21 AM gwb2351: how about that solaris zenpack...
10:30:27 AM jb: Jane_Curry: http://pastebin.com/mf75e8dc
10:30:40 AM adytum-bot: Title: pastebin - collaborative debugging tool (at pastebin.com)
10:30:43 AM gwb2351: do you have any near-term plans to "officially" support zones ?
10:31:41 AM jb: Jane_Curry: any idea why is barfing?
10:32:17 AM Jane_Curry: Ticket #4869 was raised to address the problems but it's still open
10:32:48 AM mrayzenoss: gwb2351: I'll look into the zones support
10:33:18 AM jb: Jane_Curry: anyway around it?  i know some people have been using it..
10:34:31 AM mrayzenoss: gwb2351: well, the Extended Monitoring Guide lists that as a limitation, I'll see if it's being worked on
10:34:51 AM Jane_Curry: I found that hand-editing any field in a barf'ed device seemed to restore it..
10:35:01 AM jb: Jane_Curry: none of the devices are actually being added..
10:35:02 AM Jane_Curry: .. didn't try with zendmd..
10:35:19 AM gwb2351: yeah, the case i opened is 8751
10:35:23 AM jb: Jane_Curry: it says they are, but they aren't in the GUI
Da-Geek left the room (quit: "Leaving"). (10:35:38 AM)
10:35:49 AM Jane_Curry: .. but manually editing stuff is probably a no-no - if you need to script-add you don't want to back and touch them all
10:36:45 AM jb: hm
10:36:54 AM jb: INFO:zen.DeviceLoader:Device 10.1.48.15 loaded!
10:37:01 AM Jane_Curry: jb - what version of Zenoss are you on?
10:37:03 AM jb: its just not showing up anywhere
10:37:04 AM jb: 2.5.1
ke4qqq___ [n=ke4qqq@65.5.145.2] entered the room. (10:40:16 AM)
ke4qqq left the room (quit: Read error: 145 (Connection timed out)). (10:42:46 AM)
10:47:58 AM gwb2351: mrayzenoss: and the trac is https://dev.zenoss.com/tracint/ticket/1986
gorkadel01 left the room (quit: "This computer has gone to sleep"). (10:49:08 AM)
devnet [n=devnet@207.59.52.2] entered the room. (10:51:56 AM)
10:53:04 AM jb: guess it doesn't work
10:53:04 AM jb: hm
theacolyte left the room. (10:54:54 AM)
10:59:37 AM gwb2351: so developer-types, i have this problem using ssh to older solaris boxes that don't support aes-265...
10:59:47 AM gwb2351: aes-256, sorry
11:00:04 AM Jane_Curry: I have just retested the script with a 2-line import file and it works for me
11:00:11 AM Jane_Curry: The first data line was
11:00:16 AM Jane_Curry: "group-100-a1.class.example.org","/VM-land","/Raddle",,"/snmp_no_ping",,,,,"2","12345","1",,,,,"300","","","1"
11:00:21 AM Jane_Curry: and the second
11:00:42 AM jb: 10.1.41.15,,/DCs,/FMS,/Devices/Server/Windows/DC,Dell,,Microsoft,Windows 2003,,,,,fcsnmp1ro,,2c,,,,
11:00:42 AM Jane_Curry: "server.class.example.org","/VM-land","/Raddle",,"/Server/Linux",,,,,"2","12345","1",,,,,"1000","","","1"
11:00:45 AM jb: is what im using
11:00:53 AM jb: they need double quotes around every value?
11:02:36 AM rmatte: jb: ah crap, yeh they do
11:02:44 AM rmatte: jb: but the comment in the script doesn't specify that
11:02:52 AM rmatte: it just shows bleh,bleh,bleh,bleh
11:03:21 AM Jane_Curry: I've just pasted your line into my csv file and it shows up OK in the device list
11:03:37 AM rmatte: jb: If you're using excel, it only supports output with commas and no quotes, but you can always install openoffice which supports the "","","" style output
11:04:02 AM jb: hrmm
11:04:08 AM jb: Jane_Curry: odd.
11:04:16 AM jb: so you used it without double quotes?
11:04:16 AM Jane_Curry: so I don't think the quotes are necessarily your problem
11:04:32 AM Jane_Curry: exactly as you posted - I pasted
11:04:44 AM rmatte: Jane_Curry: by the way, you old links to that script got trashed when they moved to the new community site, it'd be worth reposting it
11:04:52 AM rmatte: s/you/your
11:05:16 AM jb: well, then this does not make sense
11:05:20 AM jb: the devices are not being added
11:06:02 AM Jane_Curry: Can you try pasting one of my lines into a csv input file - just to test the quoting?
11:06:13 AM jb: sure, it will work even though I don't have those locations/groups/etc?
11:06:30 AM rmatte: it'll create them I believe
11:06:39 AM rmatte: from what I recall
11:06:57 AM jb: yep, with your line, it attempts to model
11:07:01 AM Jane_Curry: correct - it will create any groups, locations, systems it needs
11:07:07 AM jb: and the device was added
11:07:22 AM rmatte: jb: then there's something wrong with your line I guess
11:07:26 AM jb: yeah
11:07:41 AM rmatte: the first thing that jumps out at me is...
11:07:46 AM rmatte: 10.1.41.15,,/DCs,
11:07:47 AM rmatte: versus
11:07:56 AM rmatte: "server.class.example.org","/VM-land",
11:08:02 AM jb: no location
11:08:08 AM rmatte: ah
11:08:08 AM jb: and i also prefixed the device class with /Devices
ideopathic [n=ideopath@vpn.filmdept.com] entered the room. (11:08:09 AM)
11:08:10 AM jb: jane didnt
11:08:14 AM rmatte: thought VM-land was a device group
11:08:26 AM rmatte: yeh, you don't need /Devices
11:08:32 AM rmatte: it knows it's adding it as a device class
11:08:51 AM Jane_Curry: Nope, VM-land is a location
11:09:00 AM jb: that was it
11:09:09 AM rmatte: ah
willwh left the room (quit: Nick collision from services.). (11:09:25 AM)
willwh1 [n=willwh@24.68.238.209] entered the room. (11:09:26 AM)
willwh1 is now known as willwh (11:09:36 AM)
11:09:36 AM jb: although it didnt model
11:09:40 AM jb: but the device was added
11:09:52 AM rmatte: you can model them afterwards
11:10:04 AM rmatte: I run the script and make sure it adds everything without modelling just to get it in there
11:10:10 AM rmatte: then model it using a script afterwards
11:10:22 AM rmatte: or just let zenmodel kick off and do it
11:10:29 AM jb: yeah
11:12:16 AM jb: ok, i need to play with your zenpacks for cpu monitoring with snmpinformant
11:12:44 AM jb: without rather
11:12:57 AM rmatte: hehe
11:12:59 AM Jane_Curry: I get the model automatically  - you should see it after the Device loaded message
11:13:25 AM jb: this is going to be a large install
11:13:28 AM jb: ~900 devices
11:13:31 AM jb: basic monitoring though
11:13:40 AM jb: if it will even work
11:13:50 AM otakup0pe: ok so quick question.... how would i go about making the transform window  (when editing an event class) a heck of a lot larger
11:14:00 AM otakup0pe: or should i just give up and edit my transforms in vim :3
11:14:23 AM otakup0pe: also can you use any TALES expression in the "rule" field ?
11:14:45 AM Jane_Curry: Good question otakup0pe!
11:14:54 AM otakup0pe: which one
11:15:01 AM otakup0pe: i'm more amused than anything that i have a 20 line transform :3
11:15:07 AM jb: hrm, wonder if I can disable IP service monitoring all together
11:15:10 AM otakup0pe: but if the rules are TALE's as well...
11:15:13 AM otakup0pe: jb: should be able to ?
11:15:20 AM Jane_Curry: making the transform window big enough to use sensibly
11:15:25 AM otakup0pe: isn't that just a matter of disabling the right zproperty at the right place ?
11:16:30 AM jb: i thikn so
11:16:32 AM jb: checking now
gorkadel01 [n=gorka@extranet.mairie-saint-ouen.fr] entered the room. (11:17:02 AM)
11:17:14 AM Jane_Curry: New topic.....
11:17:55 AM Jane_Curry: Several folk have had problems when upgrading  to 2.5 with broken services / processes and resulting dead zenprocess / zenstatus
11:18:22 AM jb: i need to carve out some raid10 space for this
themurph left the room (quit: Read error: 104 (Connection reset by peer)). (11:19:04 AM)
11:19:16 AM Jane_Curry: Discard the threads where the issue was the WMI ZenPack..
11:19:59 AM Jane_Curry: there seem to be several folk who have real corruptions in the Zope database of either process monitoring or status monitoring
11:20:06 AM mrayzenoss: if you could point me to the threads, we can open tickets accordingly
11:20:19 AM mrayzenoss: especiallyif we can get QA to recreate
11:20:26 AM Jane_Curry: message/42570#42570
gorkadel01 left the room (quit: Client Quit). (11:20:50 AM)
11:21:11 AM Jane_Curry: thread/11846
11:21:26 AM jb: hrm, i can't  get to the community site right now
11:21:33 AM mrayzenoss: yeah, me neither
11:21:53 AM Jane_Curry: message/43110#43110 - this is a close match to my issue
11:22:02 AM adytum-bot: Title: Open Source Network Monitoring and Systems Management - Need a hand deleting an OsProcess... (at community.zenoss.org)
11:22:16 AM mrayzenoss: apparently adytum-bot can reach zenoss.org
11:22:25 AM jb: there it goes
11:22:31 AM jb: just very slow
11:22:41 AM mrayzenoss: Jive's support is looking at it right now
11:22:59 AM jb: yeah now its dead
11:23:00 AM mrayzenoss: it's in a cluster, and 1 of the nodes started failing yesterday
themurph [n=themurph@proxy1.castlebranch.com] entered the room. (11:24:10 AM)
11:25:21 AM mrayzenoss: it's back
11:25:32 AM Jane_Curry: message/41976#41976 - still on with pointers to corrupt processes...
11:25:41 AM adytum-bot: Title: Open Source Network Monitoring and Systems Management - Bad items in Processes hierarchy (at community.zenoss.org)
11:26:30 AM Jane_Curry: message/43116#43116
11:26:39 AM adytum-bot: Title: Open Source Network Monitoring and Systems Management - Need a hand deleting an OsProcess... (at community.zenoss.org)
11:26:55 AM Jane_Curry: I seem to have a rogue process instance..
11:27:26 AM Jane_Curry: ran reindex() and commit() in zendmd and I can now get zenprocess running again
11:27:58 AM Jane_Curry: The (single) device that has the process now looks like it is monitoring the correct processes
11:28:07 AM Jane_Curry: and gathering data but...
11:29:00 AM Jane_Curry: If I go to Processes// and select the offending process then the GUI barfs
11:29:12 AM Jane_Curry: so there is still something a bit adrift
swygue [n=rheron@69.64.209.66] entered the room. (11:30:51 AM)
11:31:34 AM Jane_Curry: In zendmd, I have tried
ideopathic left the room (quit: ). (11:32:14 AM)
11:32:15 AM Jane_Curry: for d in dmd.Processes.Zenoss.osProcessClasses.zenhub.instances(
11:32:22 AM Jane_Curry:    print d.id
11:32:58 AM Jane_Curry: where Zenoss is my  and zenhub is my process
willwh left the room (quit: Read error: 145 (Connection timed out)). (11:33:47 AM)
11:34:02 AM Jane_Curry: I get TWO identical instances of the process that was barfing in zenprocess.log
11:34:13 AM Jane_Curry: usr_local_zenoss_python_bin_.python.bin b411a17f7dc5dff7b67725a7babc0dbb
11:34:37 AM Jane_Curry: Anyone know how to delete one of these instances?
willwh [n=willwh@unaffiliated/willskills] entered the room. (11:36:03 AM)
cryptographrix left the room (quit: Read error: 110 (Connection timed out)). (11:38:16 AM)
11:40:23 AM mrayzenoss: Grrr… the dev who was supposed to cover this session today worked on a bunch of tickets on process monitoring, I'm having trouble finding domain expertise
daveborg98 [n=dborg@66.210.91.34] entered the room. (11:43:02 AM)
11:44:47 AM iancmcc: Jane_Curry: that kind of surgery can be tricky. One sec, I'm working on the steps.
11:52:30 AM iancmcc: okay, probably the easiest way is to get the index of one of those
11:52:47 AM iancmcc: dmd.Processes.Zenoss.osProcessClasses.zenhub.instances._objects
11:52:51 AM iancmcc: and then do:
11:53:20 AM iancmcc: dmd.Processes.Zenoss.osProcessClasses.zenhub.instances._remove(dmd.Processes.Zenoss.osProcessClasses.zenhub.instances._objects[n])
11:53:25 AM iancmcc: where n is the index
nzle left the room (quit: Connection timed out). (11:58:30 AM)
nzle [n=nzle@smtp.bgsinc.com] entered the room. (12:03:42 PM)
12:04:30 PM Jane_Curry: Not sure I understand the bit about getting the index - please could you elaborate slightly?
12:07:15 PM Jane_Curry: By index, do you mean the id field )I'd always thought this was identifier, not index...)
12:07:31 PM iancmcc: no, just the integer indicating position in the list.
12:07:50 PM iancmcc: kill the second one.
12:07:55 PM iancmcc: so if you only have two, n would be 1
12:09:00 PM Jane_Curry: so if my for d in dmd.Processes.Zenoss.osProcessClasses.zenhub.instances( print d.id test
12:09:32 PM Jane_Curry: delivers 4 lines and the offending duplicate is printed in lines 1 and 4,
12:09:50 PM iancmcc: then you want 3
12:09:55 PM iancmcc: as 0 is the first index
cain22 [n=cain@operation5.com] entered the room. (12:09:56 PM)
12:10:04 PM cain22: hello all
12:10:14 PM Jane_Curry: Gotcha
12:10:20 PM cain22: anyone get the following error when upgrading to 2.5.1
12:10:27 PM cain22: WARNING:ZEO.zrpc:(26145) CW: error connecting to ('localhost', 8100): ECONNREFUSED
12:10:35 PM aclark: iancmcc!
12:10:47 PM iancmcc: cain: zeo isn't running.
12:11:12 PM mrayzenoss: cain22: what installer did you use?
12:11:27 PM cain22: its an appliance
12:12:57 PM cain22: ?
12:13:55 PM iancmcc: aclark: indeed, I am here.
12:14:21 PM mrayzenoss: cain22: on the vm, go to the console and login as root (no password)
12:14:34 PM mrayzenoss: cain22: do a 'su - zenoss zenoss status'
Bryanstein [i=bryan@free.psybnc.and.eggdrop.at.shellium.org] entered the room. (12:14:50 PM)
12:14:53 PM mrayzenoss: cain22: and if something isn't running, do a 'su - zenoss zenoss restart' and check again
12:15:42 PM cain22: im in the middle of an updgrade, didn't think that restarting zenoss would be a good idea
12:16:30 PM cain22: the only thing that was supposed to be on was zeoctl
12:16:35 PM mrayzenoss: cain22: ok, then just do 'zeoctl start'
12:16:49 PM cain22: i did couple minutes ago
12:17:00 PM cain22: and as of a minute ago it looks to be continueing the upgrade
12:17:20 PM cain22: so i'll cross my fingers and hope everything is okey dokey
12:17:39 PM mrayzenoss: ahh, ok.  You're upgrading the appliance, needed the context
12:17:52 PM iancmcc: yeah, it's fine. That error message occasionally appears if zeo was a little slower than the other daemons to start
12:17:55 PM cain22:  cain22: what installer did you use?
12:17:56 PM cain22: > its an appliance
12:18:02 PM iancmcc: but they're smart enough to get a connection when it starts up, so no big deal.
12:18:21 PM mrayzenoss: *brain is fried*
12:19:01 PM cain22: lol its cool
12:19:08 PM cain22: how does everyone like the new upgrade?
12:19:15 PM cain22: better performance?
Comments (0)