So I removed the redis cache mechanism and shifted to normal --wp version. Now when I went to Wp-Crontol page after that, all my previous wp_seo events got removed and the list looked clean like it should. I tried executing the cron via the "run now" command and it worked.
After that, I shifted back to the --wpredis cache system, activated the object cache. I deleted the db value (the reviews I was fetching) and re-tried the "run now" command, it did not work
Initially, in the next run column, it was showing (2 minutes) etc. But after the time passed, it got stuck on the (now) message. Whenever I go to the cron-tab page, it just shows next run as (now) even though the time listed is that of the last execution, which never worked as expected. This happens for all the listed events i.e. once the next run time crosses, it only shows (now).
So to dig deeper, I tried executing the cron using wp-cli. When I executed the command to run all due events, it just infinitely started excuting all the wpseo_ events which were previously created. I had to hit ctrl+c to stop execution.
The next thing I checked for was all the events which are suppose to run next in the cron list using the command
wp cron event list --fields=hook,next_run
I got sooo many entries of the same wpseo events, even dating back to the year 2016.
I temporarily disabled the Yoast SEO plugin, ran a delete event command
wp cron event delete wpseo_ping_search_engines and a total of 574 instances of the cron events got deleted.
Did the same thing for the wpseo_hit_sitemap_index event as well.
After that, I again checked the list of events in the 'next run' list and did an execute due all for all events listed.
I checked the database and this time the value was there!
So for some reason, my whole cron system is kinda messed up and I am unable to figure out what might be the issue.
This is the crontab entry which I have
*/10 * * * * cd /var/www/mysite.tld/htdocs; php /var/www/mysite.tld/htdocs/wp-cron.php?doing_wp_cron > /dev/null 2>&1
Is there any way of verifying if the above version is actually executing all the cron items at all? good thing I am not using the wp cli version as it would have just stuck.
Update: When I run this on the command line, I get an error of "Could not open input file" but if I give the command without ?doing_wp_cron no error comes. Am I missing something here.