I've managed to resolve issues with message in error log: " ... [SoWebDAVRenderer]> got bogus port information from webserver: ..." According to recommendation from http://www.blog.happytec.at/index.php?mode=view&id=333 , following line should be added to nginx SOGo config:
proxy_set_header x-webobjects-server-port $server_port; It would be nice if someone can update "Config for Nginx and Sogo" Wiki page: http://wiki.sogo.nu/nginxSettings However, problem with non-functional freebusy lookups still persist. I've enabled verbose logging in SOGo, and I can't see any suspicious entry in SOGo log. I've used curl to test freebusy dav url - and it works OK: https://127.0.0.1/SOGo/dav/user/freebusy.ifb However, freebusy lookup from web interface doesn't work: POST /SOGo/so/user/freebusy.ifb/ajaxRead?sday=20140312&eday=20140326 HTTP/1.0" 200 52/0 0.057 2879 98% 0 Content of HTTP response body is made of all zeroes. The exactly same SQL query is executed in both cases: SQL: SELECT c_defaults FROM sogo_user_profile WHERE c_uid =user On Sat, Mar 8, 2014 at 11:01 PM, Djordje Crni <[email protected]>wrote: > I've upgraded to v2.2.1. SOGo and sope49-* packages (x86_64) installed > from "stable" Inverse YUM repository. > The problem remains, there are no free-busy information. > Downgraded again to v2.1.1b, and it works OK. > There are no errors in the log file before or after entry: > POST /SOGo/so/username/freebusy.ifb/ajaxRead?sday=.... > > > > On Thu, Mar 6, 2014 at 9:29 AM, Djordje Crni <[email protected]>wrote: > >> OS: CentOS 6.5 x86_64 >> SOGo and sope49-* packages (x86_64) installed from "stable" Inverse YUM >> repository. >> I have strange messages in log: " ... [SoWebDAVRenderer]> got bogus port >> information from webserver: ..." (not labeled as [ERROR]), >> and some other, which are "common": >> [ERROR] <0x0x7fc2a6550a28[NGLdapAttribute]> could not convert value of >> objectGUID to string >> [ERROR] <0x0x7fc2a6688028[NGLdapAttribute]> could not convert value of >> objectSid to string >> >> >> >> On Wed, Mar 5, 2014 at 11:22 AM, Christian Mack < >> [email protected]> wrote: >> >>> Hello djordje crni >>> >>> Am 2014-03-04 23:56, schrieb djordje crni: >>> > Free-busy lookup doesn't work after upgrading SOGo to v2.2.0. >>> > I downgraded back to v2.1.1b, and it works OK. >>> > Sogo and mamcached are stopped before upgrade and started later. >>> > >>> >>> Sorry, but I can not reproduce this. >>> On what OS are you? >>> Did you use packages, or compile it yourself? >>> Do you get any error messages in sogo.log? >>> >>> >>> Kind regards, >>> Christian Mack >>> >>> -- >>> Christian Mack >>> Abteilung Basisdienste >>> KIM IT-Services >>> Universität Konstanz >>> >>> >> > -- [email protected] https://inverse.ca/sogo/lists
