| **
Jamie,
I'm
forwarding this message for someone who tried to respond but is having problems
sending to the ARSList. Hopefully this helps.
Thanks,
Shawn
Pierson
-----Original Message----- **
From: Narsing Metpally [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 11, 2006 1:56 PM To: [email protected] Subject: RE: RPC errors/server crashing We had the issue similar to this where
server crashed every 2 hours because of arserverd process growing more than 2GB
and file descriptors crossing 1024. We contacted remedy support about this issue
and they gave us a a debug patch, it worked fine after
that. We were on Red Hat 2.3 and ARS 6.3 at that
time Thanks, Narsing -----Original Message----- Ok, we're
working with Remedy on this, but I'm hoping the list can give us more insite . .
. We upgraded
1.5 weeks ago from 5.0 to 6.3. We had a few bumps, but things seems ok at
first. Then when our users started fully using the system we started
receiving: AR System
server terminated when a signal/exception was received by the server (ARNOTE
20) The clients
see RPC errors, then eventually malloc and the system has to be restarted.
>From Remedy's recommendations, we increased our descriptors to the max
8192. This has reduced these errors, but they are still occurring every 4
- 6 hours. Our management is breathing down our necks to resolve.
Any ideas???? We are
currently running a script that refreshes every 2 seconds for arserverd cpu
utilization and memory for the next crash. Admin 6.3
patch 18 ARS 6.3
patch 18 Remedy had
me change the Fast & List to Min 4 Max 6. Waiting for the next crash
to see if this had any effect. ANY help
will be GREATLY appreciated!! =) Thanks, CONFIDENTIALITY: The information contained in this
transmission may contain privileged and confidential information. It
is intended only for the use of the person(s) named above. If you
are not the intended recipient, you are hereby notified that any review,
dissemination, distribution or duplication of this communication, and the
information contained in it, is strictly prohibited. If you are not
the intended recipient, please contact the sender and immediately destroy all
copies of the original message. _______________________________________________________________________________
|
Title: Message
- FW: RPC errors/server crashing Pierson, Shawn
- Re: RPC errors/server crashing Blodgett, Jamie
- Re: RPC errors/server crashing McKenzie, James J C-E LCMC HQISEC/L3
- Re: RPC errors/server crashing Webster, Basil

