[imp] Errors in loging into Imp.

[Ray Masa]

Hello,

I am having similar problems as Robert.  Logging issues with IMP and 
/tmp/horde.log does not receive any message.  Its always blank.

With regards to logging in, here is what I am seeing:

Horde is setup to authenticate via IMP.

When I attempt to log in using IE (version 5.0, 5.5, and 6.0) I keep getting 
returned to the log in page (no error messages, but also not logged in).  
This happens most of the time, but I have noticed that randomly (like every 
15th time or so), I will log in successfully.

When I attempt to log into just IMP (by clicking on the mail icon on the nav 
bar), I have to log in twice.  The first attempt gives me the following 
message:

Your Mail session has expired. Please login again.

My second attempt logs me into IMP.

This is only an issue with IE.  I can log into both Horde and IMP directly 
via Netscape (4.76).

If I disable the horde login via IMP, I can login correctly into horde in 
the first attempt.

I have also checked for the cookie path:
	In php.ini:
session.cookie_path = /

In horde registry.php:
	cookie_path' => '/',
	Previously it was set to cookie_path' => '/horde',


I did not find $conf['cookie']['path'] in any of the files.  Should I have 
this?  If so, which file(s) and where should this be?

All apps are installed under horde (http://www.site.com/horde).

I have installed the following components:

Horde 2.1
IMP 3.1
Kronolith 1.0
Turba 1.1
Mnemo 1.0
Nag 1.0

This is installed on:
FreeBSD 4.4
Apache
MySQL


At first I thought upgrading to IE 6 might help.  But I continue to get 
exactly the same issue.

Any ideas on how to solve this.  It is related to IMP and IE.

Ray


>From: Eric Rostetter <eric.rostetter@physics.utexas.edu>
>To: robert sand <rsand@d.umn.edu>
>CC: imp@lists.horde.org
>Subject: Re: [imp] Errors in loging into Imp.
>Date: Wed, 18 Sep 2002 10:33:14 -0500
>
>Quoting robert sand <rsand@d.umn.edu>:
>
> > The cookie path didn't chage anything.
>
>Okay, so what is your cookie path set to in horde and in php.ini?  Also,
>what are your aliases and/or RootDirectory paths in your web server config?
>Did you follow the information in the admin FAQ about how to set this
>stuff up correctly? (See http://www.horde.org/faq/admin/config/index.php#c3
>for more info).
>
> > If I knew what part of horde or imp was
> > causing the segmentation fault I would fix it but nothing is reporting 
>any
> > porblems.  The /tmp/horde.log file is empty even though I have the level 
>all
> > the way down to debug.
>
>Well, it may be unrelated to your login problems also. But surely a seg
>fault is a bad thing and should be looked at.  Also, the seg fault could
>be coming from somewhere else (like hackers trying to exploit your web
>server, etc).
>
>Okay, so you say you can't login, right?  If using Horde authentication,
>that means the seg fault is likely being produced from a call to either
>the index page (index.php) or the login page (login.php), right?
>If using IMP authentication, then in addition to the above you need to
>look at IMP's index.php, login.php, and redirect.php files which are
>involved in login.  So that limits your set to basically 2-3 files.
>
>Anyway, you probably don't even need to know that.  Looking at your log
>files from the web server, you should see a timestamp for the seg fault.
>You should then correlate that to the web server access log to see which
>access was right before that (same time, or very small delta before it).
>That should tell you which file produced the seg fault.
>
>Or, run your web server in the foreground rather than detached/backrounded.
>Watch your web logs.  Enable the web server debugging.  Maybe even run the
>web server in a debugger.  Then hit the pages.  Should clear things up.
>
>Most useful is something like this from
>http://www.php.net/manual/sv/print/faq.installation.php#faq.installation.nodata
>
>     * Stop your httpd processes
>     * gdb httpd
>     * Stop your httpd processes
>     * > run -X -f /path/to/httpd.conf
>     * Then fetch the URL causing the problem with your browser
>     * > run -X -f /path/to/httpd.conf
>     * If you are getting a core dump, gdb should inform you of this now
>     * type: bt
>
>If you have a standalone php command, you may be able to test pages with
>it and find the crash that way also.
>
>--
>Eric Rostetter
>The Department of Physics
>The University of Texas at Austin
>
>"Can you hear me now? ... Good!"
>"Can you hear me now? ... Good!"
>
>--
>IMP mailing list
>Frequently Asked Questions: http://horde.org/faq/
>To unsubscribe, mail: imp-unsubscribe@lists.horde.org




_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com