Yeah I'm doing that today, will update you. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emmanuel Cecchet Sent: Monday, April 28, 2008 8:57 AM To: Sequoia general mailing list Subject: Re: [Sequoia] Hello Again
Did you try to set the logger to DEBUG like I mentioned earlier on to get more information about the problem? Emmanuel Jonathan Poole wrote: > Any workaround? Is there something we can adjust in the code level to > get around this? > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Emmanuel Cecchet > Sent: Monday, April 28, 2008 8:40 AM > To: Sequoia general mailing list > Subject: Re: [Sequoia] Hello Again > > Jonathan, > > 2.10.10 would be much better unfortunately there is no release yet of > this version. According to Robert, this is their next thing on their > todo list but they are also working on their new asynchronous > replication project so I don't know when that is really going to happen. > > We probably need to find an alternative way of doing releases otherwise > we will never get that thing out! > > Sorry about that but there is not much I can do at the moment unless I > start doing my own releases which is not really part of my plans for > now. > > All suggestions are welcome, > Emmanuel > > >> sequoia-2.10.9-bin is the version I'm using. Is there a different >> version I'm to be running? >> >> -----Original Message----- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Emmanuel Cecchet >> Sent: Friday, April 25, 2008 3:25 PM >> To: Sequoia general mailing list >> Subject: Re: [Sequoia] Hello Again >> >> Hi Jonathan, >> >> >>> 2008-04-25 14:18:07,605 ERROR sequoia.controller.recoverylog Recovery >>> > > >>> log was unable to update request completion status: >>> [EMAIL PROTECTED] >>> <mailto:[EMAIL PROTECTED]>: UPDATE logtable >>> SET exec_status='F',update_count=0,exec_time=0 WHERE log_id=-1 >>> >>> >>> >> Do you have more information about the exception that caused the >> > error? > >> If you don't get more information, try to set the recovery log logger >> (in log4j.properties) to DEBUG. >> >> >>> How do I resolve this recovery log issue? >>> >>> >>> >> Just to be sure, you are using Sequoia 2.10.9? >> It might be a problem with exec_status column type. >> >> Keep us posted as soon as you have more details. >> Thanks, >> Emmanuel >> _______________________________________________ >> >> _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia This e-mail message is confidential, may be privileged and is intended for the exclusive use of the addressee. Any other person is strictly prohibited from disclosing, distributing or reproducing it. If the addressee cannot be reached or is unknown to you, please inform us immediately and delete this e-mail message and destroy all copies. Thank you. _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
