Re: [SOGo] [urgent] SOGo object not found index
On 07/12/2016 05:04 PM, Christian Mack (christian.m...@uni-konstanz.de) wrote: > Hello > > Am 07.07.2016 um 09:20 schrieb Pablo Abelenda (pabele...@igalia.com): >> Hi, >> >> I've been hit by this issue. My SOGo instance stopped to work. It shows >> >> object not found: SOGo => index >> >> Logs are full of: >> >> {{{ >> Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find >> MainUIProduct class! >> Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find locale for >> language: Dutch >> [...] >> Jul 07 09:17:26 sogod [12176]: 192.168.10.81, 192.168.10.13 "GET >> /SOGo/index HTTP/1.1" 404 34/0 0.069 - - 912K >> }}} >> >> Any clues? >> > > Those "did not find locale for language..." are normal for languages not > installed on your server. > You can therefore ignore those. > > Those "did not find MainUIProduct class!" I have never seen before. > Seems as if sogod can not access its libraries. > Do you have SELinux enabled? > > > Kind regards, > Christian Mack > I finally found out what was going on. I used to run sogo (version 2.x.x) installed from the official Debian repositories. A couple of months ago I switched to the Inverse repos to upgrade my deployment to the 3.x.x versions. I thought everything coming from the Debian repos was purged long ago, but sogo-common did not, so when I (as a routine) cleaned up the server by doing an apt-get autoremove, sogo-common and the files belonging to it, disappeared. Probably this files should belong to the sogo package that Inverse provides, preventing this kind of issues, don't know what you think about. Anyway, apt-get install sogo --reinstall, sorted things out for good. Many thanks for the reply. Best. -- Pablo Abelenda signature.asc Description: OpenPGP digital signature
Re: [SOGo] [urgent] SOGo object not found index
Hello Am 07.07.2016 um 09:20 schrieb Pablo Abelenda (pabele...@igalia.com): > Hi, > > I've been hit by this issue. My SOGo instance stopped to work. It shows > > object not found: SOGo => index > > Logs are full of: > > {{{ > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find > MainUIProduct class! > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find locale for > language: Dutch > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find > MainUIProduct class! > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find locale for > language: French > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find > MainUIProduct class! > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find locale for > language: Spanish > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find > MainUIProduct class! > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find locale for > language: Italian > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find > MainUIProduct class! > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find locale for > language: Portuguese > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find > MainUIProduct class! > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find locale for > language: ptBR > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find > MainUIProduct class! > Jul 07 09:17:26 sogod [12176]: [ERROR] [we-rm] did not find locale for > language: English > Jul 07 09:17:26 sogod [12176]: 192.168.10.81, 192.168.10.13 "GET > /SOGo/index HTTP/1.1" 404 34/0 0.069 - - 912K > }}} > > Any clues? > Those "did not find locale for language..." are normal for languages not installed on your server. You can therefore ignore those. Those "did not find MainUIProduct class!" I have never seen before. Seems as if sogod can not access its libraries. Do you have SELinux enabled? Kind regards, Christian Mack -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416 smime.p7s Description: S/MIME Cryptographic Signature