We were seeing the same error in our recon logs. Once we switched to the proper 
RPC port - 390698, we have been running fine. -- Shyam




________________________________
From: Thad K Esser <[email protected]>
To: [email protected]
Sent: Thu, December 17, 2009 11:00:43 AM
Subject: Re: RPC Port for reconciliation engine - ARERR[120133]

** 
Hi, 

One additional question:  Does
anyone else out there have their reconciliation engine using queues 390698
or 390699? 

Thanks,
Thad Esser
Remedy Developer 



From:  Thad K Esser <[email protected]>  
To:  [email protected]  
Date:  12/16/2009 01:04 PM  
Subject:  RPC Port for reconciliation engine -
ARERR[120133]  
Sent by:  "Action Request System discussion
list(ARSList)" <[email protected]> 
________________________________
 


** 
While investigating some errors in my arrecond.log, I ran across the KB
article below.  Having just gone through re-organizing my queues/threads,
it sure would have been nice to know this ahead of time.

Anyway, is my assumption correct that until I put the reconciliation engine
on 390698 or 390699, it will use the fast/list queues?
(I'm on CMDB 2.1 patch 4)
AIX 5.3
ARS 7.1

Thanks,
Thad Esser
Remedy Developer 

===============
http://rkm.bmc.com/rkm/viewdoc.jsp?remedy=1&doc=17151&sid=4000891&type=Published&terms=searchTerms&user=SelfHelp

Details
Self Help Document  
ID: 17151 
Type: Problem Solution 

Problem
Customer was getting warning message in arrecond.log file. This was filling
up arrecond as it was coming for every minute.

[2008/04/17 14:44:57.1050] [WARNING] [TID: 0000004648]  : Ignoring
following error for Reconciliation (The specified RE RPC port) and proceeding
further
[2008/04/17 14:44:57.1050] [WARNING] [TID: 0000004648]  :    
ARERR[120133] The CMDB RPC port specified is invalid.
[2008/04/17 14:44:57.1050] [WARNING] [TID: 0000004648]  :    
390622

Product
CMDB 2.1, ARS 7.1
Environment
Windows/Unix, CMDB 2.1, ARS 7.1

Solution
Customer was using 390622 port for Reconciliation performance.

Please use 390698 or 390699 port from CMDB 2.1 Patch 002 onwards as this
has been hard-coded in system. RFE and Defect for documentation already
submitted for this problem. We should not use any other port after above
release.
=============== 
*IMPORTANT NOTICE: This communication, including any attachment,
contains information that may be confidential or privileged, and is intended
solely for the entity or individual to whom it is addressed. If you are
not the intended recipient, you should delete this message and are hereby
notified that any disclosure, copying, or distribution of this message
is strictly prohibited. Nothing in this email, including any attachment,
is intended to be a legally binding signature. *  
_Platinum Sponsor: [email protected] ARSlist: "Where
the Answers Are"_  
*IMPORTANT NOTICE: This communication, including any attachment, contains 
information that may be confidential or privileged, and is intended solely for 
the entity or individual to whom it is addressed.  If you are not the intended 
recipient, you should delete this message and are hereby notified that any 
disclosure, copying, or distribution of this message is strictly prohibited.  
Nothing in this email, including any attachment, is intended to be a legally 
binding signature.
* 
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ 

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to