Actually, my goal was to correct the error I am having, specifically keep the database and mail homes for the domains on a more robust centralized server and export them via NFS to the front end nodes. This would provide some degree of resiliancy.
The errors I posted are the only ones I see - even when looking in logs. However, Firefox does specifically refer to the IMAP server losing connectivity so I guess I'll start there.
Can you elaborate a bit mor on your suggestion for the PHP session directory?
Thanks!
-------------- Original message --------------
From: "Paul Lesniewski" <paul@xxxxxxxxxxxxxxxx>
> > In order to build a more resiliant hosting environment, I built two
> > identical mail servers, each running ubuntu 8, postfix, courrier,
> > squirrelmail, mysql, etc. They work great as documented for virtual domain
> > hosting. My second phase was to build a third server housing the mysql user
> > database as well as the directories for the mail homes for each domain. I
> > would then expoirt via NFS to each front end mail server (mysql disabled on
> > each for phase 2, and they authenticate against the singel mysql database
> > server). Using simple pop, etc this setup works fine. But, when using
> > squirrelmail as a front end, I get an error after a successful
> > authenticat ion. T he web page is blank except for an error saying
> > "Squirrelmail: Error" in the browser tab.
>
> Are you asking for advice on building clustered mail server systems or
> for how to fix this problem? Your email reads like the former. The
> latter can only be solved if you get information about the issue from
> your web server logs per the mailing list posting guidelines, but it
> might be related to faulty (or lack of?) session tracking between the
> web servers, etc. But seriously, if you think telling us you get
> "Squirrelmail: Error" is going to help us help you...
>
> > Thie happens on both IE and
> > Firefox. Squirrelmail works fine when the mail homes are local to a front
> > end server and not accessed via NFS. I also confirmed that the NFS mounts
> > have read/write capability from the front end servers, so it 's not a
> > permissions problem. > >
> > Any advice on Squirrelmail and NFS? What's the alternative to build this out
> > to be more resiliant?
>
> Put PHP sessions in the DB or share the PHP session directory over NFS.
>
> > And for those who want to say that "The single database server is a single
> > point of failure" - this server is a Sun v490 with a 3510 array so it's got
> > plenty of redundancy. It's less likely that this server will fail as
> > compared to the 1U boxes on the front end.
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ---- -
> squirrelmail-users mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
> List info (subscribe/unsubscribe/change options):
> https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
----- squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
