Skip to main content
I get a message that the worker didn't run for a few day in /admin, I didn't change anything, the daemon is running (I restarted it too) and I started /bin/worker.php from cli. Still I get this message.

Any ideas?

I think the post from social.yl.ms will take forever to be distributed, so here is another one from squeet.me.
!Friendica Support # @utzer
#friendica @utzer [Friendica] !Friendica Support
utzer (on squeet.me)
Me again, I will have a look into the logs in 2 hours, just went to the sauna an let the problem be... Will fly to UK and at the airport I will have time for checking logs.

But still any tip is welcome to help me find the problem.
This entry was edited (5 years ago)
utzer (on squeet.me)
I get a lot of those:
[18-Aug-2019 17:14:18 Europe/Berlin] PHP Warning:  sem_get(): failed for key 0x662bf0dd: No space left on device in /srv/http/src/Core/Lock/SemaphoreLock.php on line 41
[18-Aug-2019 15:14:24 UTC] PHP Warning:  sem_get(): failed for key 0x662beae5: No space left on device in /srv/http/src/Core/Lock/SemaphoreLock.php on line 41


in the PHP error log.
utzer (on squeet.me)
OK, it seems for now I solved it with a reboot, but I would love to get a better solution. Why is Friendica holding so many semaphores and how many should be sufficient as a setting?
Philipp Holzer
I reverted some changes about semaphore which I added. They introduced some regressions, so with the current develop branch, it should work again..
utzer (on squeet.me)
@Philipp Holzer but was it a problem that cause lots of semaphore usage exceeding previous numbers?

@utzer
@Philipp Holzer @utzer [Friendica]

This website uses cookies to recognize revisiting and logged in users. You accept the usage of these cookies by continue browsing this website.

⇧