Hello Jan,thank you for your reply. I couldn't tell if there is similarities with the issue you encountered but, like in your case, we noticed that after a restart of sogo the first loading is fine (but then it's randomly either fine or a blank page).
Anyway, this is quite weird and no hints on our side till yesterday :| Le 06/02/2020 à 22:41, Jan Laufik ([email protected]) a écrit :
Hello Daniel,this looks similar as the problem I'm experiencing at one of our customers with CentOS 7 and Apache web server. Even though I'm using the same configuration on other servers too, I wasn't able to reproduce same behavior elsewhere, so I ended up with the script, that parses the log file and restarts SOGo automatically, when error appears. Originally I thought, that the problem was somehow connected with not expiring sessions from the database table, but that wasn't the case. You can find my original post here: https://lists.inverse.ca/sogo/arc/users/2019-08/msg00017.htmlJanOn Thu, Feb 6, 2020 at 3:15 PM Daniel Le Bray <[email protected] <mailto:[email protected]>> wrote:Hello, we're using the nightly build of SOGo (package version 4.3.0.20200123-1) with nginx (package version 1.14.1-1~bpo9+1) on Debian Stretch without any issue. On our test machine, we upgraded the system to Buster, only nginx has changed at a minor level (package version 1.14.2-2+deb10u1) and *no* config changes have been made either to SOGo or nginx. And now, on Buster, we have a weird behaviour of SOGo: either it works flawlessly as it should or we have a blank page! The reason of the blank page can be easily spotted: some resources cause a 404 error for they use a "/.woa/..." URI instead of a "/SOGo.woa/..." URI. So the main question is: why are those URIs wrong from time to time? This is quite random, sometime all is ok and whenever you refresh it fails. Is this something anybody else has? Is there some kind of explanation regarding the wrong URI (.woa instead of SOGo.woa)? Here is the URI when we got a blank page: (at top of the page) <link href="/.woa/WebServerResources/img/sogo.ico?lm=1580900408" rel="shortcut icon" type="image/x-icon" /> <link href="/.woa/WebServerResources/css/theme-default.css" rel="stylesheet" type="text/css" /> <link href="/.woa/WebServerResources/css/styles.css" rel="stylesheet" type="text/css" /> (at the bottom of the page) <script type="text/javascript" src="/.woa/WebServerResources/js/Main.js?lm=1580900408"></script> <script type="text/javascript" src="/.woa/WebServerResources/js/Common.js?lm=1580900408"></script> Any help or feedback will be appreciated-- Daniel Le Bray :: CRI :: Pôle Systèmes et Réseaux[email protected] <mailto:[email protected]> :: +33 (0)2 32 74 42 94 Universite Le Havre Normandie 25 rue Philippe Lebon, BP1123, 76063 Le Havre Cedex, France ========================================================== J'accepte les emails VSRE (http://vsre.info/index_fr.html) -- [email protected] https://inverse.ca/sogo/lists
-- Daniel Le Bray :: CRI :: Pôle Systèmes et Réseaux [email protected] :: +33 (0)2 32 74 42 94 Universite Le Havre Normandie 25 rue Philippe Lebon, BP1123, 76063 Le Havre Cedex, France ========================================================== J'accepte les emails VSRE (http://vsre.info/index_fr.html)
smime.p7s
Description: Signature cryptographique S/MIME
