Skip to main content

On friendica.utzer.de I got 4000 items in the queue, some of them date back to 16th Feb.

How can I check why these items are still in the queue and not processed? I had briefly upgraded to PHP8, maybe this is the reason, but how can I check what is going on?

!Friendica Support @utzer #Friendica

#friendica @utzer [Friendica] !Friendica Support
utzer [Friendica]
utzer [Friendica]  
•
maybe posts are not set out at all?
Valvin
Valvin  
•
@Admin (of friendica.utzer.de) i've read a quick message about php8 which is not yet compatible with friendica @utzer
@utzer [Friendica] @Admin (of friendica.utzer.de)
utzer [Friendica]
utzer [Friendica]  
•
@Valvin yes, I know, I figured that out. 😉
@Valvin
Valvin
Valvin  
•
@utzer i was looking for the link and see it was your post i read ;)
@utzer [Friendica]
utzer [Friendica]
utzer [Friendica]  
•
@Michael Vogel any idea why Friendica does not stick to the php_path? First I thought it was because I called the daemon.php without the php command, so I added /usr/bin/php7 to the command, but that didn't do the trick. So somehow Friendica seems to trigger the worker and there it does not adhere to the set path?
@Michael Vogel
Hypolite Petovan
Hypolite Petovan  
•
Weird, troubleshooting a PHP path issue with the worker for someone else, I was able to solve their problem by updating this configuration value to the specific PHP interpreter.
utzer [Friendica]
utzer [Friendica]  
•
@Hypolite Petovan did that person have two php versions installed?
@Hypolite Petovan
Hypolite Petovan
Hypolite Petovan  
•
Yes, one in /usr/bin/php compiled as a cgi-fcgi module which tripped the PHP SAPI check at the start of bin/worker.php file. And one in /usr/local/bin/php correctly compiled as a cli module and the one we ended putting in the configuration variable.
utzer [Friendica]
utzer [Friendica]  
•

@Hypolite Petovan hmm ok, I just got two, /usr/bin/php (php 8.x) and /usr/bin/php7. And the worker ran with /usr/bin/php. Don't know why, the daemon was started with /usr/bin/php7 and the config value was set to that as well.

In the end I got frustrated and uninstalled the 8.x version to see what errors come, but didn't figure that out, so I ln -s the 7.x version to /usr/bin/php to have it running well.

@Hypolite Petovan
Hypolite Petovan
Hypolite Petovan  
•
Sorry about that, both the worker and the daemon react with a delay to config changes because of the way they work over a long period of time. For the worker, you need to wait for all the worker processes to be done before a change of config can be active. For the daemon, it needs to be stopped and restarted.
Roland Häder
Roland Häder  
•
@Admin (of friendica.utzer.de) @utzer I think that's the problem. You have two versions of PHP installed at the same server. It always seem to cause interference. I guess the best is (in my view) to uninstall PHP8 as it is to new and Friendica doesn't fully work on it (it was mentioned somewhere, I forgot by who).
@utzer [Friendica] @Admin (of friendica.utzer.de)
utzer [Friendica]
utzer [Friendica]  
•

@Hypolite Petovan of course I killed all php processes, restarted httpd, mariadb, php-fpm and the daemon. 😉

I think it might be borken, my guess is that at some point there is a call that starts a php process without the set path.

@Hypolite Petovan
utzer [Friendica]
utzer [Friendica]  
•
@Roland Häder I did uninstall php 8, but I think somewhere there is some call of php that does not use the set path.
@Roland Häder
Roland Häder
Roland Häder  
•
@utzer Ah, good. That is ruled out. 😀
:-)
@utzer [Friendica]
⇧