This is now becoming a consistent / persistent problem. I had to kill -9 to stop the dsmserv process. I restarted the server (via service .. start) and there didn't seem to be any damage done.
However, attempting to stop/halt it, again, produced the same result - dsmserv using 200% CPU and after 2-hours I had to kill -9. So, obviously there are big enough changes in 6.3.3 vs 6.3.2, to cause problems like this, since none of my 6.3.x or 6.2.x servers exhibit this behavior. Any suggestions on how to diagnose this "issue" before I contact IBM and open a PMR? On Thu, Nov 29, 2012 at 2:04 PM, Zoltan Forray <[email protected]> wrote: > Just did my first install/conversion of a 6.2.3 TEST server to 6.3.3.000 > (RH Linux) > > While the install and startup went fine, it won't HALT. > > After the install/upgrade, I got in via dsmadmc just fine. Checked the > actlog - saw all the schema changes/upgrades. Updated/registered the > licenses and then issued HALT. Got the usually warning and said YES. > > Now it has been sitting for >25-minutes since the halt. > > Can't get back in via dsmadmc. > > Top shows dsmserv using >200% CPU. > > I tried standard kills, with no luck. I hate to do a kill -9 but will if > I don't have a choice. > > What the heck is it doing? Should I wait longer or just kill it with > extreme prejudice? > > -- > *Zoltan Forray* > TSM Software & Hardware Administrator > Virginia Commonwealth University > UCC/Office of Technology Services > [email protected] - 804-828-4807 > Don't be a phishing victim - VCU and other reputable organizations will > never use email to request that you reply with your password, social > security number or confidential personal information. For more details > visit http://infosecurity.vcu.edu/phishing.html > > -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
