Hi List,
I've done a Sogo install with Samb4 from the sogo.repo on a CentOS 6.3
box - I've done it on both a physical server as well as an OpenVZ
container and the results are always the same.
The versions are as follows:
samba4-4.0.1-4.centos6.1.x86_64
openchange-rpcproxy-2.0.r3669.sogo-1.centos6.x86_64
sogo-activesync-2.2.7-1.centos6.x86_64
openchange-2.0.r3669.sogo-1.centos6.x86_64
openchange-ocsmanager-2.0.r3669.sogo-1.centos6.x86_64
sogo-openchange-backend-2.2.6-1.centos6.x86_64
sogo-2.2.7-1.centos6.x86_64
dovecot-2.0.9-7.el6_5.1.x86_64
dovecot-pigeonhole-2.0.9-7.el6_5.1.x86_64
The system installs the Outlook clients can connect (I've set both
dovecot and Sogo to use the internal Samba4 LDAP directory for auth) - I
have this in my dovecot.conf:
passdb {
driver = static
args = nopassword=y
}
Which is what I understand is needed to take care of "trust" or no
password auth.
I can give more details of my config if needed - I seem to have regular
frequent samba4 crashes - but not always with the same error:
Common ones are:
PANIC: Bad talloc magic value - unknown value
PANIC: internal error
One or two things to query for a start:
1. How can I create a trace to better help here?
2. I notice the version of Samb4 in use on the repo is quite old by now
- the latest release is: 4.0.21
I see quite a few references to patches or similar that might help
resolve but I'm not sure how to do that in the scenario I have with it
all being installed through yum as per the instructions on:
http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf
Unfort this is very urgent as we did not encounter this in testing and
only once the machine hit production!
Regards,
--
Lawrence Haw
Commercial Internet Solutions
Tel: +27879401302
Cel: +27827936386
Web: www.cis.za.net
--
[email protected]
https://inverse.ca/sogo/lists