exec from Alert panics process

[Tim Malaney]

In trying to shutdown a thread in an alert, using the exec value of “hcicmd -p t_anc6 -c “HLAB_RES_SEND pstop”” shuts down the thread then seconds later panics the process —

[cmd :cmd :INFO/0:   t_anc6_cmd:02/27/2008 08:03:13] Doing ‘pstop’ command on thread ‘HLAB_RES_SEND’

[prod:prod:INFO/0:HLAB_RES_SEND:02/27/2008 08:03:13] Checking for leaked handles in the General interpreter…

[prod:prod:INFO/0:HLAB_RES_SEND:02/27/2008 08:03:13] Checking for leaked handles in the TPS interpreter…

[cmd :cmd :INFO/0:   t_anc6_cmd:02/27/2008 08:03:14] Receiving a command

PANIC: “str != ((char *) 0)”

PANIC: Calling “pti” for thread t_anc6_cmd

---

Scheduler State

---

Thread Events     State      Priority Runnable  PT Msgs

Anyone run into this issue. Running HPUX 5.4.1

Thanks

Topic

[Tim Malaney]

If anyone is interested, the same line in a script works, unless the script is called from an alert. This panics the process. If I pipe the command to output in the script, then run the script from an alert it works. This works in a script called from an alert;

hcicmd -p t_anc6 -c “HLAB_RES_SEND pstop” |tee -a $Log

[Kathy Zwilling]

Tim,

I have been having this same issue and found your email.   Has the resolution that you described fixed this for good?

Why the tee command?

Thanks,

Kathy Zwilling

[Robert Milfajt]

Quote:

Why the tee command?

tee takes the output of the command and writes it to a file specified in the arguments.  The -a flag says to append the output and not to overwrite the file.

This is good when using log files for various cron jobs, etc.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Tim Malaney]

Using the tee command to route the response from the shutdown command works. Otherwise the command thread appears to try to process the response.

[Author]

Replies