On May 4, 2018 8:18:21 AM EDT, Christian Mack <[email protected]> wrote: >Am 04.05.2018 um 13:35 schrieb "Fabian A. Santiago" >([email protected]): >> On May 4, 2018 3:54:25 AM EDT, Christian Mack <[email protected]> wrote: >>> Am 03.05.2018 um 14:28 schrieb "Fabian A. Santiago" >>> ([email protected]): >>>> On May 3, 2018 2:12:05 AM EDT, Christian Mack <[email protected]> >wrote: >>>>> Am 02.05.2018 um 13:25 schrieb "Fabian A. Santiago" >>>>> ([email protected]): >>>>>> On May 2, 2018 3:16:03 AM EDT, Christian Mack <[email protected]> >>> wrote: >>>>>>> Hello >>>>>>> >>>>>>> Am 30.04.2018 um 21:51 schrieb "Fabian A. Santiago" >>>>>>> ([email protected]): >>>>>>>> April 12, 2018 9:52 PM, "Fabian A. Santiago" >>>>>>>> <[email protected]> wrote: >>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>> I'm running sogo along with dovecot and postfix with a mysql >>>>>>>>> (mariadb 10.2.14) backend on centos >>>>>>>>> 7.4. >>>>>>>>> >>>>>>>>> it all used to work just fine. >>>>>>>>> >>>>>>>>> problem started when i attempted to update using the v4.x >>> nightly >>>>>>>>> builds repo from v3.x. >>>>>>>>> >>>>>>>>> i updated my repo address, ran yum update, executed the db >>> update >>>>>>>>> shell script, restored my >>>>>>>>> original conf files, and then on attempted restart, the >service >>>>>>>>> times out and fails to start. >>>>>>>>> >>>>>>>>> my strace of the attempted start is here: >>>>>>>>> >>>>>>>>> https://pastebin.com/GY6hag4b >>>>>>>>> >>>>>>>>> the log file is also not being written either at this point. >>> there >>>>>>>>> is no log since the upgrade. >>>>>>>>> >>>>>>>>> I've since tried reverting to v3.x, restored a pre-update db >>>>>>>>> backup, >>>>>>>>> and still the service fails to >>>>>>>>> start. something got hosed up but i'm unsure of where to look. > >>>>>>>>> >>>>>>>>> I'm at a loss at this point and am looking for any help i can >>> get. >>>>>>>>> thanks. >>>>>>>>> >>>>>>>> >>>>>>>> (Bump) >>>>>>>> >>>>>>>> I haven't heard back from anyone on this issue. Does anyone >have >>>>>>>> any >>>>>>> ideas? Or where to even start looking? Thanks. >>>>>>>> >>>>>>> >>>>>>> I assume you checked that your maria DB is running. >>>>>>> Did you check, if the SOPE packages are up to date and from the >>>>>>> Inverse Repo? >>>>>>> >>>>>> >>>>>> Yes to all. I have other services on this box using the DB (such >as >>>>>> email) and all else is fine. All packages did come from the >>> official >>>>>> nightly repo. >>>>>> >>>>> >>>>> Did you enable AppArmor or SELinux? >>>>> >>>>> >>>> >>>> No I didn't. Haven't changed anything since I ran 3.x successfully. > >>> When reverting to V3, did you also remove all SOPE and GNUstep >packages >>> before installing sogo V3? >>> >>> >>> Kind regards, >>> Christian Mack >> >> Yes > >As all those packages are matching, I assume you run out of memory. >Could you try to reduce the number of workers before start (=PREFORK) >in >/etc/sysconfig/sogo? > > >Kind regards, >Christian Mack
I will try that when I have time and will post the result. But I used to run sogo just fine with the same config. Just so I know, what's your reason for believing I could be running out of memory now? I'm just trying to educate myself is all. I will try it. Thanks for your suggestions. -- Fabian A. Santiago OpenPGP: 0x643082042dc83e6d94b86c405e3daa18a1c22d8f (current key) 0x3c3fa072accb7ac5db0f723455502b0eeb9070fc (to be retired / revoked) -- [email protected] https://inverse.ca/sogo/lists
