atomtopubsub has stopped updating the movim feed nodes #21
Description
Hi edhelas
I have had your latest atomtopubsub running for some days now (prosody 13.01 and latest movim). It has filled the 30 nodes with aggregated articles, and in CLI it looks like it continue to do so without any error, other than occationally a feed source may be unreachable for some strange reason.
The problem is that, even if it continues to grab content from the feeds, the new articles for the most part does not any longer show up in the movin nodes. Exerpt a few (maybe 4 - 5 articles a day in total). I now have several rss-atomnodes from sources that I know produce 10 - 20 articles a day, not showing up in the nodes.
I thought it could be due to some resource bottleneck on the server (digitalocean droplet, 1GB memory), but that does not seem so.
I had recognised a couple of these warnings:
[16-May-2025 03:42:09] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it
and increased the number of them in the /etc/php/8.3/fpm/pool.d/www.conf file as follows:
pm.max_children = 15
pm.start_servers = 7
pm.min_spare_servers = 6
pm.max_spare_servers = 10
as per instructions in this article: https://www.kinamo.be/en/knowledge-base/determining-the-correct-number-of-child-processes-for-php-fpm
ps -e | grep php-fpm (confirmed changed settings was done)
But that seems not to have helped any at all. So there must be something else preventing the nodes from being updated with whatever atomtopubsub delivers. Any idea?