[Migrated content. Thread originally posted on 21 March 2012]
CASSTART - when the script runs twice the second time shuts down the region.
In testing thi start up script. I placed the call to the script in the "execute now" box.
I clicked on the execute button and the region started without problems.
I then accidentally clicked on the execute button again and the region showed "stopped" and under the status log the "server" and "CP 1" had no indicators. The task manager had the cascd and the casmgr still running. I killed these guys and brought the region down.
So I guess there's 2 questions implied:
a) why does starting a region which cause the region to crash
b) if the status is stopped why were the tasks still running?
Any thoughts...
#EnterpriseDeveloperCASSTART - when the script runs twice the second time shuts down the region.
In testing thi start up script. I placed the call to the script in the "execute now" box.
I clicked on the execute button and the region started without problems.
I then accidentally clicked on the execute button again and the region showed "stopped" and under the status log the "server" and "CP 1" had no indicators.
casstart itself shouldn't have that effect. Unless something else in your script does, then there's really no way to tell what happened without looking at diagnostics.
The task manager had the cascd and the casmgr still running. I killed these guys and brought the region down.
So I guess there's 2 questions implied:
a) why does starting a region which cause the region to crash
It doesn't, normally. We'd need a failure diagnostic collection to investigate what happened in this particular case.
b) if the status is stopped why were the tasks still running?
The CAS processes are loosely coupled to the MFDS (directory) process, which is what's showing the region status. MFDS has no way of knowing what CAS processes are running; MFDS isn't even necessarily running on the same machine.
The region status that MFDS displays is a field in the MFDS configuration repository, which is updated by various region processes (either cascd or casmgr, and mfcs). As region startup progresses those processes will update the MFDS configuration with the current region state. Similarly, as the region shuts down, various processes update the configuration to indicate that it's stopping. At some point, they have to change the status to "stopped"; and that has to happen before all the processes have exited (or there wouldn't be anything to set the status).
[Migrated content. Thread originally posted on 21 March 2012]
CASSTART - when the script runs twice the second time shuts down the region.
In testing thi start up script. I placed the call to the script in the "execute now" box.
I clicked on the execute button and the region started without problems.
I then accidentally clicked on the execute button again and the region showed "stopped" and under the status log the "server" and "CP 1" had no indicators. The task manager had the cascd and the casmgr still running. I killed these guys and brought the region down.
So I guess there's 2 questions implied:
a) why does starting a region which cause the region to crash
b) if the status is stopped why were the tasks still running?
Any thoughts...
#EnterpriseDeveloperThanks. I'll open a ticket with support and go that route rather the forum.
