Log In
Home
(1 votes) 3:51 pm
December 17, 2022
Offline
Several feeds no longer work after the update. I tried with the new Balanced tags parameter too but no luck.
[21-12-22 02:12:02] Unable to parse 
Login to see this link
[21-12-22 02:12:02] Feed syndication failed
How can I go back to the older version?
5:05 pm
July 2, 2009
Offline
Which version you'd like to go to? Just pick here the version you want and I'll switch you back to it: Login to see this link
P.S. But before doing that, make sure that your server is able to retrieve the feed. I mean check the connection to the remote host and make sure your server IP is not banned by the feed's owner. I suggest you to do so, because the feed is ok and I can easily pull it from any of my hosts, including the local server at my home computer.
6:18 pm
December 17, 2022
Offline
OK, it did pull a post now, but I noticed that the log shows "Unable to parse Login to see this link.....feed url...............t" after each feed retrieval. Not sure what that is, but it works.
7:51 pm
July 2, 2009
Offline
I means that both cURL and PHP file_get_contents() function were unable to download the remote file. Not to parse it, but just to download any content at all. E.g. the remote server was down, there was a connecting problem between your server the remote one, your IP was blocked, the file was blank because a PHP error on that site etc. It's like when you try to open some webpage in the browser and receive a message: the page can not be loaded. Many various reasons could cause that.
11:09 am
December 17, 2022
Offline
CyberSEO said
Which version you'd like to go to? Just pick here the version you want and I'll switch you back to it:P.S. But before doing that, make sure that your server is able to retrieve the feed. I mean check the connection to the remote host and make sure your server IP is not banned by the feed's owner. I suggest you to do so, because the feed is ok and I can easily pull it from any of my hosts, including the local server at my home computer.
Version 10.000 please. This is the only one I used.
OMG, 10.001 caused me a nightmare and had to restore a backup. I don't know what caused the problem but basically I had to "sudo systemctl restart php8.0-fpm.service" to load any page on the site. The pages would work for a few seconds and then the whole website crashes. Took me hours to find out that Disabling the CyberSEO fixed the server downtime.
3:01 pm
December 17, 2022
Offline
UPDATE - I have no idea what went wrong, but everything just worked again from the backup once I deactivated the CyberSEO plugin. The backup had the new version (10.001).
Now I have re-enabled CyberSEO 10.001. The plugin lost all the RSS feeds after reactivating it, yet the logs where still there.
I restored the feed information from the backup database (i hadn't exported them before) and it worked. The new posts we imported but for some feeds CyberSEO would say 0 posts added but it would have already added 4 or 5 posts. I guess that's an issue with 10.001.
I've re-enabled cron and will monitor the site to see if it breaks again.
3:16 pm
July 2, 2009
Offline
Version 10.001 has only one function added. This one: Login to see this link and nothing else.
Moreover, this function is disabled by default, so version 10.001 has no other differences to 10.000. Could you please how this change may cause a nightmare?
I mean even in theory. Let's imagine we are writing a script for new a sci-fi blockbuster here :)
I wonder why I'm getting such reports every time the new version gets published. I optimize a file loading routine, the server crashes. I add one single WordPress API function call, which is not even enabled by default and people lose all the feed settings...
But every single story ends up like: "my admin has changed some server settings. the issue is fixed now", or "I found I've installed a plugin which deletes the data from WordPress datadase", or something like this:
Login to see this link
or like this:
Login to see this link
or your very first post in this thread. You say that's "because of update", but in fact it seems that the remote host was temporary down and the plugin just received a 503 error (Login to see this link) form it instead of the actual RSS feed.
I can officially assure you that there were no changes in CyberSEO Pro 10.001 that can hurt your feed settings at all.
3:39 pm
July 2, 2009
Offline
Just imagine for a second, if there is an error in version 10.001, which deletes all the feed settings at your installation, it should cause the same trouble at all the other sites that use CyberSEO Pro. Is that correct? According to my logic, there must be a thousand of post about it from other customers. Just because a bug in may code will affect just everyone, while some local issue at one single website could be cause by some other local problems at that single particular website? Am I wrong?
P.S. As about broken feed settings or duplicated posts. This issue may really happen when a few parallel instances of the plugin pull feeds and writes something into your database at the same time. It could really happen when a customer uses "auto" RSS pull mode. E.g.: Login to see this link
And that's why I urge everybody to use cron: Login to see this link
So please use cron and forget about these issues once and for all.
4:12 pm
December 17, 2022
Offline
CyberSEO said
Version 10.001 has only one function added. This one:Moreover, this function is disabled by default, so version 10.001 has no other differences to 10.000. Could you please how this change may cause a nightmare?
I mean even in theory. Let's imagine we are writing a script for new a sci-fi blockbuster here :)
I wonder why I'm getting such reports every time the new version gets published. I optimize a file loading routine, the server crashes. I add one single WordPress API function call, which is not even enabled by default and people lose all the feed settings...
But every single story ends up like: "ah, my admin has changed some server settings. the issue is fixed now", or "ah I found I've installed a plugin which deletes the data from WordPress datadase", or something like this:
or like this:
or your very first post in this thread. You say that's "because of update", but in fact it seems that the remote host was temporary down and the plugin just received a 503 error (
I can officially assure you that there were no changes in CyberSEO Pro 10.001 that can hurt your feed settings at all.
OK, site was down again (Error 504). Restarting PHP-FPM lets the pages load but then it stops again after a few seconds.
Once I deactivated the plugin the site started working again. To get the plugin page to load I had to restart FPM 3 times.
4:15 pm
December 17, 2022
Offline
CyberSEO said
Just imagine for a second, if there is an error in version 10.001, which deletes all the feed settings at your installation, it should cause the same trouble at all the other sites that use CyberSEO Pro. Is that correct? According to my logic, there must be a thousand of post about it from other customers. Just because a bug in may code will affect just everyone, while some local issue at one single website could be cause by some other local problems at that single particular website? Am I wrong?P.S. As about broken feed settings or duplicated posts. This issue may really happen when a few parallel instances of the plugin pull feeds and writes something into your database at the same time. It could really happen when a customer uses "auto" RSS pull mode. E.g.:
And that's why I urge everybody to use cron:
So please use cron and forget about these issues once and for all.
I have been using cron from the very beginning. I had to disable it to troubleshoot the issue and then brought it back.
I understand your logic and I would agree with it if all sites were identical, unfortunately there are several combinations of plugins in each and I'm sure that is why you would get isolated reports of such issues.
Anyway, re the deleted feeds, I should have made an export before deactivating the plugin, but it was hard to get any page to work for more that a few seconds before everything broke again.
4:23 pm
December 17, 2022
Offline
CyberSEO said
P.S. As about broken feed settings or duplicated posts. This issue may really happen when a few parallel instances of the plugin pull feeds and writes something into your database at the same time. It could really happen when a customer uses "auto" RSS pull mode. E.g.:
Maybe that's the issue. I'm using cron set to check every 10 minutes. I then have the feeds themselves set mostly for hourly checks, but others can be at much longer intervals, with over 30 feeds there is usually 3-4 to check every hour.
I had also increased the timeout to 600 in the settings as per the screenshot in the manual, so maybe the cron is triggering while the previous job is still lurking around. I don't think any single pull would take 10 minutes especially that the checks are frequent.
4:24 pm
July 2, 2009
Offline
MediFormatica said
CyberSEO said
Version 10.001 has only one function added. This one:Moreover, this function is disabled by default, so version 10.001 has no other differences to 10.000. Could you please how this change may cause a nightmare?
I mean even in theory. Let's imagine we are writing a script for new a sci-fi blockbuster here :)
I wonder why I'm getting such reports every time the new version gets published. I optimize a file loading routine, the server crashes. I add one single WordPress API function call, which is not even enabled by default and people lose all the feed settings...
But every single story ends up like: "ah, my admin has changed some server settings. the issue is fixed now", or "ah I found I've installed a plugin which deletes the data from WordPress datadase", or something like this:
or like this:
or your very first post in this thread. You say that's "because of update", but in fact it seems that the remote host was temporary down and the plugin just received a 503 error (
I can officially assure you that there were no changes in CyberSEO Pro 10.001 that can hurt your feed settings at all.
OK, site was down again (Error 504). Restarting PHP-FPM lets the pages load but then it stops again after a few seconds.
Once I deactivated the plugin the site started working again. To get the plugin page to load I had to restart FPM 3 times.
This is a question for your host admin, because only he/she has an access to the server error log.
4:30 pm
July 2, 2009
Offline
MediFormatica said
CyberSEO said
P.S. As about broken feed settings or duplicated posts. This issue may really happen when a few parallel instances of the plugin pull feeds and writes something into your database at the same time. It could really happen when a customer uses "auto" RSS pull mode. E.g.:Maybe that's the issue. I'm using cron set to check every 10 minutes. I then have the feeds themselves set mostly for hourly checks, but others can be at much longer intervals, with over 30 feeds there is usually 3-4 to check every hour.
I had also increased the timeout to 600 in the settings as per the screenshot in the manual, so maybe the cron is triggering while the previous job is still lurking around. I don't think any single pull would take 10 minutes especially that the checks are frequent.
You should not run cron more often than the timeout period. Also what kind of feed do you pull where the authors post a new article every 10 minutes? Actually once or twice a day is more than enough for almost anything...
In such a regime you just literally forces your server hardware.
5:02 pm
December 17, 2022
Offline
I get your point, though I do have a reason for such frequency for my use case. I'm pulling from several feeds and then posting to social media. That's a approximately a total of 20 - 30 posts a day. So instead of posting a bulk of stories twice a day I would have them trickle through the day.
I also thought this would be better for the server as I'm not trying to pull alot of posts in one go, rather none or 1-2 every 10 minutes.
Anyway, thanks for the suggestions. I'll try to space them out a bit and see how it goes.
As for the server, during the downtime there is nothing eating up the resources, it just sits there with a very low load. I just added another core and 6 GB of RAM yesterday thinking it may help. During the fetch the CPU load increases but then its over in a minute or so.
WPeMatico sometimes overloaded the CPU especially when I was adding a new feed and pulling 10-15 posts in one go, and the website would be unreachable, but then it would be back in a minute with any intervention from my side.
As always, thanks for your prompt responses.
2:16 am
July 2, 2009
Offline
I've made some improvement of in the script. Now the feeds won't be pulled if the time passed since the previous operation is less than the max execution time + 30 seconds. So two simultaneously running copies of CyberSEO Pro should not interfere. This may also help to prevent duplicated post generation in "auto" mode.
All RSSMost Users Ever Online: 541
Currently Online: JoJo
7 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 68
Freedom: 61
Pandermos: 54
MediFormatica: 49
B8europe: 48
Member Stats:
Guest Posters: 337
Members: 2853
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1640
Posts: 8352
Newest Members:
wanmarkets, torontomark48, info.ckmedianetwork, contact.mybeautystar, samuelbodde, john.prushAdministrators: CyberSEO: 3947