I solved this by disabling the chkconfig script and adding a line to run it with the start parameter in rc.local which runs last in the startup order.
J.T. Shyman Column Technologies _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Axton Sent: Wednesday, February 13, 2008 9:29 PM To: arslist@ARSLIST.ORG Subject: Re: Using $PROCESS$ and set fields on 7.1 (RESOLVED) ** Could it be the run order? Post the header from the /etc/init.d file where the run levels and run orders are defined. e.g., #!/bin/sh # # named # # chkconfig: 2345 15 85 Axton Grams On Feb 13, 2008 9:18 PM, J.T. Shyman <[EMAIL PROTECTED]> wrote: ** Ok, final solution: Don't start ARSystem automatically at startup. I've got a chkconfig script starting ARSystem automatically on system boot. For some reason, ARSystem started this way doesn't work well with the $PROCESS$ set fields action. However, if I log in as root and stop/start the ARSystem, using the same script then the $PROCESS$ set fields actions work. No idea what is causing this at this point, but I've got a solution J.T. Shyman Column Technologies _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of J.T. Shyman Sent: Wednesday, February 13, 2008 7:47 PM To: arslist@ARSLIST.ORG Subject: Re: Using $PROCESS$ and set fields on 7.1 False alarm. A reboot of the VM brought the problem back.meaning it is environmental. Back to the drawing board. J.T. Shyman Column Technologies _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of J.T. Shyman Sent: Wednesday, February 13, 2008 5:46 PM To: arslist@ARSLIST.ORG Subject: Re: Using $PROCESS$ and set fields on 7.1 All, Patch 001 to the linux version of ARSystem 7.1 corrects this and it works as expected now. J.T. Shyman Column Technologies _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of J.T. Shyman Sent: Monday, February 11, 2008 3:11 PM To: arslist@ARSLIST.ORG Subject: Using $PROCESS$ and set fields on 7.1 I'm having a strange issue trying to use an external process in a set fields action on AR 7.1 on Red Hat 4. I've created a simple form with a button and an active link that fires on that button that does nothing more than a set fields action which includes: $PROCESS$ @@:echo $HOSTNAME This works fine on an AR 7.0.1 Patch 005 server but not on a AR 7.1 server. The AR 7.1 server tells me there is an error in the set fields action and, when I converted it to a filter to see if I could get more information, it turns out the return code on the 7.1 server is 1 and not 0. I'm using the exact same form and workflow as I exported them from the 7.0 server and imported them on the 7.1 server. I haven't found a defect or KB entry on BMC's site about $PROCESS$ not working in 7.1 or being fixed in patch 001. Does anyone have a AR 7.1 server running on Linux that is also experiencing this? J.T. Shyman Column Technologies __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
