Hi Allen,
We've got all our SOGo instances currently running on a mix of ESX 4.1,
ESXi 4.1 and ESXi 5 hosts (we're in the process of migrating to vSphere
5) - all 1.3.8b at the moment.
We're running 32 bit CentOS 5 instances, up to date as of a few days ago.
In all cases our SOGo VMs are used only for SOGo itself, a matching
Apache instance and a memcache instance. MySQL backends are on other
VMs, as are Funambol and LDAP instances. Since the OS is free why not
restrict it to one VM per function no? :)
I'd have to check the Funambol/SOGo-Connector versions but I'm pretty
sure they were the versions recommended on the website.
I've not seen any issues with Calendar causing a crash when synced with
Funambol, but I'd suggest upgrading to the current release version
unless there's a compelling reason not to, to ensure that any bugs that
could have cause this behaviour haven't already been fixed.
We were previously running the 1.3.5 version without that kind of bug
showing up, incidentally. I can't honestly recall if we had Funambol
running at that point however.
Thanks,
-Nathanael Bettridge
On 27/10/2011 1:34 AM, Allen Chen wrote:
Hi,
I really have some problems with SOGo-1.3.5a rpms on ESXi 4.1 guest
with CentOS 5.6(32bit).
Can somebody post your working environments running on VMware?
1. Vmware version?
2. Linux version? 32 or 64
3. SOGo version? rpm or source?
4. Funambol and SOGo-connector?
I reinstalled SOGo-1.3.5a rpms on CentOS 5.6(32bit) with different
hardware environments:
SOGo works fine with VirtualBox, CentOS KVM and any physical machines.
But I have some issues with SOGo on ESXi 4.1 guest: the installation
is done without any
problems. but sogo daemon exits with signal 11 when I click 'Calendar'
in web GUI. This happens
if the calendar has been synced with Funambol.
Thanks a lot,
Allen
--
[email protected]
https://inverse.ca/sogo/lists
