OnDemand User Group

Support Forums => MP Server => Topic started by: dbenson100 on September 13, 2017, 07:58:59 AM

Title: High CPU utilization on AIX 7.1 (IBM license monitor utility)
Post by: dbenson100 on September 13, 2017, 07:58:59 AM

I'm curious to know if anyone else has had problems on their CMOD server where the IBM licensing scan utility "wscanfs" has been consuming high amounts of CPU?  I am seeing this utility constantly running at above 30% CPU.  I have a number of other AIX 7.1 servers, but this production CMOD server is the only one that this is happening on.  I don't believe this is directly related to CMOD, but I have been after IBM for a resolution since January and I didn't know if anyone else is seeing issues.

Title: Re: High CPU utilization on AIX 7.1 (IBM license monitor utility)
Post by: Justin Derrick on September 14, 2017, 04:29:02 AM

Hey Dave.

I would normally kill and restart a misbehaving process.  Does the problem go away if you bounce arssockd?

-JD.

Title: Re: High CPU utilization on AIX 7.1 (IBM license monitor utility)
Post by: dbenson100 on September 18, 2017, 10:32:03 AM

I can have this service killed almost every day, but it comes back during the nightly TSM backup cycle.  It is part of Our Tivoli/BigFix implementation that IBM uses to monitor license product capacity.  My guess is it is crawling the OD repository even though we have told them to exclude this file system.

I didn't really expect any solutions here, I was just wondering if anyone else has seen a similar issue.

Thanks.

Title: Re: High CPU utilization on AIX 7.1 (IBM license monitor utility)
Post by: Justin Derrick on September 20, 2017, 05:55:00 AM

Yeah, if this is some sort of inventory tool, it might be reading every individual file, then doing some work on each file to determine if it matches what it's looking for -- and if it ends up searching the caches, yeah...  it'll be doing that for a looooong time.

I'd double-check the configuration to see if you've typo'd the cache filesystems or something.  Otherwise, you'll need to start harassing IBM regularly.

-JD.