I actually found the issue. Apparently it was a firewall which blocked access to the sieve server. No idea why that would make the preferences work sometimes but not at other times, but once that was fixed there was no issue either with loading or with saving the preferences.
On 23-06-2020 10:06, Daniel Kollmer ([email protected]) wrote: > > Hello all > > I am currently testing an installation of the SOGo 4 nightly build and > I run into an issue with the preferences setting. > > At irregular occasions (but more often than not) I get a 504 Gateway > Time-out from the nginx server. > > All I can see in the logs in terms of error for the session is > > client disconnected during delivery of response for > <WORequest[0x0x56200f1e8210]: > method=GET uri=/SOGo/so/danielk/Preferences app=SOGo rqKey=so > rqPath=danielk/Preferences> (len=26618): > the socket was shutdown > > I have a PREFORK setting for 25 workers and I have enough on them, > also memory is not an issue (I have more than 3G free), and there is > nothing I can see in the database server logs either. > > My system is CentOS 7 with nginx-1.16.1-1.el7.x86_64 and > memcached-1.4.15-10.el7_3.1.x86_64. The database server is on a > separate host, version rh-mariadb102-mariadb-server-10.2.22-1.el7.x86_64 > > Also, I have noticed, that *if* I get to the preferences and I change > something, the Save function does not appear to work in the web > interface. If navigating away from the preferences page, I get a > message that I have unsaved options. Interestingly, even if I choose > "don't save", the options I changed are retained once I get back to > preferences (usually takes one or two tries) > > Could you give me suggestions where to look for solutions for those > issues? > > Thanks in advance. > > Daniel > > -- > [email protected] > https://inverse.ca/sogo/lists -- [email protected] https://inverse.ca/sogo/lists
