Terry may have a point there.. Especially if you had previously started the AR Server with a user other than the user that you are now starting it up with, and there are still some files that the AR Server tries to write to, that is still owned by that previous user.
Joe ________________________________ From: Terry Bootsma <[email protected]> To: [email protected] Sent: Wednesday, July 29, 2009 2:47:10 PM Subject: Re: Upgrade issues with 7.1 ** I am wondering if it has something to do with the permissions under which the arsystem binaries are running within your Unix environment. Are you running as non-root? If so, does the error go away when running as root? It might be a starting point.. Terry On Jul 29, 2009, LJ Longwing <[email protected]> wrote: Hmmm....not sure then...sorry > >-----Original Message----- >From: Action Request System discussion list(ARSList) >[mailto:[email protected]] On Behalf Of jaimie >Sent: Wednesday, July 29, 2009 11:25 AM >To: [email protected] >Subject: Re: Upgrade issues with 7.1 > >I turned off logging and then deleted the arerror.log. I then restarted the >server and am getting the same error. It only occurs during >starting/stopping the server. > >On Jul 29, 12:05 pm, LJ Longwing <[email protected]> wrote: >> Wow....I completely missed >> >> Wed Jul 29 08:46:00 2009 WriteWorkflowTraceLog() >> >> Yes, I agree with Fredrick, turn off your workflow logging (filter, >> api, >> etc) and then restart...I would not expect that error if you don't >> have logging turned on at startup/shutdown... >> >> >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> >> [mailto:[email protected]] On Behalf Of Grooms, Frederick W >> Sent: Wednesday, July 29, 2009 9:58 AM >> To: [email protected] >> Subject: Re: Upgrade issues with 7.1 >> >> We see that error all the time when we are shutting down the ARS binaries. >> It is due to the fact that the thread that does the logging is closed >> before the other threads. Stop the app and delete the arerror.log >> file. When you restart the app check if you still receive the error. >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:[email protected]] On Behalf Of LJ Longwing >> Sent: Wednesday, July 29, 2009 10:38 AM >> To: [email protected] >> Subject: Re: Upgrade issues with 7.1 >> >> I'm by no means an expert on Unix systems, but this is Remedy >> complaining about the ability to kick off os level threads...so this >> is something you will need to tweak at the OS Level, not Remedy. >> >> -----Original Message----- >> From: Action Request System discussion list(ARSList) >> [mailto:[email protected]] On Behalf Of jaimie >> Sent: Wednesday, July 29, 2009 9:21 AM >> To: [email protected] >> Subject: Upgrade issues with 7.1 >> >> Hi Everyone, >> >> We keep seeing the below error in our arerror.log. We have already >> verified that we have enough memory allocated and we have increased >> our thread counts. BMC technical support cannot seem to help us and >> we have done everything that was suggested in forums. We have >> upgraded 3 test servers from 6.3 to 7.1 and all of them are displaying >> the same error. There are no other errors showing up in our >> armonitor.logs either. We are not seeing any issues while logged in, >> but we want to make sure that this issue is resolved before we upgrade >> our production server. We know that ARERR 8747 is also a "false" >> error so that is not helping us either. We have only upgraded the >> server and not any other ITSM applications since we do not use them. >> We are currently on AIX 5.3 and Oracle 10g. >> >> Any suggestions would be appreciated. >> >> Thank you, >> >> Jaimie >> >> Wed Jul 29 08:46:00 2009 15 >> Wed Jul 29 08:46:00 2009 0 : Unable to access thread local storage. >> (ARERR 8747) >> Wed Jul 29 08:46:00 2009 WriteWorkflowTraceLog() Wed Jul 29 >> 08:46:00 2009 0 : Unable to access thread local storage. >> (ARERR 8747) >> Wed Jul 29 08:46:00 2009 WriteWorkflowTraceLog() Wed Jul 29 >> 08:46:01 2009 0 : Unable to access thread local storage. >> (ARERR 8747) >> Wed Jul 29 08:46:01 2009 WriteWorkflowTraceLog() Wed Jul 29 >> 08:46:01 2009 0 : Unable to access thread local storage. >> (ARERR 8747) >> Wed Jul 29 08:46:01 2009 WriteWorkflowTraceLog() Wed Jul 29 >> 08:46:01 2009 0 : Unable to access thread local storage. >> (ARERR 8747) >> Wed Jul 29 08:46:01 2009 WriteWorkflowTraceLog() _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
