When encountering a situation like the Autosys programs are not processing anything (example: scheduler does not seem to be processing events, application server is not processing requests, WebUI is taking up CPU but not letting any activity go by), collecting stack information from such programs will help Support and Engineering teams diagnose the issue at hand.
AutoSys Workload Automation
WCC/WebUI
Main WCC:
count=1
while [ $count -le 6 ]; do
echo "iteration $count out of 6, sleeping 30seconds"
kill -3 `ps -few|grep CA_WCC_INSTALL_LOCATION |grep -v grep |awk '{print $2}'`
count=$((count+1))
sleep 30
done
Collector:
count=1
while [ $count -le 6 ]; do
echo "iteration $count out of 6, sleeping 30seconds"
kill -3 `ps -few|grep com.ca.wcc.collector.CollectorApplication |grep -v grep |awk '{print $2}'`
count=$((count+1))
sleep 30
done
AutoSys
Scheduler / event_demon:
count=1
while [ $count -le 6 ]; do
echo "iteration $count out of 6, sleeping 30seconds"
pstack `ps -few|grep "event_demon -A"|grep -v grep|awk '{print $2}'` > pstack_event_demon_$count.txt
count=$((count+1))
sleep 30
done
Application Server / as_server:
count=1
while [ $count -le 6 ]; do
echo "iteration $count out of 6, sleeping 30seconds"
pstack `ps -few|grep "as_server -A"|grep -v grep|awk '{print $2}'` > pstack_as_server_$count.txt
count=$((count+1))
sleep 30
done
Web Server / AEWS:
count=1
while [ $count -le 6 ]; do
echo "iteration $count out of 6, sleeping 30seconds"
pstack `ps -few|grep "AEWS"|grep -v grep|awk '{print $2}'` > pstack_AEWS_$count.txt
count=$((count+1))
sleep 30
done
Provide the pstack_*.txt files as well as $AUTOUSER/out/* files for the problematic day in question for Support review.