I have noticed "check Failed increment ctasd_mem_usage counter" error on the selfmonitoring log: (attahed is the full log)
2010:09:24-13:58:14 stuffman selfmonng[4260]: W child returned status: exit='0' signal='0'
2010:09:24-13:58:19 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 1 - 10
2010:09:24-13:58:24 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 2 - 10
2010:09:24-13:58:29 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 3 - 10
2010:09:24-13:58:34 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 4 - 10
2010:09:24-13:58:39 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 5 - 10
2010:09:24-13:58:44 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 6 - 10
2010:09:24-13:58:49 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 7 - 10
2010:09:24-13:58:54 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 8 - 10
2010:09:24-13:58:59 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 9 - 10
2010:09:24-13:59:04 stuffman selfmonng[4260]: W check Failed increment ctasd_mem_usage counter 10 - 10
2010:09:24-13:59:04 stuffman selfmonng[4260]: W triggerAction: 'cmd'
2010:09:24-13:59:04 stuffman selfmonng[4260]: W actionCmd(+): '/var/mdw/scripts/ctasd restart'
2010:09:24-13:59:08 stuffman selfmonng[4260]: W child returned status: exit='0' signal='0'
2010:09:24-13:59:13 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 1 - 10
2010:09:24-13:59:18 stuffman selfmonng[4260]: I check Failed increment ctasd_mem_usage counter 2 - 10
Thanks
This thread was automatically locked due to age.
