Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 1 subscriber
  • Views 9583 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Relay server encounter error "Caught CORBA system exception"

Azwan

Hi All,

Based on subject above does anyone successfully resolved this issue?, currently I'm encounter few relay server which didn't appear connected at SEC even after service has been restarted. Thanks

RMS Logs

RMS logs

22.08.2012 12:00:19 055C I Getting parent router IOR from 172.16.116.169:8192
22.08.2012 12:00:20 055C I Received parent router's IOR:
IOR:010000002600000049444c3a536f70686f734d6573736167696e672f4d657373616765526f757465723a312e300000000100000000000000a4000000010102000f0000003137322e31362e3131362e3136390000012000004100000014010f004e5550000000210000000001000000526f6f74504f4100526f7574657250657273697374656e740003000000010000004d657373616765526f7574657200000003000000000000000800000001005200004f41540100000014000000010052000100010000000000090101000000000014000000080000000100a60086000220
22.08.2012 12:00:20 055C I Successfully validated parent router's IOR
22.08.2012 12:00:20 055C I Accessing parent
22.08.2012 12:02:01 055C E ParentLogon::RegisterParent: Caught CORBA system exception, ID 'IDL:omg.org/CORBA/TRANSIENT:1.0'
OMG minor code (2), described as '*unknown description*', completed = NO

Telnet Result from Relay Server

IOR:010000002600000049444c3a536f70686f734d6573736167696e672f4d657373616765526f75
7465723a312e300000000100000000000000a4000000010102000f0000003137322e31362e313136
2e3136390000012000004100000014010f004e5550000000210000000001000000526f6f74504f41
00526f7574657250657273697374656e740003000000010000004d657373616765526f7574657200
000003000000000000000800000001005200004f4154010000001400000001005200010001000000
0000090101000000000014000000080000000100a60086000220

Telnet Result from Parent Server

IOR:010000002600000049444c3a536f70686f734d6573736167696e672f4d657373616765526f75
7465723a312e300000000100000000000000a0000000010102000d0000003137322e39362e382e31
3531000001204100000014010f004e5550000000210000000001000000526f6f74504f4100526f75
74657250657273697374656e740003000000010000004d657373616765526f757465720000000300
0000000000000800000001b2ee00004f4154010000001400000001b2ee0001000100000000000901
010000000000140000000800000001b2a60086000220

:28685


This thread was automatically locked due to age.
Parents
  • 0

    Hello Azwan,

    I'm not sure which direction is Telnet Result from Relay Server: Is this the result of telnet parent 8192 run on the Relay? Or the other direction? If the former then the relay should have the address 172.96.8.151 and the server 172.16.116.169, correct?

    Anyway, the log probably doesn't stop there so please post some of the following lines. Also - do the failing relays have something in common?

    Christian

    :28691
Reply
  • 0

    Hello Azwan,

    I'm not sure which direction is Telnet Result from Relay Server: Is this the result of telnet parent 8192 run on the Relay? Or the other direction? If the former then the relay should have the address 172.96.8.151 and the server 172.16.116.169, correct?

    Anyway, the log probably doesn't stop there so please post some of the following lines. Also - do the failing relays have something in common?

    Christian

    :28691
Children
No Data