DX Unified Infrastructure Management

We have a script that runs every 15mins which looks for the alarm message from the controller "FAILED to start" and then it runs the Probe_verify & probe activate against these.  

We have a dedicated HUB for Servers built from images and we have hundreds of these in this state on a daily basis, does anyone have a similar script we could run against all Robots against a specific HUB as we want to remove the reliance on the "FAILED to start" alert messages.

Cheers Rowan, current script below.  We would like to run a separate script against all Robots, only on one HUB.

-- Start of script
local al = alarm.list() -- Get alarm list

local re = "%p%a+%d*_*%a*%d*%p" -- Regex to match probe name with alpha, numbers and underscore

if al ~= null then
for i = 1,#al do
if al[i].prid == "controller" then -- First, filter to get alarms from controller probe only

if string.match(al[i].message,"FAILED to start") then -- Second, filter to get controller alarms with specific text i-e "FAILED to start"

probe = string.gsub(string.match(al[i].message,re),"'","") -- Get probe name from alarm message and then remove quotes from probe name to use in probe_verify callback
--print(al[i].message.."! Probe-> "..probe) -- View alarms with probe names which failed to start

addr = "/"..al[i].domain.."/"..al[i].hub.."/"..al[i].robot.."/".."controller" -- Build Nimsoft address
printf("/"..al[i].domain.."/"..al[i].hub.."/"..al[i].robot.."/".."controller".."<->Probe="..al[i].prid) -- Print Nimsoft address(es)

-- Now run the probe_verify callbacks on each probe which FAILED to start

local args = pds.create()
pds.putString(args,"name",probe)
nimbus.request(addr,"probe_verify",args)
nimbus.request(addr,"probe_activate",args)
pds.delete(args)
sleep (100) -- A little delay between each probe callback
end
end
end
end
-- End of script

Hi,

Did you open a support ticket about your problem ? Or have you troubleshooted the core issue ? Most of the time it's because a probe have to start after another one (this is configurable in the probe definition if you edit the nimsoft package).

Making a callback for all robots (all probes) seem to be a bad solution (that's my developer opinion).

Best Regards,

Thomas

The issue occurs because the Servers in question are spun up from an image on a regular basis, we have a local scripts which clears the niscache on them when they start but nothing else.

What do you mean by this?

"his is configurable in the probe definition if you edit the nimsoft package"

Great stuff, I'll have a play and update the thread early next week.

Quick test of the script in our UAT environment and I get the following error:

Error in line 36: 'end' expected (to close 'for' at line 11) near '<eof>'

The script works a treat to get the list of failed / deactivated probes per HUB, however, we would like to use the extraction to run the probe verify commands against the failed ones.  Is it possible to add this to the script?