> I have committed a fix in CVS head to track down the problem. Could you

> retry with the latest code and provide me with the output?

> You should get something like 'Unable to find remote controller name for

> member ....'

>

 

Ok, i now fully managed to migrate to sequoia 3.0-beta. Here is the output you requested: [Scenario: start 2 controllers, then kill controller 192.168.10.92]

 

 

2006-10-11 09:59:55,900 INFO  continuent.hedera.gms Member(address=test92.dresden.local/192.168.10.92:32796, uid=192.168.10.92:32796) failed in Group(gid=qualiproof-dev)

2006-10-11 09:59:55,902 DEBUG sequoia.controller.recoverylog Storing checkpoint Member(address=test92.dresden.local/192.168.10.92:32796, uid=192.168.10.92:32796) quit group qualiproof-dev-controller-A-20061011095955901+0200 at request id 0

2006-10-11 09:59:55,903 WARN  controller.virtualdatabase.qualiproof-dev Unable to find remote controller name for member Member(address=test92.dresden.local/192.168.10.92:32796, uid=192.168.10.92:32796) in list {Member(address=/192.168.10.92:32796, uid=192.168.10.92:32796)=192.168.10.92:1090, Member(address=/192.168.10.90:32846, uid=192.168.10.90:32846)=192.168.10.90:1090}

2006-10-11 09:59:55,904 DEBUG controller.virtualdatabase.qualiproof-dev Refreshing members list:[Member(address=/192.168.10.90:32846, uid=192.168.10.90:32846)]

2006-10-11 09:59:55,905 INFO  controller.virtualdatabase.qualiproof-dev 0 requests were waiting responses from

2006-10-11 10:00:06,341 DEBUG controller.jmx.AuthenticatingMBeanServer no authentication required

2006-10-11 10:00:06,341 DEBUG controller.jmx.AuthenticatingMBeanServer Authentication with principal was successfull

2006-10-11 10:00:06,342 INFO  controller.virtualdatabase.qualiproof-dev Member(address=/192.168.10.90:32846, uid=192.168.10.90:32846) see members:[Member(address=/192.168.10.90:32846, uid=192.168.10.90:32846)] and has mapping:{Member(address=/192.168.10.92:32796, uid=192.168.10.92:32796)=192.168.10.92:1090, Member(address=/192.168.10.90:32846, uid=192.168.10.90:32846)=192.168.10.90:1090}

 

 

A “show controllers” outputs furthermore:

 

qualiproof-dev is hosted by 2 controller(s):

        192.168.10.92:1090   < -- this controller is dead and should not be seen here anymore

        192.168.10.90:1090 

 

 

 

BTW: if I don’t specify a jdbcIpAdress in my controller settings, sequoia 3.0 defaults always to 0.0.0.0 – meaning it could not automatically identify my real ip-adress (192.168.10.90), isn’t? With sequoia 2.10 there was no such problem ...

 

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to