Mar 20
4 / 4
Mar 26
12d ago
amorel
16d
1

Dear egw forum,

Our File Manager has several directories, one of which contains 10,000+ documents.
Since the last update, we’ve been getting an error WEBDAV-syncing this directory
It works up to 3,500 files, but not beyond that.
Here’s the error message.

egroupware-nginx | 2025/03/13 07:36:44 [error] 21#21: *3961 FastCGI sent in stderr: "PHP message: PHP Fatal error: Maximum execution time of 210 seconds exceeded in /usr/share/egroupware/api/src/Mail/Credentials.php on line 627" while reading response header from upstream, client: 172.19.0.1, server: _, request: "PROPFIND /egroupware/webdav.php/home/xxx/yyy/zzz/ HTTP/1.1", upstream: "fastcgi://172.19.0.4:9000", host: "xxx.yyy.zzz"

Increasing egw_memory_limit or egw_max_execution_time or egw_apc_shm_size had no effect

Which version : 23.1.20250307
Installation type : egroupware-docker installation
Which module : webdav
Does the error occur after an update/upgrade : since the last update (Back to version 23.1.20250113: everything works fine)
During which action does the error occur : external webdav sync (tried with our own client + windows client)

Any help would be appreciated

Alex

RalfBeckerEGroupware GmbH
16d

I wonder how the timeout happen in api/src/Mail/Credentials.php in a WebDAV PROPFIND request.
That is really strange …

Problem with PHP Fatal: Maximum execution time exceeded is, that you can’t get a trace from it (like an exception), but setting a higher max_execution_time (`EGW_MAX_EXECUTION_TIME environment variable in your docker-compose.override.yml) should give you more time, which either leads to the PROPFIND to succeed, or fail again with no further clue :frowning:

I looked yesterday into a similar case with WebDAV, exceeding a 30 second timeout, with just 170 folders in a collection. The strange thing is: the time spend in the VFS backend function for the directory listing is a fraction of a second.

I wonder if that’s a recent PHP problem somehow.

A user on the German forum had a wired LDAP problem, which turned out to be related to the PHP version of the package and which is supposedly fixed in the las PHP release, so you could give updating PHP a try:

docker exec -it egroupware bash
apt-get update && apt-get upgrade -y
exit
docker restart egroupware

Let me know if that helped.

Ralf

amorel
15d

Hi there
I tried PHP update
I also tried to push today’s egw version
with same issue on large directory
Alex

StefanUEGroupware GmbH
12d

Hi amorel.

You may also find more information in the WebDAV log. Under certain circumstances it may also be cancelled because there is a problem with a file(?)…

Stefan