OpenChange causes Samba crash (and then no more usable)

[stevew]

I was a bit foolish and tried this for a small customer of ours ...

I tried turning off Cached Exchange Mode on all the machines, which had "some effect", in that a few started working ... So I added more and it just got progressively worse.

I also tried importing from PST, and I have a feeling it was a monster 9GB mailbox which caused it. since I have backups I'm going to try a more stable version of OpenChange until this gets worked out.

[rcarney]

I am having exactly the same problem, guys and gals.  Crash crash crashes are real and serious. Making the software pretty much useless.  There are YouTube videos showing it working perfectly.  What has happened and who is approving the releases that waste everyone's time.  Come on people...   What release actually works?

[rcarney]

Someone on the project should post that 3.4 does NOT work as a Microsoft Exchange replacement to save people time...  Especially not as a drop in as is being advertised.  We waste time and get frustrated then lose confidence in the Zentyal project and team.

The goal is admirable, but do NOT release things that do NOT work, please.

[kissg1988]

I'd like to point out that these crashes are still present in Zentyal 3.4 Community Edition. Profile creation works fine in Outlook, but as soon as I try to send a message, samba crashes and accepts no connections until it is restarted.

Using the nightly build of Zentyal 3.5, it's even worse: I couldn't even configure my mailbox in Outlook 2010 as the profile creation process does not work at all, it is stuck at the step where the mailbox's name should be resolved.

I'm aware that openchange integration is still a a tech preview but I'd expect slightly more stable operation, it's impossible to test how it performs if it doesn't perform at all.

I even installed a clean CentOS 6.5 system and created an openchange environment from scratch by carefully following the cookbook's instructions on the Openchange project site. I tried compiling the softwares from source but it was too time-consuming so I switched to the nightly build packages published by Inverse (samba4 + openchange + sogo) but the result is the same: unstable operation.

Zentyal as a whole is an awesome project and a really worthful alternative for SMBs that want to cut their costs but the openchange implementation still looks way too unstable to be able to use in production.

Are there any plans to improve openchange's stability in the next release of Zentyal? What about the business releases? Do they already have a stable implementation of openchange?

Thanks and keep up the good work!

[rcarney]

Can someone from the project please comment on this state of affairs?

Thank you!

[Luigi]

Hi Everyone,

We're too having similar issues with openchange on zentyal 3.4.3.

We are managing to connect outlook to the mailbox but as soon as there is some activity on the mailbox the connection to the server is lost and on the zentyal web GUI we get a samba crash report. In order to be able to re-connect the samba service has to be restarted.

We have attempted to apply several updates which related to samba and openchange but nothing seems to be tackling this issue.

We have also tried using the non-cached mode in outlook yet still we got the same results.

Has anyone managed to successfully use openchange or found a solution to this issue?

Thanks and regards,
Luigi

[rcarney]

is there any one from Zentyal looking at these forums?  At least give us a status - please....

[w00dmAn]

Same things
Anyone try to reinstall a module?

[theb2b]

Here is what I know about this problem
1. Here is the crux of the problem, from the crash report;
     Traceback (most recent call last):
        File "/usr/sbin/samba_dnsupdate", line 510, in <module>
          get_credentials(lp)
        File "/usr/sbin/samba_dnsupdate", line 123, in get_credentials
          raise e
     RuntimeError: kinit for SERVERNAME$@DOMAIN-NAME.LOCAL failed (Cannot contact any KDC for requested realm)
2. Known bug with samba4, see here;
             https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/809638
3. Did the suggested fix\work around, did not work
      modify /etc/krb5.conf
------------ snip snip -------------------
[libdefaults]
 default_realm = VMNET.US
 dns_lookup_realm = false
 dns_lookup_kdc = true
 ticket_lifetime = 24h
 renew_lifetime = 7d
 forwardable = true

[realms]
 VMNET.US = {
  kdc = vmnet-dc1.vmnet.us
  admin_server = vmnet-dc1.vmnet.us
 }

[domain_realm]
 .vmnet.us = VMNET.US
 vmnet.us = VMNET.US

Made the changes, modified as needed to match my domain, restarted DNS, still suffering from the same issue, now what??
Supposedly zentyal to drop openladp and go with samba4 only, attempt to overcome this problem???

4.No official response on how to fix this issue

In the meantime any idea's anyone, anyone, anyone.

[rcarney]

Zentyal team, can you please comment on this thread?

[psifactory]

A Comment from the team would be very nice....

[scuzz]

I have the same problems on zentyal 3.4.6.
I think i'll remove Zentyal Server and upgrade to a new Microsoft Server. I really like the Zentyal
project but I think it's gonna take a couple of years before it will turn into a real microsoft replacement

[psifactory]

I did a test with the version 3.5 beta. And after importing a .pst to an exchange account the openchange module crashes..

[rcarney]

I was hoping they would fix this issue in 3.5, sad.

[psifactory]

Does anyone know if there is a bug ticket?