SugarCRM 6.0.2 CE on Multiple backend servers - problem staying logged in

**sean.powell** · 2011-07-09, 01:44 AM

[Edit - I'm running 6.2.0 not 6.0.2]

Hello,

A little background on my infrastructure before we get into the problem -
I am running 8 CentOS servers running apache and php and all the usual bells and whistles. These apache servers have a mounted NFS volume sharing the document root of every website on my "cluster". I then have a separate beefy MySQL 5.1 database server.

Sitting in front of this configuration is a F5 BigIP Load balancer that routes traffic to a up/healthy "web node" (one of the 8 machines centos machines).

Now onto the problem:

I have a fresh install of sugarcrm. The sugarcrm document root is housed on the NFS share, so they are identical across all web nodes (as they all have that NFS share mounted as their document root). I installed and configured this all going specifically to one host (dubbed web1, of course!). I had no issue at all until I activated the load balancer and started to hit all 8 nodes after the initial installation.

Now my specific problem is that once I login, I will click through a couple pages (namely in the admin section so far) and I will immediately get logged out with the red text "You have been logged out because your session has expired."

I have turned off the following option in the configuration file (config.php in document root): 'verify_client_ip' => false, in order to alleviate this problem, but it appears to have no affect.

Is there anything else I need to be doing to make this work? I have not had much issue with any other dynamic, php-driven software solutions such as Drupal and Wordpress and the like so I am a bit stumped on what I need to do to fix this.

Any advice would be greatly appreciated.

Sean

**sean.powell** · 2011-07-09, 02:08 AM

I seem to have fixed it

I moved my php sessions onto the NFS so they are now shared across all 8 web nodes. This has fixed the problem apparently. I guess other solutions I am currently running don't rely so heavily on php sessions, which is why I haven't encountered this yet.