Timeout in ESPOcrm, need to restart Webservice
-
@jensbee4 Ah thanks. I think the issue is that apache gets "stuck". I have seen this happen when I run
stresson the PHP apps as well. For a start, are you able to give the EspoCRM app more memory underResources? How much memory have you given it right now? I think that will mitigate the issue. -
Maybe, if we can't get apache to work. Usually upstream always recommends apache, so it's easier for us.
-
Memory Limit is set to 1GB ( CPU Shares : 75 %)
Will go to 2GB. I will report when it happend again.Regards Jens
-
ESPO hangs again
ps aux:USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 63948 7312 pts/0 Ss+ Oct02 2:10 /usr/bin/python /usr/bin/supervisord --configuration /etc/supervisor/supervisord.conf --nodaemon -i EspoCRM root 37 0.0 0.0 46620 5016 pts/0 S Oct02 0:10 /usr/bin/python /usr/bin/pidproxy /var/run/apache2/apache2.pid /bin/bash -c APACHE_CONFDIR='' source /etc/apache2/envvars && rm -f ${A www-data 38 0.0 0.2 554456 23084 pts/0 Sl Oct02 0:03 /usr/bin/php /app/code/current/websocket.php root 41 0.0 0.3 695028 24060 pts/0 S Oct02 0:25 /usr/sbin/apache2 -DFOREGROUND root 45 0.0 0.0 4672 740 pts/0 S Oct02 0:00 /bin/cat root 46 0.0 0.0 4672 688 pts/0 S Oct02 0:01 /bin/cat root 69 0.0 0.0 18508 2304 pts/1 Ss+ Oct02 0:00 /bin/bash www-data 1065 0.0 0.4 698148 34536 pts/0 S 05:50 0:00 /usr/sbin/apache2 -DFOREGROUND www-data 1068 0.0 0.4 698156 34496 pts/0 S 06:02 0:00 /usr/sbin/apache2 -DFOREGROUND www-data 1078 0.0 0.3 697832 30292 pts/0 S 06:27 0:00 /usr/sbin/apache2 -DFOREGROUND www-data 1088 0.0 0.4 698148 32612 pts/0 S 06:40 0:00 /usr/sbin/apache2 -DFOREGROUND www-data 1091 0.2 0.4 698172 36008 pts/0 S 06:58 0:00 /usr/sbin/apache2 -DFOREGROUND www-data 1102 0.6 0.4 698144 35748 pts/0 S 07:00 0:00 /usr/sbin/apache2 -DFOREGROUND root 1103 0.0 0.0 18508 3404 pts/2 Ss 07:01 0:00 /bin/bash root 1123 0.0 0.0 34404 2908 pts/2 R+ 07:02 0:00 ps auxsupervisorctl status web
web RUNNING pid 37, uptime 3 days, 22:12:03 -
@jensbee4 Thanks. In the latest EspoCRM package (1.14.0), you can now go to File Manager and edit apache/mpm_preform.conf. What you can do is to bump the MaxRequestWorkers to say 20 or so and then restart the app.
-
@girish
OK, will try to change the config.I got following:
root@bcd346e4-22d8-49d4-93fc-89f39a77a693:/app/code/6.0.0# supervisorctl restart webnt size. web: stopped web: ERROR (spawn error) root@bcd346e4-22d8-49d4-93fc-89f39a77a693:/app/code/6.0.0# supervisorctl restart web web: stopped web: ERROR (spawn error) root@bcd346e4-22d8-49d4-93fc-89f39a77a693:/app/code/6.0.0# supervisorctl restart web web: stopped web: started root@bcd346e4-22d8-49d4-93fc-89f39a77a693:/app/code/6.0.0#Is the a log to see something about the spawn error?
-
@jensbee4 said in Timeout in ESPOcrm, need to restart Webservice:
Is the a log to see something about the spawn error?
Yes, it's all redirected to stdout. So you can see it in the cloudron logs view.
-
We still have the same problem too.
-
Most likely this was also related to the apache max worker count setting https://httpd.apache.org/docs/2.4/mod/mpm_common.html#maxrequestworkers
For next release we will put this as the default to 256 while one can still configure a higher value if needed in the prefork config in /app/data
-
N nebulon marked this topic as a question on
-
N nebulon has marked this topic as solved on
-
-
@girish
Jan 11 15:59:37=> Healtheck error: Error: Timeout of 7000ms exceeded
Jan 11 15:59:47=> Healtheck error: Error: Timeout of 7000ms exceeded
Jan 11 15:59:57=> Healtheck error: Error: Timeout of 7000ms exceeded
Jan 11 16:00:07=> Healtheck error: Error: Timeout of 7000ms exceeded
Jan 11 16:00:17=> Healtheck error: Error: Timeout of 7000ms exceeded
Jan 11 16:00:27=> Healtheck error: Error: Timeout of 7000ms exceeded -
