in reply to pasjrwoctx👽

friendica (DFRN) - Link to source

Anomaly

@pasjrwoctx👽
in reply to Anomaly

friendica - Link to source

pasjrwoctx👽

@Anomaly then if you open terminal on your server, and cd to your friendica dir, bin/worker.php it should run the worker, and one other thing you can try, is go to myphpadmin open your database for friendica, and in the sql tab enter DELETE FROM `workerqueue` WHERE `done` = 1; which will clear all jobs completed, the task may be completed, but not cleared out of the database table. other than that maybe @hypolite can help maybe better
@Anomaly
in reply to pasjrwoctx👽

friendica (DFRN) - Link to source

Anomaly

Thanks so much for the help @pasjrwoctx👽

~/friendica$ bin/daemon.php status
Daemon process 1120 is running.

Mysql
DELETE FROM workerqueue WHERE done = 1;
Query OK, 151 rows affected (0.004 sec)

For now UpdateContacts it's still there
Maybe @Hypolite Petovan will give some suggestions

@Hypolite Petovan @pasjrwoctx👽
in reply to silverwizard

friendica (DFRN) - Link to source

Anomaly

@silverwizard @Hypolite Petovan @pasjrwoctx👽
I killed the process and restarted it
systemctl status friendica-daemon.service
● friendica-daemon.service - Friendica daemon
     Loaded: loaded (/etc/systemd/system/friendica-daemon.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-03-09 19:13:33 CET; 21min ago
   Main PID: 1105 (php)
      Tasks: 1 (limit: 19101)
     Memory: 71.1M (peak: 294.3M)
        CPU: 38.343s
     CGroup: /system.slice/friendica-daemon.service
             └─1105 /usr/bin/php ./bin/daemon.php start

I turn on debug logs , these are all the messages
@Hypolite Petovan @silverwizard @pasjrwoctx👽

Friendica Support reshared this.

in reply to Anomaly

friendica - Link to source

pasjrwoctx👽

@Anomaly also try, Admin/Site/Worker Maximum load average=50, Maximum number of parallel workers=20, Maximum load for workers=150, Worker defer limit=15, Worker fetch limit=25, it may help as well as double check your Database Lock Wait Timeouts, check the Friendica log files for any error messages related to lock wait timeouts, sorry I cant offer more, im a little limited on my knowledge, just sharing everything I know, because I have dealt with some of these issues, y
@Anomaly

Friendica Support reshared this.

in reply to Anomaly

friendica - Link to source

Hypolite Petovan

@Anomaly Deferred tasks aren't currently running. They failed during they initial run, which placed them in this wait list with a next try date in the future. From your screenshot it appears that the task creation date and the next try date are pretty close to each other, so it must only have failed a few times at most.

Running either the worker or the daemon manually will not clear deferred tasks which next try date have not been reached yet. There's an incremental back off system that increases the delay before the next try after each new failure. Once the task succeeds, the task will clear from the deferred list.

@Anomaly

Friendica Support reshared this.

in reply to Hypolite Petovan

friendica (DFRN) - Link to source

Anomaly

@Hypolite Petovan
yes I thought this, but why has this entry been in the list for 2 months? All entries are successfully completed .
I have no problems with friendica, if this entry does not cause problems,can be on the list.
I'm not very experienced with friendica, so I'm asking
@Hypolite Petovan

Friendica Support reshared this.

⇧