Prev: solaris 10 install from netwoork dvd
Next: *** How to change Hard Limit / Open file descriptors LIVE in Solaris 10
From: victor.engle on 2 Feb 2010 09:57 Group, I have a strange problem and I'm stuck. I'm using a scheduler called UC4 to start programs/scripts etc on solaris systems. The scheduler has something called and executor on the solaris host which exec's programs as root on UC4's behalf. The issue is that with the new version of the executor, some programs hang; like EMC's symmir for example seems to get stuck in a loop and truss shows it looping on this... close(28610643) Err#9 EBADF I've written test programs to capture the environment of programs started by the executor and I can't find anything different between the new and old executors. Just looking for suggestions as to how to go about troubleshooting this problem. Thanks, Vic
From: Richard B. Gilbert on 2 Feb 2010 10:38 victor.engle(a)gmail.com wrote: > Group, > > I have a strange problem and I'm stuck. I'm using a scheduler called > UC4 to start programs/scripts etc on solaris systems. The scheduler > has something called and executor on the solaris host which exec's > programs as root on UC4's behalf. The issue is that with the new > version of the executor, some programs hang; like EMC's symmir for > example seems to get stuck in a loop and truss shows it looping on > this... > > close(28610643) Err#9 EBADF > > I've written test programs to capture the environment of programs > started by the executor and I can't find anything different between > the new and old executors. Just looking for suggestions as to how to > go about troubleshooting this problem. > > Thanks, > Vic Re-install the old version of UC4! If you have a machine that can be used as a test platform, it's best to install on the test machine first. It avoids these embarrassing situations!
From: victor.engle on 2 Feb 2010 10:54
> Re-install the old version of UC4! > > If you have a machine that can be used as a test platform, it's best to > install on the test machine first. It avoids these embarrassing situations! Thanks Richard. Of course I didn't put the new version in production. It's in a test environment until it is proven to work. Right now I can run job from the test env and compare results to production. |