Re: Sync Terminated Abnormally

Simon Brereton <[email protected]>
Newsgroups gmane.comp.horde.sync
Message-ID <8AEF1088F84EE440A3004F96F838014E0DE737AC@DADAEXCCR.dadaexchange.local>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Jan Schneider
> Sent: Thursday, November 05, 2009 3:46 AM


> > So, it's a birthday for a contact in my phonebook, but all the other
> > contacts seem to be fine, so what's wrong with this one?  What do
> > you need to help me diagnose this?
> 
> A contact birthday in the events table? That's interesting. If your
> phone is really synching its contacts with the remote calendar, then
> it should use different UIDs for synchings with the calendar and the
> address book.
> As you already found out, we have a mapping table that maps the UIDs
> on the device with the UIDs in Horde. This is a 1-to-1-mapping. So, if
> the device decides to use the same UID for two different objects
> (which, ironically, no longer makes it a UID), on the object would fail.
> If this is really the case, then I consider this device pretty broken.

Jan - apologies for the delayed response - life gets in the way some times.   I was being unclear.   When I add birthdays to my contacts on the SE, it automatically asks if I want to add it to the calendar and set a reminder, etc.  I checked on the device and it all seemed to be fine.  This morning, I decided to check on the calendar in Horde and I noticed the reminder was set to be 899 minutes prior to the event.  I deleted the event totally from the phone and set it up in the calendar as it should be and then did a sync and it now seems to be all working.


> >> > Also, it would be nice to be able to sync the Bookmarks - the phone
> >> > supports this DB, but Horde doesn't seem to (yet)..
> >>
> >> You don't even have a Horde bookmark application installed, where
> >> should those bookmarks be synched? Beside that, we don't support
> >> synchronization with our bookmark application yet anyway, see
> >> http://bugs.horde.org/ticket/7250
> >
> > I thought I had it installed.  Sorry.  I'll install it today.  Good
> > to see it's on the wishlist though.  Since I'm not using CVS, is
> > there a way to install this?  I don't see a tar.gz to download.
> 
> http://snaps.horde.org/

I presume I have to download the HEAD and FRAMEWORK passages.  Is there a mini-howto on how to install from snaps?

> >> > Finally, on an unrelated issue there is also this in the log every
> 5
> >> > minutes, but I can't find anything on google about it - I don't
> >> > believe it's related, but if you can point me in the right
> direction
> >> > to fix, that would be great.
> >> >
> >> > Oct 30 21:00:01 HORDE [error] [kronolith] Required "horde_base" not
> >> > specified in VFS configuration. [pid 19373 on line 77 of
> >> > "/usr/share/horde3/lib/Horde/Scheduler.php"]
> >>
> >> You didn't set up a VFS backend in your Horde configuration, which is
> >> necessary for the scheduler script.
> >
> > I thought I'd done that.  Sorry.  After doing that, the message
> > disappears from my logs but logging into dimp causes this error.
> >
> > Catchable fatal error: Object of class PEAR_Error could not be
> > converted to string in /usr/share/horde3/lib/Horde.php on line 783
> >
> > I have not been able to troubleshoot this at all.

I'm still having this error - > > Catchable fatal error: Object of class PEAR_Error could not be converted to string in /usr/share/horde3/lib/Horde.php on line 783

The relevant code is about testing for webroots - I don't understand how implementing the VFS would have broken this.  I've googled - but the only page linked was my previous post.  Please can you help.

Thanks.

Simon



-- 
sync mailing list - Join the hunt: http://horde.org/bounties/#sync
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.