[SOGo] Uncaught exception in sogo-tools when removing vacation
Hello, I have a problem with sogo-tool and SOGo 2.3.17 installed from the inverse repository (rhel6/CentOS6) and would like to know if: - I am the only one to meet this problem - If it's only a MySQL configuration problem or if it's a sogo-tool bug - If you can give any MySQL configuration tuning tips to get the best from SOGo So here is my problem : I use the cron /etc/cron.d/sogo provided by the sogo package to automatically disable the auto-reply of my users! But sometimes (can't find a pattern), the sogo-tool binary throw this uncaught exception : <0x0x2b9c2b8[SOGoCache]> Cache cleanup interval set every 300.00 seconds <0x0x2b9c2b8[SOGoCache]> Using host(s) 'localhost' as server(s) 2017-01-11 00:01:01.389 sogo-tool[24742] Removed auto-reply of user x /usr/sbin/sogo-tool: Uncaught exception FetchFailed, reason: Lost connection to MySQL server during query So i guess the problem is not comming from SOGo but I would like to get some hints/advices about the best way to fix this issue? And also want to make sure there is no problem with sogo-tool. Best regards, Julian -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
okay, thanks again. On 15.08.2013 14:00, Szládovics Péter wrote: Hi Michael, I think the RPC over LAN and HTTP proxy over WAN. All authentication settings are same in both method. 2013-08-15 08:33 keltezéssel, Michael Volz írta: Hi Peter, thanks again. I also tried several times with that box checked. But I will try this again. In general: which connection settings are the preferred / most stable ones? RPC or http proxy? Which authentication for each? I systematically tried them all but couldn't recognize big differences. How is that in your long term experience? Regards Michael Am 14.08.2013 19:34, schrieb Szládovics Péter: Michael, Did you check the Always prompt for user name and password checkbox at Exchange settings? http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf Chapter 8 (Page 17) - Step 8 Please check it again. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
Hey Ludovic, thanks for the information. From your BTS I see that there is a Bug concerning the creation of new Events in Outlook. From that I understand that I should at least be able to see my partners events if I have the permissions, am I right? Currently I only see the free/busy information. Kind regards Michael On 15.08.2013 14:39, Ludovic Marcotte wrote: On 2013-08-15 2:46 AM, Michael Volz wrote: thank you for your answer. That's kind of bad news. Do you mean SOGo 2.1 or OpenChange 2.1? SOGo v2.1 - look at our BTS for marked bugs for the release. Is there a schedule yet? I think it'll take 6 to 8 weeks before delivering that release. Is there a possibility that it would work with a more recent version of OpenChange compiled from source? Using the sources won't change anything. You could follow the bugs and eventually use a nightly build. Thanks, -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
Hi Peter, thanks again. I also tried several times with that box checked. But I will try this again. In general: which connection settings are the preferred / most stable ones? RPC or http proxy? Which authentication for each? I systematically tried them all but couldn't recognize big differences. How is that in your long term experience? Regards Michael Am 14.08.2013 19:34, schrieb Szládovics Péter: Michael, Did you check the Always prompt for user name and password checkbox at Exchange settings? http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf Chapter 8 (Page 17) - Step 8 Please check it again. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
Hi Michael, I think the RPC over LAN and HTTP proxy over WAN. All authentication settings are same in both method. 2013-08-15 08:33 keltezéssel, Michael Volz írta: Hi Peter, thanks again. I also tried several times with that box checked. But I will try this again. In general: which connection settings are the preferred / most stable ones? RPC or http proxy? Which authentication for each? I systematically tried them all but couldn't recognize big differences. How is that in your long term experience? Regards Michael Am 14.08.2013 19:34, schrieb Szládovics Péter: Michael, Did you check the Always prompt for user name and password checkbox at Exchange settings? http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf Chapter 8 (Page 17) - Step 8 Please check it again. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
On 2013-08-15 2:46 AM, Michael Volz wrote: thank you for your answer. That's kind of bad news. Do you mean SOGo 2.1 or OpenChange 2.1? SOGo v2.1 - look at our BTS for marked bugs for the release. Is there a schedule yet? I think it'll take 6 to 8 weeks before delivering that release. Is there a possibility that it would work with a more recent version of OpenChange compiled from source? Using the sources won't change anything. You could follow the bugs and eventually use a nightly build. Thanks, -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Uncaught exception
Dear sogo community, first of all I wanted to thank the inverse team, Péter Szladovics and Olivier Bitsch. With the help of their tutorials, VMs and scripts I was able to build an ansible playbook for installing SOGo and OpenChange. I need Outlook support, so the OpenChange part was critical. Thanks again, great work! But I am still having some issues. One is this uncaught exception that raises once in a while. Every time it does, Outlook looses connection to Exchange. It often happens when I try to share a user's calendar with another user: /usr/sbin/samba: Uncaught exception NSInvalidArgumentException, reason: SOGoMAPIDBFolder(instance) does not recognize folderType When I restart samba4 (which doesn't die, at least not entirely), Outlook can reconnect, but the expected changes of the permissions didn't happen. I uploaded a verbose (level 5) samba log of the event here: http://pastebin.com/HhMmc7rN. My smb.conf is like that: http://pastebin.com/L1TxejnP. Sogo is configured with GNUStep, the sogo-tool dump-defaults is: http://pastebin.com/bemzrg7c. I use postgresql as database backend and dovecot as imap server. In general outlook works. I can receive and send emails, I can create and modify calendar items and contacts. Only calendar sharing is limited and I have stability problems because of such exceptions that make a restart of samba necessary. Regarding calendar sharing: I can share calendars in SOGo web interface and it fully works there. My partner can create, modify and delete calendar items for me. But this doesn't work in Outlook. For Outlook the same shared calendar is read only and I only see the free/busy information, not event details. If I want to change the permissions for my calendar through Outlook it doesn't let me choose options that allow the other person to make changes. I can select them but they would immediately switch back to the read only versions when I commit the changes. And most of the time such operations cause exceptions like the one described above. Is this normal behavior because of the limits of the outlook compatibility or can it be solved? I read that seeing the details of appointments may not be supported. Is this still the case and if yes - is it likely to change? Are there ways to make it happen? Thanks a lot for any help or hint! Michael -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
2013-08-14 16:38 keltezéssel, Michael Volz írta: Dear sogo community, first of all I wanted to thank the inverse team, Péter Szladovics and Olivier Bitsch. With the help of their tutorials, VMs and scripts I was able to build an ansible playbook for installing SOGo and OpenChange. I need Outlook support, so the OpenChange part was critical. Thanks again, great work! But I am still having some issues. One is this uncaught exception that raises once in a while. Every time it does, Outlook looses connection to Exchange. It often happens when I try to share a user's calendar with another user: /usr/sbin/samba: Uncaught exception NSInvalidArgumentException, reason: SOGoMAPIDBFolder(instance) does not recognize folderType When I restart samba4 (which doesn't die, at least not entirely), Outlook can reconnect, but the expected changes of the permissions didn't happen. I uploaded a verbose (level 5) samba log of the event here: http://pastebin.com/HhMmc7rN. My smb.conf is like that: http://pastebin.com/L1TxejnP. Sogo is configured with GNUStep, the sogo-tool dump-defaults is: http://pastebin.com/bemzrg7c. I use postgresql as database backend and dovecot as imap server. In general outlook works. I can receive and send emails, I can create and modify calendar items and contacts. Only calendar sharing is limited and I have stability problems because of such exceptions that make a restart of samba necessary. Regarding calendar sharing: I can share calendars in SOGo web interface and it fully works there. My partner can create, modify and delete calendar items for me. But this doesn't work in Outlook. For Outlook the same shared calendar is read only and I only see the free/busy information, not event details. If I want to change the permissions for my calendar through Outlook it doesn't let me choose options that allow the other person to make changes. I can select them but they would immediately switch back to the read only versions when I commit the changes. And most of the time such operations cause exceptions like the one described above. Is this normal behavior because of the limits of the outlook compatibility or can it be solved? I read that seeing the details of appointments may not be supported. Is this still the case and if yes - is it likely to change? Are there ways to make it happen? Thanks a lot for any help or hint! Dear Michael, Just a hint from me, but it maybe (I hope) helps you. The outlook not the best choice (IMHO the worst), but on commercial environment it's the default (a Hungarian slang: the necessary evil). So. Workaround, but working fine: Share all of needed resources under the web (SOGo interface), and use them in Outlook. One thing won't works: shared folders. But contacts and calendars ;) You will need same method about out of office settings and server side mail rules. As far as I excperienced - Thunderbird the one and only MUA for using the most features (with lot of extensions), but neither the sharing resources. So, the web client will your best friend ever :) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
Dear Péter (and list), I fully agree with your opinion on Outlook. But it doesn't seem to be in our power to break its dominance in business environments so we sadly have to deal with it. I followed your hint an configured the permissions for the shared calendar with the web interface. It works fine there, I can read an write the shared calendars. But still it doesn't work in Outlook. I tried around and found that Outlook doesn't authenticate correctly against ocsmanager. As (if I recall right - correct me if I'm wrong) openchange handles shared calendars via ews and thus via ocsmanager that looks as it could be related to the problem. This is from the apache (ssl) log: 192.168.16.97 - - [14/Aug/2013:17:53:15 +0200] POST /ews/as HTTP/1.1 401 5317 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:53:15 +0200] POST /ews/as HTTP/1.1 401 634 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:53:15 +0200] POST /ews/as HTTP/1.1 200 3146 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:53:18 +0200] HEAD /ews/oab.xml HTTP/1.1 401 5264 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:53:20 +0200] HEAD /ews/oab.xml HTTP/1.1 401 325 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:53:22 +0200] HEAD /ews/oab.xml HTTP/1.1 401 325 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:53:22 +0200] HEAD /ews/oab.xml HTTP/1.1 401 581 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:53:22 +0200] HEAD /ews/oab.xml HTTP/1.1 404 261 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:53:24 +0200] POST /autodiscover/autodiscover.xml HTTP/1.1 401 5317 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:53:24 +0200] POST /autodiscover/autodiscover.xml HTTP/1.1 401 634 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:53:24 +0200] POST /autodiscover/autodiscover.xml HTTP/1.1 200 1514 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] POST /ews/oof HTTP/1.1 401 5317 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] POST /ews/oof HTTP/1.1 401 634 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] POST /ews/oof HTTP/1.1 404 362 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] POST /ews/oof HTTP/1.1 401 5317 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] POST /ews/oof HTTP/1.1 401 634 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:54:04 +0200] POST /ews/oof HTTP/1.1 404 362 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:54:26 +0200] HEAD /ews/oab.xml HTTP/1.1 401 5264 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:54:28 +0200] HEAD /ews/oab.xml HTTP/1.1 401 325 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:54:30 +0200] HEAD /ews/oab.xml HTTP/1.1 401 325 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:54:30 +0200] HEAD /ews/oab.xml HTTP/1.1 401 581 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:54:30 +0200] HEAD /ews/oab.xml HTTP/1.1 404 261 - Microsoft BITS/7.5 192.168.16.97 - - [14/Aug/2013:17:54:32 +0200] POST /autodiscover/autodiscover.xml HTTP/1.1 401 5573 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) 192.168.16.97 - - [14/Aug/2013:17:54:32 +0200] POST /autodiscover/autodiscover.xml HTTP/1.1 200 1514 - Microsoft Office/14.0 (Windows NT 6.1; Microsoft Outlook 14.0.6129; Pro) This is from the ocsmanager log: 2013-08-14 17:53:15,769 INFO [openchange.web.auth.NTLMAuthHandler] [worker 9] client did not pass auth cookie 2013-08-14 17:53:15,793 INFO [openchange.web.auth.NTLMAuthHandler] [worker 0] client did not pass auth cookie 2013-08-14 17:53:15,793 INFO [openchange.web.auth.NTLMAuthHandler] [worker 0] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock (1053) 2013-08-14 17:53:15,846 INFO [openchange.web.auth.NTLMAuthHandler] [worker 1] acquiring lock /var/cache/ntlmauthhandler/ntlm-127.0.0.1.lock (1053) 2013-08-14 17:53:18,191 INFO [openchange.web.auth.NTLMAuthHandler] [worker 3] client did not pass auth cookie 2013-08-14 17:53:20,680 INFO [openchange.web.auth.NTLMAuthHandler] [worker 5] client did not pass auth cookie 2013-08-14 17:53:22,700 INFO [openchange.web.auth.NTLMAuthHandler] [worker 4] client did not pass auth cookie 2013-08-14 17:53:22,704 INFO [openchange.web.auth.NTLMAuthHandler] [worker 6] client
Re: [SOGo] Uncaught exception
On 2013-08-14 11:05 AM, Szládovics Péter wrote: As far as I excperienced - Thunderbird the one and only MUA for using the most features (with lot of extensions), but neither the sharing resources. Not sure what you mean here but if you install the SOGo Integrator extension in Thunderbird, you can do everything SOGo Web can do regarding calendar sharing from Thunderbird. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
2013-08-14 19:18 keltezéssel, Ludovic Marcotte írta: On 2013-08-14 11:05 AM, Szládovics Péter wrote: As far as I excperienced - Thunderbird the one and only MUA for using the most features (with lot of extensions), but neither the sharing resources. Not sure what you mean here but if you install the SOGo Integrator extension in Thunderbird, you can do everything SOGo Web can do regarding calendar sharing from Thunderbird. Once I tried the integrator, but it didn't give username from me (just password) for authentication, and used the OS account. I use lot of mail accounts in one Thunderbird. Perhaps I was wrong, but I haven't tried it since that time. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
On 2013-08-14 12:19 PM, Michael Volz wrote: I followed your hint an configured the permissions for the shared calendar with the web interface. It works fine there, I can read an write the shared calendars. But still it doesn't work in Outlook. It's most likely currently broken and needs to be worked on. We aim to improve this considerably in the upcoming v2.1.0 release. -- Ludovic Marcotte lmarco...@inverse.ca :: +1.514.755.3630 :: http://inverse.ca Inverse inc. :: Leaders behind SOGo (http://sogo.nu) and PacketFence (http://packetfence.org) -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
2013-08-14 18:19 keltezéssel, Michael Volz írta: For me it looks like Outlook never sends the right authentication and because of that ocsmanager just sends the free/busy information but no other details back to Outlook. I can't dig deeper today, but I will tomorrow. Maybe somebody has an idea? I found that my /etc/ocsmanager/ocsmanager.ini (http://pastebin.com/Qcs0vriS) is pretty raw, was I supposed to configure it? I never came across it. Sorry for this unreflected mail - just some last minute thoughts before knock off. But am I right that my calendar problem could be related to ocsmanager or is this normal behaviour? I also saw that even when I tell Outlook to connect via http there is very little activity with apache oder ocsmanager but very much witch samba so it seems to me that it connects directly via rpc after all. Michael, Did you check the Always prompt for user name and password checkbox at Exchange settings? http://www.sogo.nu/files/docs/SOGo%20Native%20Microsoft%20Outlook%20Configuration.pdf Chapter 8 (Page 17) - Step 8 Please check it again. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Uncaught exception
On 13-08-14 1:30 PM, Szládovics Péter wrote: 2013-08-14 19:18 keltezéssel, Ludovic Marcotte írta: On 2013-08-14 11:05 AM, Szládovics Péter wrote: As far as I excperienced - Thunderbird the one and only MUA for using the most features (with lot of extensions), but neither the sharing resources. Not sure what you mean here but if you install the SOGo Integrator extension in Thunderbird, you can do everything SOGo Web can do regarding calendar sharing from Thunderbird. Once I tried the integrator, but it didn't give username from me (just password) for authentication, and used the OS account. I use lot of mail accounts in one Thunderbird. Perhaps I was wrong, but I haven't tried it since that time. the integrator uses the username from the default mail account to authenticate against the sogo server. -- users@sogo.nu https://inverse.ca/sogo/lists
