Is the following logs normal for running in a cluster: 09:14:24,006 INFO controller.RequestManager.iasipaiddb Resuming activity for iasipaiddb09:14:24,048 WARN jgroups.protocols.UDP discarded message from different group "iasipaiddb" (our group is "iasdsydb"). Sender was 10.99.9.229:3314509:14:24,090 WARN jgroups.protocols.UDP discarded message from different group "iasipaiddb" (our group is "iasdsydb"). Sender was 10.99.9.229:3314509:14:24,121 INFO controller.RequestManager.iasipaiddb All activity is now resumed for iasipaiddb09:14:24,122 INFO controller.recoverylog.RecoverThread Database backend DB1 is now enabled09:14:24,495 WARN jgroups.protocols.UDP discarded message from different group "iasipaiddb" (our group is "iasdsydb"). Sender was 10.99.9.229:3314509:14:27,754 WARN jgroups.protocols.UDP discarded message from different group "iasdsydb" (our group is "iasipaiddb"). Sender was 10.99.9.229:3314309:14:28,757 WARN jgroups.protocols.UDP discarded message from different group "iasdsydb" (our group is "iasipaiddb"). Sender was 10.99.9.229:3314309:14:32,464 WARN jgroups.protocols.UDP discarded message from different group "iasipaiddb" (our group is "iasdsydb"). Sender was 10.99.9.229:3314509:14:33,466 WARN jgroups.protocols.UDP discarded message from different group "iasipaiddb" (our group is "iasdsydb"). Sender was 10.99.9.229:3314509:14:35,115 WARN jgroups.protocols.UDP discarded message from different group "iasdsydb" (our group is "iasipaiddb"). Sender was 10.99.9.229:3314309:14:36,118 WARN jgroups.protocols.UDP discarded message from different group "iasdsydb" (our group is "iasipaiddb"). Sender was 10.99.9.229:3314309:14:41,887 WARN jgroups.protocols.UDP discarded message from different group "DefaultPartition" (our group is "iasipaiddb"). Sender was 127.0.0.1:3277109:14:41,889 WARN jgroups.protocols.UDP discarded message from different group "DefaultPartition" (our group is "iasdsydb"). Sender was 127.0.0.1:3277109:14:42,013 WARN jgroups.protocols.UDP discarded message from different group "iasipaiddb" (our group is "iasdsydb"). Sender was 10.99.9.229:3314509:14:42,895 WARN jgroups.protocols.UDP discarded message from different group "DefaultPartition" (our group is "iasipaiddb"). Sender was 127.0.0.1:3277109:14:42,896 WARN jgroups.protocols.UDP discarded message from different group "DefaultPartition" (our group is "iasdsydb"). Sender was 127.0.0.1:3277109:14:43,018 WARN jgroups.protocols.UDP discarded message from different group "iasipaiddb" (our group is "iasdsydb"). Sender was 10.99.9.229:3314509:14:44,138 WARN jgroups.protocols.UDP discarded message from different group "DefaultPartition" (our group is "iasipaiddb"). Sender was 127.0.0.1:3277109:14:44,139 WARN jgroups.protocols.UDP discarded message from different group "DefaultPartition" (our group is "iasdsydb"). Sender was 127.0.0.1:3277109:14:44,257 WARN jgroups.protocols.UDP discarded message from different group "DefaultPartition" (our group is "iasdsydb"). Sender was 127.0.0.1:3277109:14:44,263 WARN jgroups.protocols.UDP discarded message from different group "DefaultPartition" (our group is "iasipaiddb"). Sender was 127.0.0.1:32771 It is really annoying as its filling my logs and potentially hiding something I care about. Or does the above mean something is wrong. As the moment I just have the one controller running.
From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Mon, 7 Jul 2008 13:41:56 -0700Subject: Re: [Sequoia] DB failover does not seem to be working Hi Adam, You need to restore the backup on the second controller. The general flow is as follows: 1.) Initialize first backend. 2.) Dump backend contents. This creates a dump with an associated checkpoint. You can enable the backend at this time. 3.) Transfer log and dump to second controller. This gets the controllers syncrhonized. 4.) Load the dump on the second backend. 5.) Enable the second backend. At this point your cluster is up and running. Cheers, RobertOn 7/7/08 12:27 PM, "Adam Purkiss" <[EMAIL PROTECTED]> wrote: That was the reason it did not start up. I will see if this fixes things Can I confirm that if I use this then when I restore backend DB1 on controller 1 do I need to restore the same backup on controller 2 or do I just enable it.From: [EMAIL PROTECTED]: [EMAIL PROTECTED]: Mon, 7 Jul 2008 11:54:09 -0700Subject: Re: [Sequoia] DB failover does not seem to be workingHi Adam, Can you check your hedera.properties file and look at the JGroups config file name? If it is sequencer.xml, you have just hit a configuration problem that is logged as sequoia-1102, which is fixed in the codeline. The problem is that the jgroups-all.jar file also contains a sequencer.xml file with a bad IP address. It picks this up before the Sequoia version. To correct the problem, rename config/sequencer.xml to config/sequoia_sequencer.xml and adjust the name accordingly in the Hedera properties file referenced by your virtual database. Thanks, Robert-- Robert Hodges, CTO, Continuent, Inc.Email: [EMAIL PROTECTED]: +1-510-501-3728 Skype: hodgesrm _________________________________________________________________
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
