Hi folks...
I've got a REALLY strange one here. A customer has recently upgraded to CMOD 8.5.0.6, and is seeing a very strange behaviour after just a few hours of CMOD running. The arssockd process spawns multiple 'child' processes of the 'license' server. I've never worked on this server before (and wasn't involved in the upgrade) so this behaviour is totally mysterious. Here's a sample of the process list after just 24 hours:
# ps -ef |grep arssockd
archive 409676 798936 0 Feb 01 - 0:00 arssockd-dpycserr: license (Cur(135), Max(1000))
archive 798936 1 0 Feb 01 - 78:57 arssockd-dpycserr: license (Cur(0), Max(1000))
archive 495936 798936 0 Feb 01 - 0:00 arssockd-dpycserr: license (Cur(127), Max(1000))
archive 926192 798936 0 Feb 01 - 0:00 arssockd-dpycserr: license (Cur(94), Max(1000))
archive 995668 798936 0 23:27:59 - 0:00 arssockd-dpycserr: license (Cur(3), Max(1000))
archive 999766 798936 0 Feb 01 - 0:00 arssockd-dpycserr: license (Cur(129), Max(1000))
archive 1036594 798936 0 Feb 01 - 0:21 arssockd-dpycserr: cmd
archive 1065250 798936 0 23:28:04 - 0:00 arssockd-dpycserr: license (Cur(6), Max(1000))
archive 1089894 798936 0 01:30:31 - 0:00 arssockd-dpycserr: license (Cur(9), Max(1000))
The weirdest part of all is that the server seems to run just fine, despite the weirdness.
These folks are on AIX 5.3, DB2 9.5, and (as mentioned above) CMOD 8.5.0.6.
Any insight would be GREATLY appreciated!
-JD.