error occurred whilst communicating with the server (only on admin logins)

error occurred whilst communicating with the server (only on admin logins)

by Francis Lorenzo Guingao Doydora -
Number of replies: 1

Good day everyone,

I was hoping you could help me with this error and how to go about fixing it.

This only appears when I login with admin account and it happens intermittently. After said error occurs, I'm redirected back to the login page. So far, no news of students or faculty experiencing this issue.

Attached are images of said error.

Moodle version: 3.9.6+ (Build: 20210330) (2020061506.01)

OS: Ubuntu 20.04

Webserver: Apache

Database: MySQL 8

PHP: 7.4

Moodle was installed in our inhouse data center.

Attachment image (2).png
Attachment image.png
Average of ratings: -
In reply to Francis Lorenzo Guingao Doydora

Re: error occurred whilst communicating with the server (only on admin logins)

by Francis Lorenzo Guingao Doydora -
Okay, so I turned on debugging and saw this error.

[Thu Apr 15 10:58:42.154633 2021] [proxy_fcgi:error] [pid 863360:tid 140159806859008] [client 10.5.1.179:50150] AH01071: Got error 'PHP message: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 602112 bytes) in /var/www/html/moodle/cache/stores/redis/lib.php on line 664', referer: https://elearn.xu.edu.ph/admin/search.php

Checked further and saw that calendar and timeline were causing the memory exhaustion. This only happens in the admin account as all activities are loaded in the admins calendar when viewing the dashboard. This error does not appear in students/faculty for now.

10.5.1.179 - - [12/Apr/2021:16:47:12 +0800] "POST /lib/ajax/service.php?sesskey=EeMGf4zqZA&info=core_calendar_get_calendar_monthly_view HTTP/1.1" 500 324 "https://elearn.xu.edu.ph/admin/search.php" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36"

Searched Google and it led me to the solution of increasing memory_limit = 128M to something like 256M. Question is, is it safe to implement in production and would it cause any problems down the road? Is the memory_limit bump substantial and would it double the memory consumption of apache and php-fpm?
Average of ratings: -