Actually, if you do the host thing as recommended by J.T. Shyman ( "3. Make sure the hosts file on each server points to the server group host name for its own IP." ) You shouldn't need the server plugin aliases. The host file method, however, is a boxwide fix which may or may not be acceptable depending on your environment. Using plugin aliases keeps you from having to do this. I'd be willing to bet that your servers initially start with the correct configuration and when they try to read the ar.conf file some time later, they may get one from a different server. A different, server is probably getting the ar.conf from the one that has Disable-Escalations: F and then tries to start processing them. The ar.conf is modified as the operations fail from one server to the next.
________________________________ From: Matthew Kunkel Sent: Wednesday, January 02, 2008 9:56 AM To: '[email protected]' Subject: RE: Server Group Error 8745 I spent almost a year going through stuff like this on a Unix server group. We're up and stable now, I just hope it says that way. Although I never experienced the error you mention below, a few things come to mind. Research the Map-IP-Address parameter, it doesn't appear to be set and according to the whitepaper it probably should be. Also look into the server plug-in aliases. I had a problem where each server connected to another server (in a tangled mess) using the ARSYS.ARDBC.CONFIGFILE plug-in. Server A was using server C's ar.conf and C was using B, etc... I'd look into the following plugin aliases since I don't' see them either: Server-Plugin-Alias: AREA AREA myserver-app1 Server-Plugin-Alias: ARSYS.ARDBC.LDAP ARSYS.ARDBC.LDAP myserver-app1 Server-Plugin-Alias: ARSYS.ARDBC.CONFIGFILE ARSYS.ARDBC.CONFIGFILE myserver-app1 Server-Plugin-Alias: ARSYS.ARDBC.REPORT ARSYS.ARDBC.REPORT myserver-app1 Server-Plugin-Alias: ARSYS.ARF.WEBSERVICE ARSYS.ARF.WEBSERVICE myserver-app1 Of course if you're not using the plugins above, then you don't need the alias. -Matt ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of LJ LongWing (Head) Sent: Wednesday, January 02, 2008 9:38 AM To: [email protected] Subject: Re: Server Group Error 8745 ** Ok....I went over this countless times over the weekend and can't figure out what's wrong....here is my ar.cfg file for each server App1: Server-Name: myserver-app Server-Connect-Name: myserver-app1 IP-Name: myserver-app IP-Name: myserver-app1 App2: Server-Name: myserver-app Server-Connect-Name: myserver-app2 IP-Name: myserver-app IP-Name: myserver-app2 According to the Server Group doc, all servers in the group must have the same 'Server-Name'...so they do. The Server-Connect-Name is the value used by the operation ranking form, and must be dns resolvable...which they are. Here is the server group log <SGRP> /* Wed Jan 02 2008 08:33:25.2960 */ Server Group Trace Log -- ON (AR Server 7.1.00 Patch 001 200711161033) <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ The Administration operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ Starting Administration operation <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ The Administration operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ Starting Administration operation <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ The Escalation operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ Starting Escalation operation <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ The Escalation operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ Starting Escalation operation <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ The Archive operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ Starting Archive operation <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ The Archive operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ Starting Archive operation <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ The E-Mail Engine operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.7810 */ Resuming E-Mail Engine operation <SGRP> /* Wed Jan 02 2008 08:33:37.8120 */ The E-Mail Engine operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.8120 */ Resuming E-Mail Engine operation <SGRP> /* Wed Jan 02 2008 08:33:37.8120 */ The Flashboards operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.8120 */ Resuming Flashboards operation <SGRP> /* Wed Jan 02 2008 08:33:37.8120 */ The Flashboards operation is currently owned by server myserver-app1 <SGRP> /* Wed Jan 02 2008 08:33:37.8120 */ Resuming Flashboards operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Server myserver-app1 assuming responsibility for unowned Administration operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Starting Administration operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Server myserver-app1 assuming responsibility for unowned Escalation operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Starting Escalation operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Server myserver-app1 assuming responsibility for unowned Archive operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Starting Archive operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Server myserver-app1 assuming responsibility for unowned E-Mail Engine operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Resuming E-Mail Engine operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Server myserver-app1 assuming responsibility for unowned Flashboards operation <SGRP> /* Wed Jan 02 2008 08:34:36.8290 */ Resuming Flashboards operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Server myserver-app1 assuming responsibility for unowned Administration operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Starting Administration operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Server myserver-app1 assuming responsibility for unowned Escalation operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Starting Escalation operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Server myserver-app1 assuming responsibility for unowned Archive operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Starting Archive operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Server myserver-app1 assuming responsibility for unowned E-Mail Engine operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Resuming E-Mail Engine operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Server myserver-app1 assuming responsibility for unowned Flashboards operation <SGRP> /* Wed Jan 02 2008 08:35:36.8610 */ Resuming Flashboards operation as you see there are two weird things going on...it seems to be doing each operation twice....and for that matter...each time I add the server back into the group it creates two records in the ranking form for each server....any ideas???? ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shyman, Jonathan Sent: Friday, December 28, 2007 12:54 PM To: [email protected] Subject: Re: Server Group Error 8745 ** Something may not have been set right when this server was originally added to the server group. It may be possible to track down what if you can compare the settings in ar.conf and in Remedy Administrator on both servers. If that fails to turn up anything a next step might be to remove the primary server from the server group and then add it back. I'm not sure what impact that may have on operations when you do it or if you'd have to stop/restart all the server group servers to make the change. J.T. Shyman Column Technologies [EMAIL PROTECTED] ________________________________ From: LJ LongWing (Head) Sent: Fri 12/28/2007 2:48 PM To: [email protected] Subject: Re: Server Group Error 8745 ** Ok...here is something Odd...the Primary server (the one having the issues with the escalation Queue says this on startup) <SGRP> /* Fri Dec 28 2007 12:02:49.7240 */ The Administration operation is currently owned by server <ThisServer> <SGRP> /* Fri Dec 28 2007 12:02:49.7240 */ Starting Administration operation then 30 seconds later, and every thirty seconds it gives this message...for each operation that it is an owner for <SGRP> /* Fri Dec 28 2007 12:03:18.6640 */ Server <ThisServer> assuming responsibility for unowned Administration operation <SGRP> /* Fri Dec 28 2007 12:03:18.6640 */ Starting Administration operation which tells me that server1 in this group isn't recognizing itself? ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shyman, Jonathan Sent: Friday, December 28, 2007 11:38 AM To: [email protected] Subject: Re: Server Group Error 8745 ** Yes, what he said. Thanks, Joe. Good point. J.T. Shyman Column Technologies [EMAIL PROTECTED] ________________________________ From: Joe D'Souza Sent: Fri 12/28/2007 1:34 PM To: [email protected] Subject: Re: Server Group Error 8745 ** Also turn on the server group logs on all the servers belonging to the server group.. If there is a communication problem between the servers in the server group, it will show on these logs... Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of Shyman, Jonathan Sent: Friday, December 28, 2007 1:29 PM To: [email protected] Subject: Re: Server Group Error 8745 ** Since this seems to be occurring during server group communication I would wonder if the two servers can talk to each other. If these servers are in fact in a servergroup, here's what I'd do to start troubleshooting: 1. Make sure each server in the group can ping each other server both by short name and my fully-qualified domain name (FQDN) 2. Make sure each server in the group can ping the server group host name. I'm assuming you are using a hardware load-balancer of some kind to do this and that it has its own name and IP address 3. Make sure the hosts file on each server points to the server group host name for its own IP. J.T. Shyman Column Technologies [EMAIL PROTECTED] ________________________________ From: LJ LongWing (Head) Sent: Fri 12/28/2007 1:24 PM To: [email protected] Subject: Re: Server Group Error 8745 ** The first restart today was by complete reboot of the server...so no possibility of a thread not shutting down...and it started happening as you can see almost exactly an hour afterwards. Then the second you see is just a restart of the service, and again, an hour before throwing the error again...so I don't think it's a thread issue. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Joe D'Souza Sent: Friday, December 28, 2007 11:12 AM To: [email protected] Subject: Re: Server Group Error 8745 ** This is probably because the escalation thread that was created previously has not been killed gracefully after the server was brought down. After stopping the services could you check to see if the Escalation RPC is still in use by an rpcinfo -all? Joe -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] Behalf Of LJ LongWing (Head) Sent: Friday, December 28, 2007 12:58 PM To: [email protected] Subject: Re: Server Group Error 8745 ** Found some more information about this....this appears to begin almost exactly 1 hour after I restart the server Fri Dec 28 07:06:46 2007 : Action Request System(R) Server Version 7.1.00 Patch 001 200711161033 (c) Copyright 1991-2007 BMC Software, Inc. Fri Dec 28 08:06:58 2007 ServerGroup : Unable to create a queue to process RPC requests. (ARERR 8745) Fri Dec 28 08:06:58 2007 CreateEscalationQueue Fri Dec 28 09:51:10 2007 : Action Request System(R) Server Version 7.1.00 Patch 001 200711161033 (c) Copyright 1991-2007 BMC Software, Inc. Fri Dec 28 10:51:00 2007 ServerGroup : Unable to create a queue to process RPC requests. (ARERR 8745) Fri Dec 28 10:51:00 2007 CreateEscalationQueue Any suggestions yet? ________________________________ From: LJ LongWing (Head) [mailto:[EMAIL PROTECTED] Sent: Friday, December 28, 2007 7:04 AM To: [email protected] Subject: Server Group Error 8745 Recently stood up my first server group and one of them is giving the following error Fri Dec 28 06:54:10 2007 ServerGroup : Unable to create a queue to process RPC requests. (ARERR 8745) Fri Dec 28 06:54:10 2007 CreateEscalationQueue Strange part is I can't find this error in the documentation, not in the Error guide, or any of the other docs...can't find any reference to it anywhere....not on Google, nor list archives...any suggestions? ARS 7.1 Win2k3 __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ ----------------------------------------- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the individual or entity to whom they are addressed. If you have received this email in error destroy it immediately. ********************************************************************** Wal-Mart Confidential ********************************************************************** _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
