Timeout in ESPOcrm, need to restart Webservice

[robi]

@girish does it make sense to replace apache with nginx or lighttpd (many other options that are more modern, reliable, lightweight, faster and consume less memory)?

[girish]

Maybe, if we can't get apache to work. Usually upstream always recommends apache, so it's easier for us.

[A Former User]

Memory Limit is set to 1GB ( CPU Shares : 75 %)
Will go to 2GB. I will report when it happend again.

Regards Jens

[A Former User]

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 aux

supervisorctl status web
web RUNNING pid 37, uptime 3 days, 22:12:03

[girish]

@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.

[A Former User]

@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?

[girish]

@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.

[marcusquinn]

We still have the same problem too.

[nebulon]

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

[p44]

Dear all, it seems that I'm experiencing this problem... I can only surf to homepage... I'm on v7.6.3 (Ubuntu 20.04.2 LTS), Espo CRM 8.1.0

[girish]

@p44 anything in the logs?

[p44]

@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

[robi]

@p44 that means it's not running.

[p44]

@robi yes, but it was in "running" state... I increased resources to a VPS and now seems to be stable... very strange...

[robi]

@p44 check the App memory graphs

[p44]

@robi All Memory graphs about Cpu and memory allocations was all ok... even VPS graphs...

[robi]

@p44 Welp, something else crashed then

[p44]

@robi Thank's Robi, I still didn't understand what happened, to be honest... Maybe it was some problem related to VPS... I don't know...

Do you know if (and how) I can force a database rebuild/cleaning with CLI? Thank's again

[robi]

@p44 I'd imagine it happens automatically in Cloudron, and @girish might know for sure.

[p44]

@girish @nebulon I'm still approaching with this problem:

Jan 16 17:57:07=> Healtheck error: Error: Timeout of 7000ms exceeded
Jan 16 17:57:17=> Healtheck error: Error: Timeout of 7000ms exceeded
Jan 16 17:57:27=> Healtheck error: Error: Timeout of 7000ms exceeded
Jan 16 17:57:37=> Healtheck error: Error: Timeout of 7000ms exceeded

How I can understand what's happening?

Rebooting I got: "server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting", maybe is this?