Hi Nuno,
Yes I do see messages, were they leave, like this:
2007-05-23 10:26:41,264 WARN Member(address=/xxx.234.68.194:32862,
uid=xxx.234.68.194:32862) has left distributed virtual database
test_big_13_C
2007-05-23 10:26:42,076 WARN Member(address=/xxx.234.68.194:32812,
uid=xxx.234.68.194:32812) has left distributed virtual database
test_big_6_C
2007-05-23 10:26:42,131 WARN Member(address=/xxx.234.68.194:32911,
uid=xxx.234.68.194:32911) has left distributed virtual database
test_big_20_C
2007-05-23 10:26:42,158 WARN Member(address=/xxx.234.68.194:32833,
uid=xxx.234.68.194:32833) has left distributed virtual database
test_big_9_C
2007-05-23 10:26:42,189 WARN Member(address=/xxx.234.68.194:32855,
uid=xxx.234.68.194:32855) has left distributed virtual database
test_big_12_C
2007-05-23 10:26:42,288 WARN Member(address=/xxx.234.68.194:32826,
uid=xxx.234.68.194:32826) has left distributed virtual database
test_big_8_C
2007-05-23 10:26:47,309 WARN Member(address=/xxx.234.68.194:32819,
uid=xxx.234.68.194:32819) has left distributed virtual database
test_big_7_C
2007-05-23 10:26:53,499 WARN Member(address=/xxx.234.68.194:32869,
uid=xxx.234.68.194:32869) has left distributed virtual database
test_big_14_C
2007-05-23 10:26:54,367 WARN Member(address=/xxx.234.68.194:32805,
uid=xxx.234.68.194:32805) has left distributed virtual database
test_big_5_C
2007-05-23 10:26:54,675 WARN Member(address=/xxx.234.68.194:32940,
uid=xxx.234.68.194:32940) has left distributed virtual database
test_big_25_C
2007-05-23 10:27:03,370 WARN Member(address=/xxx.234.68.194:32933,
uid=xxx.234.68.194:32933) has left distributed virtual database
test_big_24_C
2007-05-23 10:27:03,399 WARN Member(address=/xxx.234.68.194:32848,
uid=xxx.234.68.194:32848) has left distributed virtual database
test_big_11_C
2007-05-23 10:27:26,651 INFO Database backend
test_big_50_Bbeqv377w is
now in state disabling
2007-05-23 10:27:26,658 INFO Database backend
test_big_50_Bbeqv377w is
now in state disabled
2007-05-23 10:29:23,343 INFO Database backend
test_big_50_Bbeqv377w is
now in state backing up
2007-05-23 10:29:37,408 INFO Database backend
test_big_50_Bbeqv377w is
now in state disabled
2007-05-23 10:29:37,414 INFO Database backend
test_big_50_Bbeqv377w is
now in state replaying
2007-05-23 10:31:15,518 INFO Database backend
test_big_50_Bbeqv377w is
now in state write-only enabled
2007-05-23 10:31:15,527 INFO Database backend
test_big_50_Bbeqv377w is
now in state enabled
2007-05-23 10:34:25,071 WARN Member(address=/xxx.234.68.194:32784,
uid=xxx.234.68.194:32784) has left distributed virtual database
test_big_2_C
2007-05-23 10:34:48,960 WARN Member(address=/xxx.234.68.194:32904,
uid=xxx.234.68.194:32904) has left distributed virtual database
test_big_19_C
2007-05-23 10:34:58,793 WARN Member(address=/xxx.234.68.194:32890,
uid=xxx.234.68.194:32890) has left distributed virtual database
test_big_17_C
2007-05-23 10:35:04,500 WARN Member(address=/xxx.234.68.194:32776,
uid=xxx.234.68.194:32776) has left distributed virtual database
test_big_0_C
2007-05-23 10:35:06,168 WARN Member(address=/xxx.234.68.194:32883,
uid=xxx..234.68.194:32883) has left distributed virtual database
test_big_16_C
2007-05-23 10:35:06,651 WARN Member(address=/xxx.234.68.194:32798,
uid=xxx.234.68.194:32798) has left distributed virtual database
test_big_4_C
2007-05-23 10:35:16,010 WARN Member(address=/xxx.234.68.194:32840,
uid=xxx.234.68.194:32840) has left distributed virtual database
test_big_10_C
2007-05-23 10:35:16,201 WARN Member(address=/xxx.234.68.194:32876,
uid=xxx.234.68.194:32876) has left distributed virtual database
test_big_15_C
2007-05-23 10:35:20,257 WARN Member(address=/xxx.234.68.194:32924,
uid=xxx.234.68.194:32924) has left distributed virtual database
test_big_21_C
2007-05-23 10:35:20,459 WARN Member(address=/xxx.234.68.194:32791,
uid=xxx.234.68.194:32791) has left distributed virtual database
test_big_3_C
2007-05-23 10:36:46,531 INFO Virtual database test_big_50_C
successfully
backuped database backend test_big_50_Bbeqv377w with dump name
init_dump_test_big_50_C
2007-05-23 10:36:46,543 INFO Dump init_dump_test_big_50_C for virtual
database test_big_50_C is being transferred on remote controller
xxx.234.68.194:1090
2007-05-23 10:36:46,565 ERROR Failed to transfer dump
init_dump_test_big_50_C for virtual database test_big_50_C (because
of :
Cannot find controller xxx.234.68.194:1090 in group)
2007-05-23 11:26:14,165 WARN Member(address=/xxx.234.68.194:32897,
uid=xxx.234.68.194:32897) has left distributed virtual database
test_big_18_C
Which type of hedera logging do you mean? My setting at the moment
is as
follows:
# Hedera channels test #
log4j.logger.test.org.continuent.hedera.channel=INFO, Console,
Filetrace
log4j.additivity.test.org.continuent.hedera.channel=false
# Hedera adapters #
log4j.logger.org.continuent.hedera.adapters=INFO, Console, Filetrace
log4j.additivity.org.continuent.hedera.adapters=false
# Hedera factories #
log4j.logger.org.continuent.hedera.factory=INFO, Console, Filetrace
log4j.additivity.org.continuent.hedera.factory=false
# Hedera channels #
log4j.logger.org.continuent.hedera.channel=DEBUG, Console, Filetrace
log4j.additivity.org.continuent.hedera.channel=false
# Hedera Group Membership Service #
log4j.logger.org.continuent.hedera.gms=DEBUG, Console, Filetrace
log4j.additivity.org.continuent.hedera.gms=false
Best regards,
Malte
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
