Maybe in your case it is some workflow that got the same kind of corruption?
At the time that your server crashes, does the server process grows indefinitely till it can grow no more and then crash? That is what I used to experience. And during this process it would fill up the C:\Temp folder with a file that would grow as long as the server was up and stop growing when the arserver process crashed. I had to manually delete the file that got created in the temp directory to release the space it occupied before restarting the server. You may want to check your /tmp folder to see if there are files owned by the user starting the arserverd process, that are significantly large, created at the time you performed an action that caused the process to crash.. Delete all such files.. But yes you may want to get a debug build of the AR Server to debug the server at the time the process crashes. The debug file generated will be pretty large so make sure you have enough space in your apps volumn as this file will be created in the bin directory of the server installation. Joe ________________________________ From: "[email protected]" <[email protected]> To: [email protected] Sent: Monday, July 20, 2009 1:19:06 PM Subject: Re: Saving form entry crashes server Thanks again, Joe. I tried adding and deleting a field to and from both forms, but it didn’t change the situation. So I guess I’ll try Remedy support. Dwayne From:Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe DeSouza Sent: Monday, July 20, 2009 1:08 PM To: [email protected] Subject: Re: Saving form entry crashes server ** Martin, I had something similar like this happen to me on one of my Windows server. This only happened when a database was restored from another server that was running on an AIX environment in our case to a temporary development server on Windows. We had to debug the arserver process, and send the results to Remedy and they found that some of our form definitions were bad, and these were the forms that would crash the server when certain actions (mostly a search be it during a search or a save or whatever) were performed on them. Fortunately what fixed those forms was opening the form in the Admin tool, and saving them by creating a temp field and deleting it. You may need to open a ticket with Remedy and get their help to debug your arserver process at the time it crashes. Joe ________________________________ From:"[email protected]" <[email protected]> To: [email protected] Sent: Monday, July 20, 2009 1:00:15 PM Subject: Re: Saving form entry crashes server Thanks, Joe. Our system admin assures me that we have lots of space. If I do “df –k” the highest percentage is 36% Dwayne From:Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Joe DeSouza Sent: Monday, July 20, 2009 12:56 PM To: [email protected] Subject: Re: Saving form entry crashes server ** Are you running out of space in the /tmp volumn? What are your results of df -k Joe ________________________________ From:"[email protected]" <[email protected]> To: [email protected] Sent: Monday, July 20, 2009 12:47:15 PM Subject: Saving form entry crashes server ** Dear List, We have a form (IT:Request) that we have been using for years with no problem. Now all-uva-sudden whenever we save certain entries we get: ARERR [90] Cannot establish a network connection to the AR System server : rem1 : RPC: Miscellaneous tli error - System error (Connection refused) And we get a core dump and the system is unavailable for about 30 seconds. There are no errors in sql, filter or api logs. arerror.log simply repeats the above message. The api log says: ARSetServerInfo -- as user Remedy Application Service from Unidentified Client (protocol 13) at IP address 134.126.10.192 (ip of local server) but it says that on both entries that do and don’t crash the server. Even when the saves crash the system, they do take affect, and are displayed once the system comes back up. The entries that crash the server have one thing in common, there is a subfile IT:Review. I can take an entry that does not crash the server, add an associated IT:Review entry, and it will crash the server if I try to save it. But there is nothing wrong with IT:Review. I can display and modify its entries just fine. Nor can I see anything wrong with the IT:Request table displaying the IT:Review entries, and anyway, it has been sitting there unchanged for years. I am totally stumped. Does anyone have any suggestions? (ARS 7.1 p3, RH Linux server, Oracle 10.2 db) Dwayne Martin James Madison University _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
