Thanks Joe for the response, just found the time to look at this again.
- the alert tool is working, but this error in the aralert.log occurs with
every entry of successful (or not) alert being sent.
- arthread.log - no entries
- filter/escalation logs no errors/worflow pointing to oldserver..
ARALERT.LOG
<ALRT> <TID: 0000000772> <RPC ID: 0001451293> <Queue: Admin >
<Client-RPC: 390620 > <USER: Remedy Application Service > /* Fri Apr 20
2012 10:07:57.9129 */Alert Trace Log -- ON (AR Server 7.5.00 Patch 004
201002051027
<ALRT> <TID: 0000001563> <RPC ID: 0001451610> <Queue: Fast >
<Client-RPC: 390620 > <USER: USER2 > /* Fri Apr 20
2012 10:08:38.2992 */Queued alert request for user USER1 at address
MACHINEIP1 on port 48989
<ALRT> <TID: 0000001563> <RPC ID: 0001451610> <Queue: Fast >
<Client-RPC: 390620 > <USER: USER2 > /* Fri Apr 20
2012 10:08:38.2993 */Queued alert request for user USER1 at address
MACHINEIP2 on port 60538
<ALRT> <TID: 0000001049> <RPC ID: 0000000000> <Queue: Alert >
<Client-RPC: 390601 > <USER: AR_NOTIFIER > /* Fri Apr 20
2012 10:08:38.3057 */Alert for user USER1 successfully sent to address
MACHINEIP1 on port 48989 ("MESSAGE")
<ALRT> <TID: 0000001049> <RPC ID: 0000000000> <Queue: Alert >
<Client-RPC: 390601 > <USER: AR_NOTIFIER > /* Fri Apr 20
2012 10:08:38.3077 */Error (68) in binding send socket for address
<OLDSERVERIP:0>
<ALRT> <TID: 0000001049> <RPC ID: 0000000000> <Queue: Alert >
<Client-RPC: 390601 > <USER: AR_NOTIFIER > /* Fri Apr 20
2012 10:08:38.3078 */Pausing for 1 second(s) before attempting connection
retry
<ALRT> <TID: 0000001049> <RPC ID: 0000000000> <Queue: Alert >
<Client-RPC: 390601 > <USER: AR_NOTIFIER > /* Fri Apr 20
2012 10:08:39.3096 */Error (68) in binding send socket for address
<OLDSERVERIP:0>
<ALRT> <TID: 0000001049> <RPC ID: 0000000000> <Queue: Alert >
<Client-RPC: 390601 > <USER: AR_NOTIFIER > /* Fri Apr 20
2012 10:08:39.3097 */Alert for user USER1 not sent to address MACHINEIP2 on
port 60538 ("MESSAGE")
<ALRT> <TID: 0000000772> <RPC ID: 0001452058> <Queue: Admin >
<Client-RPC: 390620 > <USER: Remedy Application Service > /* Fri Apr 20
2012 10:09:14.0397 */Alert Trace Log -- OFF
<END OF LOG FILE>
ARTHEAD.LOG
<THRD> /* Fri Apr 20 2012 10:07:57.9163 */ Thread Trace Log -- ON (AR Server
7.5.00 Patch 004 201002051027)
<THRD> /* Fri Apr 20 2012 10:09:14.0397 */ Thread Trace Log -- OFF
<END OF LOG FILE>
ARFILTER
<FLTR> <TID: 0000002591> <RPC ID: 0001510176> <Queue: Fast >
<Client-RPC: 390620 > <USER: USER >
/* Fri Apr 20 2012 11:39:06.8798 */ <Filter Level:0 Number Of
Filters:297> Checking "FP-SM 750 S Notify Assignee"
<FLTR> <TID: 0000002591> <RPC ID: 0001510176> <Queue: Fast >
<Client-RPC: 390620 > <USER: USER >
0: Notify
<FLTR> <TID: 0000002591> <RPC ID: 0001510176> <Queue: Fast >
<Client-RPC: 390620 > <USER: USER >
Priority:0 Mechanism: Alert To: SUPPORTPERSONEL
<FLTR> <TID: 0000002591> <RPC ID: 0001510176> <Queue: Fast >
<Client-RPC: 390620 > <USER: USER >
"MESSAGE"
<FLTR> <TID: 0000002591> <RPC ID: 0001510176> <Queue: Fast >
<Client-RPC: 390620 > <USER: USER >
/* Fri Apr 20 2012 11:39:06.8813 */ Start filter processing (phase 1) --
Operation - CREATE on Alert Events - <NULL>
<FLTR> <TID: 0000002591> <RPC ID: 0001510176> <Queue: Fast >
<Client-RPC: 390620 > <USER: USER >
/* Fri Apr 20 2012 11:39:06.8813 */ End of filter processing (phase 1)
-- Operation - CREATE on Alert Events - <NULL>
--
View this message in context:
http://ars-action-request-system.1093659.n2.nabble.com/Error-68-in-binding-send-socket-for-address-tp7478905p7484912.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
