Unable to view mail messages
Paul Waldo
paul at waldoware.com
Mon Jan 7 14:22:17 CET 2008
On Monday 07 January 2008 3:23:53 am Gunnar Wrobel wrote:
> Paul Waldo <paul at waldoware.com> writes:
> > On Monday 17 December 2007 11:23:28 am Gunnar Wrobel wrote:
> >> Paul Waldo <paul at waldoware.com> writes:
> >> > Gunnar Wrobel wrote:
> >> >
> >> > Paul Waldo <paul at waldoware.com> writes:
> >> >
> >> > Hi all,
> >> >
> >> > I'm running kolab-server-2.2-beta-3 on a Kubuntu Gutsy 64-bit
> >> > machine. I have successfully compiled and I'm running OK.
> >> >
> >> > I am using Horde to view email. I can see the list of
> >> > messages in my inbox. When I click the Subject link, I can't see the
> >> > message. I get different problems depending on the browser:
> >> >
> >> > - In Konqueror, I see an error message where the email message
> >> > should be: "An error occurred while loading
> >> >
> >> > https://kolab.waldo.home/horde/imp/message.php?mailbox=INBOX&index=486
> >> >: Connection to host kolab.waldo.home is broken"
> >> > If I use the Refresh button, the error is no longer displayed,
> >> > but the email message area is empty
> >> >
> >> > - In Firefox, I get a dialog saying "You have chosen to open
> >> > message.php which is a: PHP file[....] What should Firefox do with
> >> > this file?"
> >> >
> >> > It looks like I'm getting some errors in the log files:
> >> >
> >> > apache-errors.log
> >> > -------------------------------
> >> > [Mon Dec 17 10:37:29 2007] [notice] child pid 18340 exit
> >> > signal Segmentation fault (11)
> >> >
> >> > A segmentation fault sounds bad here. Is this is an extremely
> >> > large message or something with a big image attachment? Are you
> >> > running on a virtual machine or is this a normal server? In case it is
> >> > virtual do you have any resource limitation that is being hit there?
> >> > What is the memory limitation for php on your machine?
> >> >
> >> > This is a virtual machine (Xen). The message is not very large. I
> >> > also noticed this in the apache_error.log: zend_mm_heap corrupted
> >> >
> >> > Here is some memory info that may help. If you want anythig else,
> >> > please let me know!
> >> >
> >> > root at kolab:/kolab/var/apache/log# find /kolab-server-2.2-beta-3 -name
> >> > php.ini -exec grep -i memory {} \; -print memory_limit = 64M
> >> > ; Maximum amount of memory a script may consume
> >> > /kolab-server-2.2-beta-3/etc/apache/php.ini
> >> > memory_limit = 8M ; Maximum amount of memory a script may
> >> > consume /kolab-server-2.2-beta-3/etc/php/php.ini
> >> > root at kolab:/kolab/var/apache/log# free -m
> >> > total used free shared buffers
> >> > cached Mem: 512 484 27 0 22
> >> > 108 -/+ buffers/cache: 353 159
> >> > Swap: 1023 102 921
> >>
> >> I don't know Xen very much. From the vServers I'm running under
> >> Virtuozzo I'm used to getting a log entry when the virtual instance
> >> tries to allocate more memory than it is being allowed to. I'd assume
> >> Xen gives you something similar.
> >>
> >> I don't think the "free" command offers much insight here since it
> >> does not document the situation when you try to run the message.php
> >> script.
> >>
> >> But from your report I'd guess that it is really related to your
> >> vServer having not enough memory available.
> >>
> >> Cheers,
> >>
> >> Gunnar
> >>
> >> > root at kolab:/kolab/var/apache/log# uname -a
> >> > Linux kolab 2.6.22-14-xen #1 SMP Sun Oct 14 23:20:20 GMT 2007 x86_64
> >> > GNU/Linux
> >> >
> >> > horde.log
> >> > ------------------------
> >> >
> >> > Dec 17 10:38:21 HORDE [error] [turba] Unable to add
> >> > INBOX/Contacts: destination folder already exists [pid 17786 on line
> >> > 435 of
> >> > "/kolab-server-2.2-beta-3/var/kolab/www/horde/turba/lib/Turba.php"]
> >> >
> >> > php-errors.log
> >> > --------------------------
> >> > [17-Dec-2007 10:34:16] PHP Notice: Unknown: SECURITY PROBLEM:
> >> > insecure server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0
> >> > [17-Dec-2007 10:37:51] PHP Notice: Undefined index: default
> >> > in
> >> > /kolab-server-2.2-beta-3/var/kolab/www/horde/turba/lib/Driver/kolab.ph
> >> >p on line 175
> >> > [17-Dec-2007 10:38:21] PHP Notice: Undefined index: default
> >> > in
> >> > /kolab-server-2.2-beta-3/var/kolab/www/horde/turba/lib/Driver/kolab.ph
> >> >p on line 175
> >> >
> >> > These errors (in fact notices) are normal as far as I can tell.
> >> > Not all of this have been removed yet but I hope to be able to track
> >> > all these issues down until we release Kolab server 2.2.
> >> >
> >> > Cheers,
> >> >
> >> > Gunnar
> >> >
> >> > _______________________________________________
> >> > Kolab-users mailing list
> >> > Kolab-users at kolab.org
> >> > https://kolab.org/mailman/listinfo/kolab-users
> >
> > Hi Gunnar,
> >
> > I don't think its a memory problem. I stopped the kolab server, doubled
> > its memory to 1 GB, and restarted. Other than kolab starting, I see
> > nothing of interest in the syslog. I still get the problem, though:
> >
> >
> > root at kolab:~# tail /kolab/var/apache/log/apache-error.log
> > [Mon Dec 17 10:43:39 2007] [notice] child pid 2018 exit signal
> > Segmentation fault (11)
> > [Mon Dec 17 10:43:39 2007] [notice] child pid 18336 exit signal
> > Segmentation fault (11)
> > zend_mm_heap corrupted
> > [Mon Dec 17 11:27:15 2007] [notice] caught SIGTERM, shutting down
> > [Mon Dec 17 11:28:18 2007] [notice] suEXEC mechanism enabled
> > (wrapper: /kolab/sbin/suexec)
> > [Mon Dec 17 11:28:18 2007] [notice] Digest: generating secret for digest
> > authentication ...
> > [Mon Dec 17 11:28:18 2007] [notice] Digest: done
> > [Mon Dec 17 11:28:19 2007] [notice] Apache/2.2.6 (OpenPKG/CURRENT)
> > mod_ssl/2.2.6 OpenSSL/0.9.8g PHP/5.2.5 configured -- resuming normal
> > operations
> > [Mon Dec 17 11:30:41 2007] [notice] child pid 4923 exit signal
> > Segmentation fault (11)
> > [Mon Dec 17 11:31:52 2007] [notice] child pid 4925 exit signal
> > Segmentation fault (11)
> > root at kolab:~# free -m
> > total used free shared buffers cached
> > Mem: 1024 426 597 0 6 164
> > -/+ buffers/cache: 255 768
> > Swap: 1023 0 1023
>
> From your recent request about cross compiling I assume that this
> issue has been resolved? Is that correct?
>
> Were you able to determine what caused the problem?
>
> Thanks!
>
> Gunnar
Thanks for the reminder, Gunnar! It turns out I still have this problem in
Horde. I have been using Kontact for a while and forgot all about the Web
part of the equation! Any ideas on what is causing these problems? Thanks!
Paul
More information about the users
mailing list