Skip to main content
!Friendica Support
Again I am getting kill messages about the worker

Killed php bin/worker.php

Friendica 'Interrupted Fern' 2024.12 - 1576
php 8.3.10
max parallel running worker: 5

Seems that worker is taking too much RAM and the system (Shared Hoster) is killing the proczess.
Frend
It might be helpful if you share your full params of current worker-settings
Hiker
Here we go.
Frend
Nothing out of the ordinary here, you could try reducing to less workers but I don't think that will help much. Are you running worker via crons or daemon?

I am running through different hosters (dedicated rack, kvm and also shared hosters) and my hoster does specify things like php process limit, memory limit, script runtime etc...

maybe you can get some more information from your hoster?
This entry was edited (3 months ago)
Michael 🇺🇦
When its a shared hoster, it might be the case that they have defined a maximum runtime for PHP processes.
Hiker
How much time do you suggest?
Michael 🇺🇦
Endless for background processes.
Hiker
The question was about the worker - is it endless as well? "Endless" isn't possible on a shared hoster.
Michael 🇺🇦
Worker processes (cleanup for example) can easily run for an hour.
Hiker
So you tell me that to install #Friendica on a shared hoster is a bad idea? Well, root servers are not in my budget.
#friendica
Michael 🇺🇦
Shred hosters can be problematic, yes.
Frend
some very strict webhosters go with 30-60s and then there are webhosters that have like 300-600 seconds. It really depends on your webhoster and the tier/package that you bought. Ask the support or try to find this information in your webhosters package description
Hiker
I could set it now to 120s - let's see if I will get still these kill messages.
Hiker
It could also be a problem with too less memory (RAM).
Hiker
Ok, perhaps the problem is solved with more RAM and longer time in php.ini.
Hiker
No,I didn't - the kill messages are back again.
Frend
All that can be really advised is to check with your hosting provider for shared webspace. Once we have exact rules or limits we can actually try to work around these. Everything else is just a shot in the dark and not really helping much.
Hiker
The worker kill problem turns out to be a database problem - error log:

Index post-tag is corrupted

How to fix this?
Hiker
Recreated the table - database error message stopped.
Hiker
From both hoster I got the notice that the php execution time is not the problem but the process takes too much RAM.
Rainer "friendica" Sokoll
Do you have messages from the OOM killer in the host's log?
Hiker
I have only logs like this from the provider

Feb 05 11:21:20 xyz.server.de kernel: Killed process 22932 (php), UID 153, total-vm:1443352kB, anon-rss:777172kB, file-rss:19936kB, shmem-rss:12472kB
⇧