Messages

1

Installation and Upgrades / [solved] sogo unavailable after upgrade to Zentyal 5 (503 Service Unavailable)

« on: July 02, 2017, 04:16:13 pm »

Hi,

Sogo isn't working after I upgraded to Zentyal 5. When I try to access https://myserver/SOGo I get a 503 Service Unavailable error. ActiveSync is also not working (it is enabled in Zentyal).

I tried to reinstall sogo en the activesync component (and restarted afterwards), but that didn't change anything.

I don't see a clear error message in my log files, but I dont know what to make of this line in my ssl-error.log:

Code: [Select]

[Sun Jul 02 16:09:05.544929 2017] [proxy:error] [pid 6962:tid 140255713818368] (111)Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:20000 (127.0.0.1) failed
[Sun Jul 02 16:09:05.544996 2017] [proxy:error] [pid 6962:tid 140255713818368] AH00959: ap_proxy_connect_backend disabling worker for (127.0.0.1) for 60s

It seems sogo isn't accepting connections, but it is running. "service sogo status" gives me this:

Code: [Select]

● sogo.service - LSB: SOGo server
   Loaded: loaded (/etc/init.d/sogo; bad; vendor preset: enabled)
   Active: active (exited) since Sun 2017-07-02 16:03:50 CEST; 10min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 7044 ExecStop=/etc/init.d/sogo stop (code=exited, status=0/SUCCESS)
  Process: 7114 ExecStart=/etc/init.d/sogo start (code=exited, status=0/SUCCESS)

Jul 02 16:03:49 waswolk systemd[1]: Stopped LSB: SOGo server.
Jul 02 16:03:49 waswolk systemd[1]: Starting LSB: SOGo server...
Jul 02 16:03:49 waswolk sogo[7114]:  * Starting SOGo sogo
Jul 02 16:03:49 waswolk sogo[7114]: 2017-07-02 16:03:49.996 sogod[7187] File NSData.m: 162. In readContentsOfFile Open ((null)) attempt failed - bad path
Jul 02 16:03:50 waswolk sogo[7114]:    ...done.
Jul 02 16:03:50 waswolk systemd[1]: Started LSB: SOGo server.
Is the error maybe perhaps a clue? Google doesn't give me much for that. I'm at loss at what I can do, so any input is welcome.

update:
I reinstalled sogo a few times. First without any result, but the trick apparently was to do a purge and a reboot before i reinstalled it. Worked afterwards. I do get the error sometimes again when I make minor changes to the configuration file, so it seems a delicate balance.

2

Contributions / Tips&Tricks / Features Requests / Re: Zentyal dead or alive ?

« on: October 08, 2016, 05:36:48 pm »

There seems to be some signals of life again: The Zentyal Twitter account just tweeted that Zentyal 5 will be released in november! I'm already excited

3

Installation and Upgrades / cant get autodiscover to work (case sensitive url)

« on: February 27, 2016, 01:40:02 pm »

I can't get the autodiscover function to get to work. My SSL certificates are in order, but it seems to get stuck on the upper/lowercase (a/A) stuff of the url. I understand the Zentyal autodiscover files somehow only work when the url has a lowercase a in them. So

https://domain.tld/autodiscover/autodiscover.xml gives the xml file with the 600 error that I should get, but https://domain.tld/Autodiscover/Autodiscover.xml gives some sort of error file.

Everything shows up green in https://testconnectivity.microsoft.com/ except for when it tries to pull up the autodiscover.xml file.

I tried to follow this post to make a directory Autodiscover and redirect with htaccess

Code: [Select]

mkdir /var/www/html/Autodiscover
echo "RedirectMatch 302 (?i)^/Autodiscover/(.*)$ https://xxx.yourdomain.com/autodiscover/autodiscover.xml" > /var/www/html/Autodiscover/.htaccess

But this doesn't seem to do anything, which i suspect has to do with the fact that urls that contain the word autodiscover get redirected, possibly by the line ProxyPassMatch in the stub apache-ocsmanager.conf.mas

   ProxyPassMatch /[Aa]utodiscover(.*)$ http://127.0.0.1:5000/autodiscover$1

Next I tried to make it work through the autodiscover subdomain option (described here ). I cancelled out the following line in the stub apache-ocsmanager.conf.mas

    ServerAlias autodiscover.<% $domain %>
   
to be able to make an autodiscover subdomain and have a directory for it in /var/www/ with an .htaccess in it to direct it by

Code: [Select]

Redirect 301 / https://domain.tld:443/autodiscover/autodiscover.xml

This doesn't seem to work as well. I get the appropriote xml file with the 600 error, but when I analyse it with the testconnectivity tool from microsoft it says the following:

An HTTPS redirect was received in response to the Autodiscover request. The redirect URL is https://domain.tld:443/autodiscover/autodiscover.xmlAutodiscover/Autodiscover.xml.

It seems to go wrong with the redirect (hence the double Autodiscover in the url), which i suspect, again, has something to do with this line in the stub apache-ocsmanager.mas

ProxyPassMatch /[Aa]utodiscover(.*)$ http://127.0.0.1:5000/autodiscover$1

But i don't know what i need to change.

Any ideas?