[horde] Activesync setup on Android

[Simon Brereton]

> -----Original Message-----
> From: Jon Spriggs [mailto:jon at sprig.gs]
> On 22 September 2011 23:06, Simon Brereton
> <simon.brereton at buongiorno.com> wrote:
> >> -----Original Message-----
> >> From: horde-bounces at lists.horde.org [mailto:horde-
> >> bounces at lists.horde.org] On Behalf Of Michael J Rubinsky Quoting
> >> Simon Brereton
> >>
> >> > Hi
> >> >
> >> > Probably I'm doing something stupid - and I know the wiki says
> it's
> >> > impossible to give a howto for every Android device, but I'm
> have
> >> an
> >> > issue setting up Activesync on Android.
> >> >
> >> > I get this when accessing the page with the browser - which I
> >> assume
> >> > is correct:
> >> >
> >> > A fatal error has occurred
> >> > Horde_Log_Handler_Stream: "" cannot be opened with mode "a+"
> >> > Details have been logged for the administrator.
> >>
> >> Why would you assume this is correct? It's not. Looks like
> something
> >> with your logging is not configured correctly.
> >
> > Well, I get a different result if I use the Administrator login -
> about 159.72 KB of debug output starting like:
> >
> >
> > A fatal error has occurred
> > Horde_Log_Handler_Stream: "" cannot be opened with mode "a+"
> >
> > 1. Horde_Injector->getInstance() /usr/share/horde4/rpc.php:96 2.
> > Horde_Injector->createInstance()
> /usr/share/php/Horde/Injector.php:248
> > 3. Horde_Injector_Binder_Factory->create()
> > /usr/share/php/Horde/Injector.php:213
> > 4. Horde_Core_Factory_ActiveSyncBackend->create()
> > /usr/share/php/Horde/Injector/Binder/Factory.php:111
> > 5. Horde_Log_Handler_Stream->__construct()
> > /usr/share/php/Horde/Core/Factory/ActiveSyncBackend.php:16
> > 6. Horde_Log_Handler_Stream->__wakeup()
> > /usr/share/php/Horde/Log/Handler/Stream.php:86
> >
> > Details
> > The full error message is logged in Horde's log file, and is shown
> below only to administrators. Non-administrative users will not see
> error details.
> >
> > But you're right - as I mentioned, nothing is being put into the
> sync.log - and since sending the email I noticed nothing is being put
> into the horde.log either!
> >
> > Here are my settings for that:
> >
> > 48 $conf['log']['priority'] = 'INFO';
> >  49 $conf['log']['ident'] = 'HORDE';
> >  50 $conf['log']['ident'] = 'HORDE';
> >  51 $conf['log']['name'] = '/var/log/horde/horde4.log';
> >  52 $conf['log']['params']['append'] = true;
> >  53 $conf['log']['params']['format'] = 'default';
> >  54 $conf['log']['enabled'] = true;
> >  55 $conf['log_accesskeys'] = false;
> >
> > Here are my directory permissions:
> > drwxr-x---  3 root   adm       4.0K Sep 18 06:26 apache2/
> > drw-rw----  2 root   www-data  4.0K Aug  8 21:32 horde/
> >
> > Perhaps I need to make them the same as the apache ones?
> >
> > But is an inability to write to the log a reason for the set-up
> failure?
> 
> I'm not a Horde expert, however, your log directory is set to not
> being able to access it
> 
> drw-rw----  2 root   www-data  4.0K Aug  8 21:32 horde/
> 
> Should be at least
> 
> drwxrwx---  2 root   www-data  4.0K Aug  8 21:32 horde/
> 
> Do this with chmod o+x,g+x horde or chmod 770 horde
> 
> To see what user/group should be writing to that directory, check the
> logs in your apache2 directory, and see which owner and group control
> those files. I suspect, as www-data is the owner of the horde
> directory, unless something has adjusted the owners of the files, it
> will *probably* be www-data.
> 
> Another alternative is to temporarily set horde to being rwxrwxrwx
> and see which user writes to the log file in there, then change it
> back to being rwxrwx <newowner> <newgroup>

Actually all the files in /var/log/apache2 are either root:root or root:adm

The problem is not on the directory ownership, I don't think - apache2 is 750 and horde is 760 - so to my understanding it already has weaker permissions.  

Nevertheless changing permissions to 766 and owner/group to www-data and even touching the files does nothing.  I'm sure it's an error in the Horde installation (rather than the product since no one else seems to have this issue).  I've checked the config against the test server and they are the same.

But that's a problem, because I don't know where to look now.  And without logging of any sort I won't be able to debug the Activesync.

Simon