Timeout in ESPOcrm, need to restart Webservice
-
@robi yes, but it was in "running" state... I increased resources to a VPS and now seems to be stable... very strange...
-
@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
-
@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 exceededHow I can understand what's happening?
Rebooting I got: "server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting", maybe is this?
-
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 thempm_prefork.conf
file and restart the app? -
@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
-
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.