[horde] Error: No connection to server

[Simon Brereton]

On 4 November 2011 15:38, Michael J Rubinsky <mrubinsk at horde.org> wrote:
>
> Quoting Simon Brereton <simon.brereton at buongiorno.com>:
>
>> However, I can definitely reproduce this - as soon as I downgrade the
>> memory limit to 128M, the portal page fails to display (either on
>> login or changing the URL first to IMP and then going to the portal).
>
> Seeing how this happens as soon as you navigate to the portal page, why not
> try to figure out which block is causing this? Either remove the blocks one
> by one until it stops happening, or remove them all and start re-adding
> them...

A lot of work, but I like you and I'd like to help improve a product
that I love...

Obviously, I can't do this for all users and combinations of blocks.
By default the account information block and the Metar block are
present from the Horde portal configuration.

-  Logout.
-  Clear Cache.
-  Remove preferences from the horde_prefs
-  Set limit to 64M
-  restart apache
-  login
-  blank screen
-  same in Chrome
-  remove the Metar block from horde4/config/conf.php
-  login
-  blank screen
-  Change URL to imp
-  ERROR CONNECTING TO SERVER!
- logout
- remove account info from blocks
-  ensure horde_prefs portal layout is clear
-  restart apache for the hell of it.
-  login
- blank screen
-  change URL to imp/
-  ERROR CONNECTING TO SERVER
-  Raise memory to 128M
-  restart apache
-  login
-  page is displayed, but portal has 1 block that says Horde is not activated
-  navigate to imp - messages load
-  logout
-  add in Metar block in horde4/config/conf.php
-  login
- blank page
-  at this point I mistakenly change the url to login.php - the portal
loaded with Metar block
-  change URL to imp (messages are displayed)
-  click on the portal link from within imp and portal is displayed,
with the Metar block
-  logout
-  login
-  blank page
-  change URL to imp/
-  logout
-  change the horde4/config/conf.php to account block only
-  login
-  portal is displayed correctly
-  logout
-  restore horde_prefs
-  login
-  blank page,
-  clear horde_prefs
-   change URL to imp/ and click on Portal link.
-  portal is displayed (complete with all the blocks I have (7) - even
though I just cleared the preference!
-  logout
-  increase memory to 256M
-  restart apache
-  change horde4/config/conf.php back to the default blocks
-  login
-  portal is displayed correctly (2 blocks).
-  logout
-  restore horde_prefs (portal_layout)
-  login
-  portal is displayed correctly (all 7 blocks)


>From this I conclude (that at least on my system - Debian 6.0,
2.6.32-5-amd64, Intel(R) Core(TM)2 Duo CPU     E7500  @ 2.93GHz) Horde
won't work with 64M, will work with 128M so long as it's not too
taxing and that 256M is needed for my relatively modest user-base,
small maildir sizes and under utilised portal spaces (I was going to
try loading a local only accessible site with graphs on system usage
in a portal block but I don't think I'll bother now.  Not unless I can
go to Eric's 1024M limit.

Simon