On Thu, Nov 26, 2009 at 02:24:47PM -0500, Ian B. MacDonald wrote:
> I am a Ubuntu Karmic barry user using Martin Owens sources
>
> ii libbarry0
> 0.16-2009111858-0git1
>
> My sync script is:
> #!/bin/sh
> evolution --force-shutdown
> msynctool --sync EvoBarry --filter-objtype note --filter-objtype todo
>
> Things have been smooth for a while, so I only backup monthlyish now.
Hi Ian,
Thanks for your detailed report.
> Sent an entry pas-id-4B0D658B0000002D of size 2564 to member 2
> (barry-sync). Changetype ADDED
>
> The result is no error on console, but the process just sits there.. an
> immediate boost in CPU and continued memory consumption is noted, with
> osplugin consuming 100%+ of one CPU core and growing in memory use.
>
> I have no choice but to CTRL-C 30 minutes later..or a day later
I'm afraid that this is likely an opensync issue, and not an issue
with the one record itself.
I'm not certain, but sometimes it seems that opensync goes into this
nearly exponential busy loop to solve conflicts. With a limited number
of records, this busy loop does eventually finish, but with 600...
I don't know how long it might take.
In my exerience, it is often due to the case where there are new records
on both sides of the sync. (more below)
> Step 1, I'd like to experiment with removing this contact, and
> continuing.. but I am not sure how to find out which contact it is. For
> now I am going to go have a look in .evolution with a text editor...
I don't think this will help, just to focus on the one record.
But it's probably worth a try.
I would enable opensync debug tracing (set the OSYNC_TRACE environment
variable to the name of an empty directory) and then while it's
in the busy loop, grep the trace logs. The data of the record should
be in the logs.
> Step 2, whats the preferred method for additional verbose debugging to
> support further dialogue and/or a change/patch to deal with this
> issue.
Opensync tracing. But the logs are generally too big to be of practical
use, with tons of data.
> Feature Note: barrybackup should have a purge Addressbook feature, as it
> doesn't save the address book on backup if there are no contacts, so
> there is no easy way to restore an empty addressboook if you create a
> backup after a fresh Blackberry firmware update (which I had). The
> method I have to use is to create, and have ready for restore, a backup
> with only one entry, and then go and delete it on the Blackberry itself
> to get to this empty address book stage.
This would be a good feature.
Fortunately, you can trick the command line btool into erasing your
database for you. If you try to save a database from a non-existent
file, it will erase the database you specify. For example:
btool -s "Address Book" -f /tmp/doesnotexist
This should be made into a legitimate feature though.
The good news, is that if you sync like this, you may find that just
removing that one record may solve your sync problems, since now it
is just a sync in one direction, and opensync doesn't have to do any
conflict checking.
- Chris
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
