Alert error: Unable to CreateProcess

[Jeanne Cole]

Hi All

We’re trying to setup an Alert in 5.7 (Windows Server 2003) to stop and start a thread based on queue depth using the GUI Alert config – but the trigger isn’t firing, we’re getting this error:

Unable to CreateProcess: hcicmd -p inbound -c “series_all_ob pstop”

The system cannot find the file specified.

We’ve tried this on a number of different threads, but with the same outcome.  Does anyone see a problem with our setup?

Thanks for your help!

Jeanne Cole

[aler:aler:WARN/0:_hcimonitord_:02/23/2011 13:19:58] All fields in WINDOW key are taken as ‘*’

[aler:aler:WARN/0:_hcimonitord_:02/23/2011 13:19:58] Alert def loaded with warnings:

   { NAME Heartbeat }

   { VALUE opque }

   { SOURCE series_all_ob }

   { WITH -2 }

   { COMP {< 2} }    { FOR {nmin 30} }    { WINDOW */*/*/* }    { ACTION {        { exec {hcicmd -p inbound -c “series_all_ob pstop”} }    } } [aler:aler:ERR /0:_hcimonitord_:02/23/2011 13:50:05] Unable to CreateProcess: hcicmd -p inbound -c “series_all_ob pstop” The system cannot find the file specified. [aler:aler:ERR /0:_hcimonitord_:02/23/2011 13:50:05] Alert #28 failed to be triggered.

Topic

[David Barr]

That’s weird. How is your hcimonitord being started? It looks like a PATH issue.

[Robert Kersemakers]

Jeanne, have you been able to resolve this problem and if so, how?

We are having the same problem on our (very small) CL5.6 Windows 2003 version. I never had the need for alerts on this machine, but ust like you I am now trying to restart a process/thread when it’s down, but I always get this error:

Code:

[aler:aler:INFO/0:  hcimonitord:04/16/2012 14:54:15] New alert #12:
{VALUE ps} {SOURCE {qry_qas }} {MODE actual} {WITH -1} {COMP {== dead}} {FOR {nsec 5}} {WINDOW {* * * * * *}} {HOST {}} {ACTION {{exec {hcienginerun -p qry_qas}}}}
[aler:aler:ERR /0:  hcimonitord:04/16/2012 14:54:25] Unable to CreateProcess: hcienginerun -p qry_qas
The system cannot find the file specified.

[aler:aler:WARN/0:  hcimonitord:04/16/2012 14:54:25] Alert #12 triggered.
alert: {VALUE ps} {SOURCE {qry_qas }} {MODE actual} {WITH -1} {COMP {== dead}} {FOR {nsec 5}} {WINDOW {* * * * * *}} {HOST {}} {ACTION {{exec {hcienginerun -p qry_qas}}}}
action: hcienginerun -p qry_qas
[aler:aler:WARN/0:  hcimonitord:04/16/2012 14:54:25] Completed Cascade Actions

I have tried starting the hcimontord under user ‘hciuser’ from command prompt, but same error. Weird thing is: if I open a command prompt from the GUI and then execute the hcienginerun command, it works fine. But if I do this from the alert, then it fails.

Anybody else out there who knows the solution for this problem? Thanks in advance.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Robert Kersemakers]

Put in a call to our local supplier; we should try to call a batch-script, where first a ‘hcisetroot’ and ‘hcisetsite’ are invoked. We are going to try that.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[James Cobane]

Robert,

Why not simply add the setroot and setsite commands to your existing exec statement in your alert:

exec {setroot;setsite yoursitename;hcienginerun -p qry_qas}

Hope this helps.

Jim Cobane

Henry Ford Health

[Robert Kersemakers]

Hi James,

Brilliantly simple, so I tested it very quickly. But alas: it’s windows, so it only executes the first command. Windows doesn’t separate commands with ‘;’.

Will need to work on that batch-script then.

Thanks!

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Robert Kersemakers]

So I got it to work with scripts, like the following start_thread script:

Code:

@ECHO OFF
:: Parameters:
:: 1 = site
:: 2 = process
:: 3 = thread
call setroot
call setsite %1
call hcicmd -p %2 -c “%3 pstart”

You need to ‘call’ the setroot/setsite commands, or else only this command will be executed and nothing else after that. That made me wonder if I could still use James’ solution, but ‘exec {call setroot; call setsite…}’ didn’t work. I even found out that Windows uses % to separate commands on one line, but I didn’t get that to work either.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Author]

Replies