[imp] Nothing being written to /tmp/horde.log

[Lachlan Cameron-Smith]

I've found the same in our setup - logging using the 'file' driver works 
fine on our server with Horde 2.1 and IMP 3.1, but no longer works for 
my Horde 2.2.3 and IMP 3.2.1 setup, with the logfile being created but 
not written to. I've had to add PEAR version 1.0.1 to make the newer 
versions happy, and this seems to be the problem - if I stick the 
Log-1.1 version which I was previously using into the PEAR directory, 
logging starts working again, but if I use the version of Log which 
comes with PEAR 1.0.1 (and even the latest version of Log, 1.6.5) no 
entries are written to the log file.

Regards,
Lachlan


Jim Adams wrote:

> Hello All:
> I have just completed installing Horde 2.2.3 and IMP 3.2.1.  While both
> Horde and IMP (along with Turba 1.2) are all seemingly working fine (logging
> in/out, reading and sending mail, looking up contacts from LDAP directory),
> the /tmp/horde.log file is still at 0 bytes (it is being created, but
> nothing written to it).
> 
> I am running this on Red Hat 9 with the following packages:
> httpd-2.0.40-21.1
> php-4.2.2-17
> sendmail-8.12.8-5.90
> pear-1.0.1
> 
> horde/test.php pages are saying I'm using correct versions of needed
> packages.
> 
> The permission settings on the /tmp/horde.log are as follows:
> --------------------
> drwxrwxrwt   12 root     root         4096 May  2 09:38 /tmp
> 
> -rw-r--r--    1 apache   apache          0 May  2 08:59 /tmp/horde.log
> --------------------
> 
> I have also verified that logging is enabled:  ** (see bottom if curious)
> /etc/php.ini is also set for logging:  *** (ditto)
> 
> 
> I've searched the FAQ pages and found no reference to this sort of problem.
> I've also searched the archives where I found one recent similar event
> mentioned:
> -------------------------------------------
> List:     imp
> Subject:  Re: [horde] logging....
> From:     Bill Dossett <bd () emtex ! com>
> Date:     2003-03-06 17:24:57
> 1
> Just to put this to rest, I found a patch to horde/lib/Horde.php
> that fixed it... logging now works  YAY!!!!
> 
> Bill
> ------------------------------------------
> 
> I've tried several different lib/Horde.php files from the CVS web tree.  The
> most recent one broke everything (1.287), so I went and found a version that
> has comments stating that the previous broke logging and I'm making the
> assumption that this version fixed it again  (1.118.2.41 by Chuck Hagenbuch)
> this was from about a month after the above comments where posted to the
> list.  I put that one into place, but no change with logging.  Can anyone
> steer me in the right direction on which version of lib/Horde.php fixes the
> logging problem or if the patch mentioned above is a completely different
> file located some where else in the CVS tree or if I am overlooking some
> other possible cause?
> 
> Thanks in advance for any and all help!
> 
> -Jim
> 
> ****Configuration file data below****
> 
> 
> 
> 
> ** horde/config/horde.php logging settings:
> -------------------------------------------
> // Should Horde log errors and other useful information?
> $conf['log']['enabled'] = true;
> 
> // What log driver should we use? Valid values are 'file', 'mcal',
> // 'sql', and 'syslog'.
> $conf['log']['type'] = 'file';
> 
> // What is the name of the log? For the 'file' driver, this is the
> // path to a text file; for mcal, it would be the name of a calendar,
> // and for sql it would be the table name to use. For the 'syslog'
> // driver it is the facility as a _constant_ (with no quotes), e.g.:
> // ... = LOG_LOCAL0;
> $conf['log']['name'] = '/tmp/horde.log';
> 
> // What level of messages should we log? The values are LOG_EMERG,
> // LOG_ALERT, LOG_CRIT, LOG_ERR, LOG_WARNING, LOG_NOTICE, LOG_INFO,
> // and LOG_DEBUG. Each level logs itself and all those that come
> // before it: LOG_ALERT would only log alerts and emergencies, but
> // LOG_DEBUG would log everything.
> $conf['log']['priority'] = LOG_DEBUG;
> 
> // What identifier should we use in the logs?
> $conf['log']['ident'] = 'HORDE';
> 
> // Any additonal configuration information, like an MCAL or database
> // username and password.
> $conf['log']['params'] = array();
> ------------------------------------------------------------
> 
> 
> *** /etc/php.ini log settings:
> ------------------------------------------------------------
> error_reporting  =  E_ALL & ~E_NOTICE
> 
> display_errors = On
> 
> display_startup_errors = Off
> 
> log_errors = On
> 
> ; Store the last error/warning message in $php_errormsg (boolean).
> track_errors = Off
> 
> ; Disable the inclusion of HTML tags in error messages.
> ;html_errors = Off
> 
> ; String to output before an error message.
> ;error_prepend_string = "<font color=ff0000>"
> 
> ; String to output after an error message.
> ;error_append_string = "</font>"
> 
> ; Log errors to specified file.
> error_log = /tmp/php-log
> -------------------------------------------------------


-- 
Lachlan Cameron-Smith
Senior Systems Specialist, ITS, Adelaide University

-----------------------------------------------------------
This email message is intended only for the addressee(s)
and contains information which may be confidential and/or
copyright.  If you are not the intended recipient please
do not read, save, forward, disclose, or copy the contents
of this email. If this email has been sent to you in error,
please notify the sender by reply email and delete this
email and any copies or links to this email completely and
immediately from your system.  No representation is made
that this email is free of viruses.  Virus scanning is
recommended and is the responsibility of the recipient.