Topic: Latest upgrade and Sogo

[dalex]

After the latest upgrade, Sogo refused to start. After a a search, i re-installed the package as suggested (to get the latest Sope packages).

Sogo started but shows a broken 1st page (login) and goes no further from there.

I tried to erase the Sogo database and re-install, but still the same result. I suspect PHP53 (broken my VegaDNS already..).

Anyone else with Sogo installed please?

[cactus]

You should find out the error in the log files. Did you already check your webserver logfiles? You can also use this perhaps: http://wiki.contribs.org/PHP#Display_Error_Messages

[Franco]

Yes, you can fix it by editing /etc/e-smith/templates/etc/httpd/conf/httpd.conf/85SOGoAccess

the PATH should be; /usr/lib/GNUstep/

Code: [Select]

# SOGo Groupware
{
    $sogoStatus = $sogod{'status'} || "disabled";
    $webmailStatus = $imp{'status'} || "disabled";

    $OUT = "";

    if (($webmailStatus eq 'disabled') and ($sogoStatus eq 'enabled')) {
        $OUT = "Redirect /webmail https://${DomainName}/SOGo";
    }
}

Redirect /sogo https://{$DomainName}/SOGo

ProxyPass /SOGo http://127.0.0.1:{$sogod{'TCPPort'}}/SOGo
ProxyPassReverse /SOGo http://127.0.0.1:{$sogod{'TCPPort'}}/SOGo

<Location /SOGo>
   order deny,allow
   deny from all
   allow from all
   SSLRequireSSL on
   RequestHeader set "x-webobjects-server-url" "https://{$DomainName}/SOGo"
</Location>

Alias /.woa/WebServerResources/ /usr/lib/GNUstep/SOGo/WebServerResources/
Alias /SOGo.woa/WebServerResources/ /usr/lib/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/ /usr/lib/GNUstep/SOGo/WebServerResources/
AliasMatch /SOGo/so/ControlPanel/Products/(.*)/Resources/(.*) /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2

<Directory "/usr/lib/GNUstep/SOGo/WebServerResources/">
    AllowOverride None
    Options +ExecCGI -Includes
    Order allow,deny
    Allow from all
</Directory>

[dalex]

Just corrected, regenerated the template, restarted httpd, stopped sogo, restored the database from backup, started sogo, and all are in tact.

Thank you very much!

Yes, you can fix it by editing /etc/e-smith/templates/etc/httpd/conf/httpd.conf/85SOGoAccess

the PATH should be; /usr/lib/GNUstep/

[cactus]

Yes, you can fix it by editing /etc/e-smith/templates/etc/httpd/conf/httpd.conf/85SOGoAccess

the PATH should be; /usr/lib/GNUstep/

Code: [Select]

# SOGo Groupware
{
    $sogoStatus = $sogod{'status'} || "disabled";
    $webmailStatus = $imp{'status'} || "disabled";

    $OUT = "";

    if (($webmailStatus eq 'disabled') and ($sogoStatus eq 'enabled')) {
        $OUT = "Redirect /webmail https://${DomainName}/SOGo";
    }
}

Redirect /sogo https://{$DomainName}/SOGo

ProxyPass /SOGo http://127.0.0.1:{$sogod{'TCPPort'}}/SOGo
ProxyPassReverse /SOGo http://127.0.0.1:{$sogod{'TCPPort'}}/SOGo

<Location /SOGo>
   order deny,allow
   deny from all
   allow from all
   SSLRequireSSL on
   RequestHeader set "x-webobjects-server-url" "https://{$DomainName}/SOGo"
</Location>

Alias /.woa/WebServerResources/ /usr/lib/GNUstep/SOGo/WebServerResources/
Alias /SOGo.woa/WebServerResources/ /usr/lib/GNUstep/SOGo/WebServerResources/
Alias /SOGo/WebServerResources/ /usr/lib/GNUstep/SOGo/WebServerResources/
AliasMatch /SOGo/so/ControlPanel/Products/(.*)/Resources/(.*) /usr/lib/GNUstep/SOGo/$1.SOGo/Resources/$2

<Directory "/usr/lib/GNUstep/SOGo/WebServerResources/">
    AllowOverride None
    Options +ExecCGI -Includes
    Order allow,deny
    Allow from all
</Directory>

You should not fix the original template as this will be overwritten on updates. You should create a custom-template fragment instead as an override of the default settings.

[dalex]

Isn't it responsibility of smeserver-sogo package makers?

In the next version of the package the corrections should be incorporated. It's not a customization to put in templates-custom, it's a functional thing.

Anyway i kept a backup copy of both fragments.

[Stefano]

it will be incorporated if you open a bug in bugzilla..

since then, you should make your editing in templates-custom dir

[hpg1953]

Hello,

I have updated Sogo and have the same Problems. After reinstall Sope I can start SOGo on the Server. But if I want to access the SOGo Server from a Client (https://ourserver/SOGo) I get the message that the service is not available.
I modifed the template 85SOGoaccess as described. Without success.
 ERROR logfile:

111 Connection refused: proxy HTTP:attempt to connect to 127.0.0.1:20000 (127.0.0.1) failed
ap_proxy_connect_backend disabling worker for (127.0.0.1)

Whats wrong now? Can you help me

regards