Timeout in ESPOcrm, need to restart Webservice

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

[nebulon]

This maybe a similar issue as https://forum.cloudron.io/topic/10364/nextcloud-is-down-one-in-a-while-and-needs-to-be-restarted-manually/2?_=1705425220470

Can you try to increase the MaxRequestWorkers in the mpm_prefork.conf file and restart the app?

[p44]

@nebulon It was 6, now I increased to 36. Let's see what happen...

[p44]

@nebulon Finally it works... thank's a lot for your advice. Just to learn more, about this value, what is the best to set? Also, I noted your previous comment:

«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», did you not apply this fix, or maybe I had an old value coming from old version?

Thank's again

[nebulon]

Correct the package for newly installed instances will contain the higher value, but since it is a user-configurable persistent file, a package update will not auto-adjust this value.