Re: Remedy BRIE Process did not shut down on ARSystem stop

[George Jungle]

**

Peter,

 

There was actually one more spot to modify within the Startup/Shutdown script.

 

Check out the last 2 lines of the extract below to. (this is what seems to execute the bit of code in the attachment you've got).

 

This works a treat for us now.

 

George.

 

 

 

#================================================
# ARSYSTEM_STOP - Stop the armonitor and associated servers
#================================================
ARSYSTEM_STOP()
{
    echo "Action Request System shutdown in progress."
    rpcb=`rpcinfo -p 1>/dev/null 2>&1;echo $?`
    [ $rpcb -eq 0 ] && rpcinfo -d 390600 1  1>/dev/null 2>&1
    #stop all the daemons (armonitor, arserverd, armaild, arservdsd, arservftd)
    STOP_SERVER "armonitor"
    [ $? -eq 1 ] &&  echo "Action Request System Monitor shutdown failed."
    STOP_SERVER "arserverd"
    [ $? -eq 1 ] &&  echo "Action Request System Server shutdown failed."
    STOP_SERVER "armaild"
    [ $? -eq 1 ] &&  echo "Action Request System Email Server shutdown failed."
    STOP_SERVER "arservdsd"
    [ $? -eq 1 ] &&  echo "Action Request System Distributed Server shutdown failed."
    STOP_SERVER "arservftd"
    [ $? -eq 1 ] &&  echo "Action Request System Full Text Index Server shutdown failed."
    STOP_SERVER "brsvcbrie"
    [ $? -eq 1 ] &&  echo "Action Request System Brie Server shutdown failed."


 

On 4/20/06, Lammey, Peter A. <[EMAIL PROTECTED]> wrote:

**

We experienced a problem this morning on one of our Remedy 6.3 servers where connection was lost to the database.
The database went down in actuality this morning for 6 minutes and then came back up.
We have a Unix service that checks for the application to be up and if it is not it stops and restarts Remedy by executing the arsystem stop and arsystem start.

We found this morning that the stop of arsystem did not bring down the BRIE process on the server.
When I contacted Remedy they indicated they have bug on this issue and a workaround that might work for us.
A while back we experienced an issue like this when we were setting up our development server and we noticed multiple BRIE processes and applied their same workaround code but it didn't seem to work.

<<BRIEarconffix.txt>>
Has anyone else experienced this same kind of issue and found a way to correct it?

Thanks
Peter Lammey
ESPN MIT Technical Services & Applications Management
860-766-4761

__20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___