no-longer beta ldms_core

Posted by Jack Coates Aug 11, 2008

I've posted a beta release of ldms_core at http://www.droppedpackets.org/scripts/ldms_core/ldms_core_2-9-5beta.zip which attempts to support email authentication. If you'd like to try it out, please let me know of any errors.

 

17 days without a complaint, it must be working. 2.9.5 is published.

6 Comments Permalink

One of the more powerful tools that LANDesk gives you is a local scheduler with all sorts of useful state filters and activity triggers... it's the Local Scheduler that you're configuring when you select inventory, policy, and vulnerability scan windows in Agent Configuration, and it's able to do some powerful things: http://community.landesk.com/support/docs/DOC-2328

 

 

One of its most useful features is the /IPADDR trigger, which causes a script to run at IP Address changes. By default this is used to launch inventory scans, but it's also useful for making decisions that depend on which netwok you've just joined... this is the concept that drives auto_gateway.vbs.

 

 

The problem with auto_gateway.vbs is that you want it to go onto systems that are, well, using the gateway... in other words, connectivity is spotty, it might not be able to download from internal servers, and you want something that will keep trying until it gets it right. Something like a vulnerability scan, in other words. Here's a custom vulnerability that installs auto_gateway and defines a Local Scheduler task to run it -- a lot can be done to improve on it, but it's a good start for solving other network-based problems as well: http://www.droppedpackets.org/security/custom-definitions/v_intl_auto_gateway-installation.xml/view

 

 

The next amazing trick is to make the vulnerability only apply to laptops... a dummy product install would do that nicely, but there ought to be a cleaner way.

0 Comments Permalink

ldms_status bug fix

Posted by Jack Coates Aug 2, 2008

http://www.droppedpackets.org/scripts/ldms_status

 

I was at a customer Friday, and discovered that when I hovered over ldms_status, it would turn red, flail madly, and keel over dead, sort of like Bowker holding a ball at first and trying to decide what to do with it. Turns out, their server had 1 Inventory Service thread and 4500 clients, so LDSCAN contained a backlog of 4300 inventory scans, and growing. Whenever CountPendingScans ran, ldms_status was correctly deciding to restart the inventory service. It was incorrectly ignoring several instructions to wait a few seconds, and it was incorrectly doing this over and over as long as I hovered over the icon, causing a flickering stream of balloon tips and event viewer messages and doing nothing for the backlog of scans.

 

Partially, this is a discovery of unexpected behavior from the poorly documented perltray... I'm discovering that the Tooltip subroutine runs repeatedly as long as you're hovering on the icon, and I suspect that it sets the Timer too, overriding my timer settings. But the other part is that I was sloppy about the tooltip in the first place, and was calling code on demand. So, I decoupled the CountPendingScans subroutine from ToolTip. I'd been meaning to do that anyway as a matter of good practice, so finding a bug is just good impetus to do it right.

0 Comments Permalink
LANDesk Community powered by Jive Software's Clearspace ® Subscribe| Legal Notices| Investor Relations| Avocent| Privacy Policy © 2009 LANDesk Software