Le 08/04/2026 à 10:33, Jacques Le Roux via dev a écrit :
Le 08/04/2026 à 09:55, Jacques Le Roux via dev a écrit :
Le 07/04/2026 à 17:59, Jacques Le Roux via dev a écrit :
Le 07/04/2026 à 15:26, Jacques Le Roux via user a écrit :
Hi,
I don't know why and I have no time to look at it right now (I could restart)
Trunk demo is OK
Jacques
I downloaded the ofbiz. log file (393 MB) but did not find any reasonable
explanation, but a lot of session destroyed (~100) in the last hour.
After that, only the sending emails job continued to work for almost an hour
and a half.
Also ~100 session destroyed in the last hour does not mean much,. Since the
start there are 31000+ such cases.
But what is weird is the start was 2026-02-17. So something is wrong with logs
rotation since this date and it continues. It's OK before.
Maybe the reason of the crash?
I restarted the demos.
Jacques
I had a look at log4j2.xml (not changed for 2 years) and docker-compose.yml
that has not related changes.
I also had a look at the Git log of tools\demo-backup\ofbizdocker, nothing. But I'm not quite sure that changes on repo are exactly the same than
on VM (hard to compare).
Finally the same thing happen for all demo instances for all logs.
As I don't understand what's happening, I'll stop demos, rename the logs
affected (to keep them) and restart demos to see tmrw if it has an impact.
Jacques
The demos were restarted but no new logs were created (ie no error.log and
ofbiz.log).
I created error.log and ofbiz.log files in trunk to no avail, they remain empty.
We clearly have an issue with logs.
I don't know docker, so it seems I'm missing something... Help appreciated...
Jacques
As a last try, I restarted the demos again, same situation.
Also all the access logs stopped around 27/Mar/2026:23:59:16
Jacques
