Zentyal Openchange Bugs to report

[cpunchin]

Hi All:

I have been toying with Openchange and Sogo for some time. Unfortunately, based on my experience, it's not ready for prime time for our office. So far, the biggest showstopper has been a known bug that makes Samba crash when you access shared contacts and/or calendars with Outlook. No, we don't use TB at the office...

I recently learned that Zentyal 3.3 had Openchange so I decided to give it a shot. Installation was flawless (waaaay faster than Sogo), however, the sharing bug was still there...  Let's hope the next update has that bug fixed since Sogo already fixed it (haven't tested it yet)

Another thing I've also noticed was that the appointments and contacts created on Outlook replicate to RoundCube Webmail, but not vice-versa (appointments created on RoundCube never land on Outlook).

Cheers to all and great job!

[jkerihuel]

Hi,

Thanks for your feedback.

I recently learned that Zentyal 3.3 had Openchange so I decided to give it a shot. Installation was flawless (waaaay faster than Sogo), however, the sharing bug was still there...  Let's hope the next update has that bug fixed since Sogo already fixed it (haven't tested it yet)

OK, so if the problem has been fixed on SOGo, then you can presumably expect an update of the SOGo package in Zentyal to fix it too. We are working closely with the SOGo people, so I'll push this forward and look for the reference ticket to find when the fix was committed. If you happen to have the ticket number you are referring in mind, sharing it would be appreciated ;-)

The next step will be to integrate this test to our Q/A automated process and ensure we do not have any regression with this in the future.

Another thing I've also noticed was that the appointments and contacts created on Outlook replicate to RoundCube Webmail, but not vice-versa (appointments created on RoundCube never land on Outlook).

Are you sure you synchronized Microsoft Outlook calendar (Shift-F9)? At the moment, there is no notifications triggered to Outlook when an appointment is created - for example - through Roundcube. Therefore, it is required to click Send&Receive and in some cases, even wait a bit longer at the moment.

Best Regards,
Julien.

[cpunchin]

Hi jkerihuel

As requested,

http://www.sogo.nu/bugs/view.php?id=2405

I also found another regarding the webmail synch issues

http://sogo.nu/bugs/view.php?id=2285

Both of them have been fixed. I'm basically waiting for Sogo 2.1 to be released to validate them.

[cpunchin]

Are you sure you synchronized Microsoft Outlook calendar (Shift-F9)? At the moment, there is no notifications triggered to Outlook when an appointment is created - for example - through Roundcube. Therefore, it is required to click Send&Receive and in some cases, even wait a bit longer at the moment.

Best Regards,
Julien.

I did a "synchronize folder" on Outlook. Contacts come in fine and I can see the download progress, but webmail originated appointments don't. Let me try the Shft-F9 trick and report back.

[jkerihuel]

Thanks for updating the ticket.

We will check whether we miss the SOGo update and if the fix is working and get back to you asap.

Best Regards,
Julien.

[jkerihuel]

I also found another regarding the webmail synch issues

http://sogo.nu/bugs/view.php?id=2285

Hello,

We are by the way not affected by this bug because Zentyal Webmail is directly fetching, creating and editing contacts through OpenChange server using PHP bindings.

Best Regards,
Julien

[jkerihuel]

We have scheduled a merge of SOGo latest version along with update of packages for tomorrow.

Best Regards,
Julien.

[cpunchin]

OK, I tried the Shft-F9 trick and it worked. However, the "Refresh Folders" also worked this time with the appointments this time. 

Seems that the Samba crash killed the sych and a full reboot fixed it.

I'll wait for the next update and do a full install and report back again...

Cheers

[J. A. Calvo]

Hi cpunchin,

We've just pushed sogo 2.1 to the Zentyal 3.3 archive. Can you please try to upgrade and give us some feedback?

Thanks!!

[cpunchin]

Sure will...

Shall I do an dist-update from my existing 3.3 or a full dist-upgrade from 3.2 ?

I can do both.

Great job

[jkerihuel]

Shall I do an dist-update from my existing 3.3 or a full dist-upgrade from 3.2 ?

apt-get upgrade from existing 3.3 should be enough.

Br,
Julien.

[cpunchin]

After the update still got issues... I did a clean install, but same.

The first outlook client connected fine (but I got a bunch of Synch Log errors)

 23:24:07 Error in folder 'Conflicts'
23:24:07        [80070057-501-80070057-733]
23:24:07        The client operation failed.
23:24:07        Microsoft Exchange Information Store
23:24:07        For more information on this failure, click the URL below:
23:24:07        http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80070057-501-80070057-733
23:24:07 Error in folder 'Local Failures'
23:24:07        [80070057-501-80070057-733]
23:24:07        The client operation failed.
23:24:07        Microsoft Exchange Information Store
23:24:07        For more information on this failure, click the URL below:
23:24:07        http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=80070057-501-80070057-733


When the second Outlook client connected I got a bunch of Samba erros and Openchange stopped responding.

See attached logs

[jkerihuel]

After the update still got issues... I did a clean install, but same.

The first outlook client connected fine (but I got a bunch of Synch Log errors)

 23:24:07 Error in folder 'Conflicts'
[...]

Hello,

If you performed a clean install, then you also need to create Outlook profiles again to sanitize the cached mode data and prevent Outlook to use mismatching sync data or recreating root folder (as exposed in the logs you provided).

Therefore the problem you encounter is unrelated to the issue you exposed in the first place. It surely requires some additional sanity checks in the fxics code along with potential provisioning changes to make sure Outlook understands this is a different server and therefore discard the existing info or warn the user. However one bug at the time.

In the meanwhile, shall I ask you to perform a new test with fresh Outlook profiles? You should not hit the last issue again and we will be able to confirm whether the sharing bug is fixed or not.

I will schedule some tasks related to information gathering (logs, dump) so we can retrieve more advanced data set and use the collected information to  investigate issues in-depth and to provide better hotfix, defensive code, sanity checks etc. I will keep you posted to this regards, hopefully on short (reasonable) notice.

Br,
Julien.

[cpunchin]

Hi Julien

My bad not to mention this before, but I did clean all the existing outlook profiles and created new ones before testing.

Another thing I did notice was that I need to do a server reboot after the error. A service rrstart is not sufficient. If needed let me know what logs to send.

Please keep in mind that this time I was not even far enough to set the sharing permissions.

I'll keep testing over the weekend...

[cpunchin]

I was able to replicate the problem.

1, Install Zentyal 3.2
2, Update to 3,3 and Install Openchange
3. Configure the Outlook Client, Create a new Profile and connect. Everything works fine. I had to manually install memcached to get rid of the SOGoCache errors from the samba logs.
4.I was able to play around with Outllook. I did notice tho, that I was getting Synch Issues at every folder synch.
5. I set to "share" my calendar with another users.
6. From another PC (brand new Outlook profile), I try to access the shared calendar and boom!. Connection is down. This time, not even a server reboot will reset it.


Hope this helps!...

Regards