smartvox
Forum Replies Created
-
For what it’s worth, I don’t think the issue is whether any support for IPv6 exists. My interpretation was that new API functions had been added in later versions of MariaDB which allow applications to query MariaDB – one of these new functions is used by the Shield plugin to enquire about IP addresses. The function just doesn’t exist in v5.5.
I found articles on the web explaining how to upgrade MariaDB to v10. It was a little bit scary so I tested it on a virtual machine before touching my production server. The most useful article I found was this:
https://www.liquidweb.com/kb/how-to-upgrade-mariadb-5-5-to-mariadb-10-0-on-centos-7/I also made some notes for myself and would be happy to send them to you by email. My business email address is shown on this link: https://www.smartvox.co.uk/about-us/
Hi Paul,
Thanks for making changes to fix this problem. It worked. As soon as I upgraded to v14, the errors stopped.
Before the upgrade I had narrowed it down to the option Hack Guard: File Scanning & Malware Protection. When the option for automatic scanning was switched off, the errors stopped.
The problems started some time ago and I suspect they are linked to my over-enthusiastic restrictions to file and directory ownership and permissions. I was getting a few other errors when trying to delete or upgrade plugins. Since reviewing and relaxing the ownership and permissions, those errors have gone away.
Thanks again.
JohnAnother extra piece of information: I think there is one instance of the error message for each active plugin. Oh, and the other error message about “Unknown column in wp_wpcslog”, that is nothing to do with Shield and I think is unrelated to the “Store directory could not be created” errors.
J.@paultgoodchild
Hi Paul,
I have upgraded MariaDB to v10.6 and the first error (INET6_ATON) has gone away.
However, the second error is still happening (Store directory could not be created). It is triggered when anyone visits the web site.
In my /etc/php.ini file, the open_basedir directive is not explicitly set so it will just take the default value.
I tinkered with wordpress debug settings and added an error_log statement into wp-cron.php to help identify the cron hook that is triggering the error. I also noticed a new error message that could be relevant:
Wordpress database error Unknown column ‘source_file’ in ‘field_list’ for query INSERT INTOwp_wpcsplog…..The hook in wp-cron,php that seems to coincide with these errors is: icwp-wpsf-ptg_build_snapshots
Thanks for your help so far.
John
Thank you Paul for a really speedy and helpful response.
I have already started to investigate how to upgrade MariaDB. Changing to MySQL 5.6 would be an alternative option, but I haven’t looked into it.Although the CentOS 7 repositories don’t offer a newer version of MariaDB, I found it is possible to download an RPM for MariaDB 10. I just need a bit of time to test the upgrade process away from my production server before applying it. I don’t want to lose any data. Hopefully the second error is also linked to this. I’ll let you know.
Thanks again.
John