hello ralf,
 
today  i upgraded to Version 3.2.10 (@shiva.inverse 201707070648) and do not face such problems.
 
one difference between our installations is the fact that our installation is based on postgresql while yours seems to be based on mysql. are there any hints in the mysql logs?
 
regards, sggs
 
Sent: Friday, July 07, 2017 at 11:05 AM
From: "\"Ralf Cirksena\" (c...@holmco.de)" <users@sogo.nu>
To: "Christian Mack" <users@sogo.nu>
Subject: Re: [SOGo] Web: Unable to save settings
On Fri, Jul 07, 2017 at 10:12:27AM +0200 you wrote:

> Am 06.07.2017 um 15:23 schrieb Ralf Cirksena (c...@holmco.de):
> > Hello,
> >
> > today we updated SOGo from 3.2.9 to 3.2.10. Now $USER cannot save
> > preferences. Error message: "Service temporarily unavailable".
> >
>
> Please check, that you also have upgraded your sope packages.


Start-Date: 2017-07-06 12:12:07
Commandline: apt-get upgrade
Upgrade: sope4.9-libxmlsaxdriver:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), sope4.9-dbg:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), sope4.9-stxsaxdriver:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), sogo:amd64 (3.2.9-1, 3.2.10-1), libsope-xml4.9:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), libsbjson2.3:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), libsope-appserver4.9:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), sogo-activesync:amd64 (3.2.9-1, 3.2.10-1), libsope-mime4.9:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), sope4.9-gdl1-mysql:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), libsope-ldap4.9:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), sogo-dbg:amd64 (3.2.9-1, 3.2.10-1), libsope-gdl1-4.9:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705), libsope-core4.9:amd64 (4.9.r1664.20170509, 4.9.r1664.20170705)
End-Date: 2017-07-06 12:14:31


Regards
--
R. Cirksena
--
users@sogo.nu
https://inverse.ca/sogo/lists
--
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to