@nprofile1q... Yes maybe one someone else has the answer.
Maybe not more than the memory limit?

Is this the import size of one item or one request?

@nprofile1q... I deleted the Task "UpdateServerPeers" that was not done since long time, and the worker succeeded.
This is about finding connected node, i guess?


Perhaps these are very large files, such as a video or something similar, that are being accessed... In my case, my first guess is that something was subscribed to via RSS feed by a user, since this blog - as far as I can see - does not use Activity Pub...

In local.config.php there is the setting:
<?phpreturn [
'config' => [
//'max_import_size' => 0, //UNLIMITED; DANGER!
//'max_import_size' => 400000000,
'max_import_size' => 5 * 1048576,
],
];

I am not sure about the reasonable import size to set there?

@nprofile1q... Thank you Jools, that helped me!
I does not know anything about blog.estela.moe but had a similar problem with another instance before.
I remembered to run this SQL query:
SELECT * FROM `workerqueue` where `pid`<>0 AND done=0;


It seems like sometimes the worker hangs on the command "UpdateServerPeers".
The instance can be different, now in worker it is community.uncensoredwisdom.com.
Maybe a bug?
I try now running the server again, and eventualy deleting this task. This takes some minutes, mom...

Updated to the new stable version.
Running bin/console.php worker throws
Die Aufgabe ".../bin/console.php" wurde in 1247 Sekunden abgeschlossen, jedoch traten Fehler aufPHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 601882656 bytes) in /.../vendor/guzzlehttp/psr7/src/Utils.php on line 91
PHP Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 803209248 bytes) in /../vendor/guzzlehttp/psr7/src/Utils.php on line 91

That is a huge amount of memory, or???

Can I do anything to reduce the amount of memory the worker consumes, bzw. is this normal?

Testing now with
ini_set("memory_limit","2048M");

And result:
PHP Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 1608515616 bytes) in

It seems there must be anything wrong?
Thanks for help!

SELECT * FROM `workerqueue` WHERE `done`=0 AND `pid`>0; hat 3 Jobs gezeigt die "fest hingen", UpdateServerPeers Jobs. Habe die gelöscht, nun läuft der Worker wieder weiter.

Error Message from worker:
PHP Fatal error: Allowed memory size of 4294967296 bytes exhausted (tried to allocate 2145386528 bytes) in /../vendor/guzzlehttp/psr7/src/Utils.php on line 91


Thats a big amount of memory?
With
ini_set("memory_limit","4096M");


at the beginning of worker.php that is not enough?
What can I do, e.g. to get the job consuming so much memory?

@nprofile1q... @nprofile1q...
@nprofile1q... nice. also fwiw:dir.friendica.social/servers
friendica.fediverse.observer/l…
#Friendica


startdir.de/software/?software… 😉

@nprofile1q... Es hängt von dem Gerät ab: Einige Bilder werden bei mir auf dem Notebook angezeigt, aber oben beschriebener Fehler erscheint auf dem Handy.
Bei anderen Bildern scheint es umgekehrt!?!

Beispielbeitrag 1: inne.city/display/f37824e8-166…
Beispielbeitrag 2: inne.city/display/f37824e8-166…

@nprofile1q...
Gerne! Im Modul unten kannst du noch den Upload für Videos einstellen. Der hinterlegte Wert sollte kleiner sein, als der Wert der php.ini.


Sorry, weiß grad nicht was Du mit "im Modul unten" meinst...?
Oder meinst Du eben "die grüne" Einstellung?

@nprofile1q... Danke Matthias!
Habe da jetzt auch 10m stehen.
Sorry, habe erste jetzt den grünen Balken als input element entdeckt, dachte bis grade das wäre nur eine readonly Anzeige 🙈
Ah 🙈