J.T., Sounds like it could be a permissions issue...
It could be that the user starting the AR System automatically is probably non root or does not have enough permissions to run that run process action? But when you start it manually, you are starting it with a user that has sufficient permissions (as its root) to run the script contained in the $PROCESS$ action??? Check your startup script to see what user you are starting the AR System with automatically and check the permissions of this user and the permissions needed to run the executable used by the $PROCESS$ action.. Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of J.T. Shyman Sent: Wednesday, February 13, 2008 9:40 PM To: [email protected] Subject: Re: Using $PROCESS$ and set fields on 7.1 (RESOLVED) ** I’m pretty sure I have it set to run at 99 on run levels 345. I’ll post the header in the morning. 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: [email protected] 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: [email protected] 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: [email protected] 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: [email protected] 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 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
