- This topic has 10 replies, 5 voices, and was last updated 11 years, 9 months ago by .
-
Topic
-
Because of network time-outs/firewalls that drop connections in such a way that Cloverleaf doesn’t know the connection has been cut, I have been trying different ways to auto-bounce a thread based off a lastr alert in our Cloverleaf 5.8 but so far, have not found a very clean way of doing it. In researching this, I have found the following: 1) The standard hcicmds for pstop and pstart don’t work from the drop-down List when configuring an exec alert line using the GUI alert tool
hcicmd -p p_other -c “problem_thread pstop”
hcicmd -p p_other -c “problem_thread pstart”
But I saw via another user’s Clovertech task that these don’t work anyway. They just look nice I guess.
2) I setup a bat file to execute the pstop and pstart based of the lastr alert and this works about 50% of the time. The other 50% of the time it leaves the thread in a “down” status.
3) To fix this secondary problem I have setup two alerts, the first one is a lastr that calls my auto-bounce bat file that leaves the thread in a “down” status about half the time. Then I setup another alert – a down alert – that calls a pstart bat file to bring the thread back up.
All in all, not very clean. Anyone have anything better?
- The forum ‘Cloverleaf’ is closed to new topics and replies.