OTRS6 Database Crash Due to Memory Loss

Community, We are currently running on the version otrs-6.0.14-01.noarch. We are getting weekly crashes where the database locks up due to being out of memory. Is this happening to anyone else? Is there a possible fix to this issue? Current set up OS: Cent OS 7.5 Memory:12 GB Database: MariaDB-compat-10.2.18-1.el7.centos.x86_64 MariaDB-client-10.2.18-1.el7.centos.x86_64 MariaDB-common-10.2.18-1.el7.centos.x86_64 MariaDB-server-10.2.18-1.el7.centos.x86_64 OTRS version otrs-6.0.14-01.noarch Issue: DB locks up, CPU locks up. Once DB is restarted, app is fine [1311431.213740] Out of memory: Kill process 8902 (/opt/otrs/bin/c) score 5 or sacrifice child [1311431.214649] Killed process 8902 (/opt/otrs/bin/c) total-vm:451892kB, anon-rss:33636kB, file-rss:268kB, shmem-rss:8kB Happens once a week Thank You, Johnnie Rucker

Hi Johnnie,
On Apr 24, 2019, at 6:08 PM, Johnnie Rucker
wrote: [1311431.213740] Out of memory: Kill process 8902 (/opt/otrs/bin/c) score 5 or sacrifice child [1311431.214649] Killed process 8902 (/opt/otrs/bin/c) total-vm:451892kB, anon-rss:33636kB, file-rss:268kB, shmem-rss:8kB
The kernel’s Oom killer is usually a good indicator that either you should add more memory or you the configuration needs to be adjusted. I had the experience most of the time with Apache’s httpd or the database. Did you have some kind of resource monitoring regarding the memory consumption of the specific services? Kind regards, Roy
participants (2)
-
Johnnie Rucker
-
Roy Kaldung