Errors logs to identify issues

[vladimir.d]

Hi everyone,

I've faced with an issue when I get EspoCRM app frozen but there is nothing in logs.
I inspected:

1. /app/data/data/logs/espo-2021-06-10.log

2. Full App logs downloaded from the container logs console

3. mysql logs in the mysql docker container on the cloudron host

What did I miss? Are Apache Error logs directed to stdout and to Full App logs?

[nebulon]

@vladimir-d have you tried to restart the app? Otherwise if the problem is still there without any clue in the logs, I guess we have to debug that on your Cloudron directly.

[vladimir.d]

Yes, we are restarting the app when it gets frozen, sometimes we restart it every 5 minutes, sometimes one in an hour, it depends on the user activity.

[nebulon]

@vladimir-d what is the behavior when the app is frozen? Are requests erroring or are there any errors reported in the browser inspector tools?

[vladimir.d]

@nebulon said in Errors logs to identify issues:

inspector tools?

Nothing in logs but get JS error in the console

Behavior is that when it gets frozen, the page refreshes fine but no data loaded, the Loading... message doesn't disappear.

[nebulon]

Just to give a small update. We have it pinned down to the apache process not serving any more requests. Not sure what the exact issue is, yet.

[vladimir.d]

Well, we figured out that there were not enough system resources so apache was dying unexpectedly. BTW, the Graphs tab did show nothing. We increased CPU app limits significantly up to 75% so we get much less freezes now.

Also we implemented a Node-Red workflow to monitor actual healthstatus of the application using EspoCRM API and submit notifications to a messenger app in case of failure.

All of that doesn't resolve the issue but allows us to keep the system running somehow by restating the app services manually.

[marcusquinn]

@vladimir-d Still need to see errors printing to logs when it does still occasionally happen. Let's keep this thread open for solving that.