• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Wordpress Update Issues

That's weird!!!

It says that root has write and read permission. Try removing the file and adding it again.

1) Remove /etc/resolv.conf: rm /etc/resolv.conf
2) Create a new file: touch /etc/resolv.conf
3) Edit this file: vim etc/resolv.conf

If it does not work or there is an error in the middle of the paste process here.

I also ask you to paste here the output of the command "lsof /etc/resolv.conf". This way you will be able to check if this file is being used by another process :)
 
The file is "locked" to prevent modifications when the server is restarted. If this works, I recommend again locking it with the command:

chattr + i /etc/resolv.conf
 
Toying with /etc/resolv.conf is not the right way of changing resolvers in CentOS.

If this is what you want, try "vim /etc/sysconfig/network-scripts/ifcfg-eth0" and modify the entries for DNS1 and DNS2 (assuming your network interface is eth0, which probably is...)

After that: "systemctl restart network.service"
 
i get the following error when i add the data from the otehr server into the resolv.conf file:
"etc/resolv.conf" E212: Can't open file for writing
Any clues to what I am doing wrong, I am logged in as the root user so i have the priviliges to write to the file, infact any file, just that this particular file doesnt allow it to be saved after writing

It's probably set as read only. Correct the permissions.
 
thanks Ernesto, i could finally write and save that file, now to see if wordpress will update or i get the same error again, will update shortly
 
Updates:
after adding the nameservers as suggested by Ernesto, and then saving the file, the downloads still didnt happen, same error as before.
I then followed Sergio's suggestions and found that the datacentres's NS were still showing in the ifcfg-eth0 file, so i changed both the DNS to the values that should really reflect, and restarted the network service,
On running the command : /cat/etc/resolv.conf, the datacentres DNS have been commented out, (though i had it replaced, and the news ones showing up, however the downloads and updates of wordpress is still an issue with the same error as before..
Any suggestions???
 
@SamirM
please be so kindliy and run the following comand on the cli just to see if curl works now in general or there is still another issue.

on comandline run
Code:
curl -X POST http://api.wordpress.org/core/version-check/1.7/
and post the output here.
 
Updates 2:
@SamirM
please be so kindliy and run the following comand on the cli just to see if curl works now in general or there is still another issue.

on comandline run
Code:
curl -X POST http://api.wordpress.org/core/version-check/1.7/
and post the output here.

[root@myserver admin]# curl -X POST http://api.wordpress.org/core/version-check/1.7/
{"offers":[{"response":"upgrade","download":"http:\/\/downloads.wordpress.org\/release\/wordpress-4.9.4.zip","locale":"en_US","packages":{"full":"http:\/\/downloads.wordpress.org\/release\/wordpress-4.9.4.zip","no_content":"http:\/\/downloads.wordpress.org\/release\/wordpress-4.9.4-no-content.zip","new_bundled":"http:\/\/downloads.wordpress.org\/release\/wordpress-4.9.4-new-bundled.zip","partial":false,"rollback":false},"current":"4.9.4","version":"4.9.4","php_version":"5.2.4","mysql_version":"5.0","new_bundled":"4.7","partial_version":false}],"translations":[]}
 
Can I ask the same question as before?
Does this problem continue to happen on just one site or all?

Who is Ernesto? :rolleyes:
Sorry that should ahve read Emerson, my bad.....

This is happening across all sites that have wordpress...and on extensive reading I am begining to sus[pect googles DNS ( the 8.8.8.8) as the culprit, but then if it works jsut fine on one server why should the otehr server have an issue is my thinking....
 
Ok, let's just take a million steps back for a second.

The issue is curl is timing out from the WP dashboard. From command line, It's working. Let's adjust the timeout values in WP.

By default it's set in 2 core WP files;

WordPress/class-wp-http-curl.php at master · WordPress/WordPress · GitHub
WordPress/class-http.php at master · WordPress/WordPress · GitHub

Let's set "5 seconds" to something crazy in both those files. Something like 120, and then test from there.
This was one of the first things i had done before posting here, however i had changed the values in just the class-http.php fie to 20 instead of 5, now i have increased the values in both the files to 120, and i still have the same error.
I guess i will try eith the OpenDNS suggestion of @Emerson too and see if things get sorted out with that
 
one more question, do all the wordpress instances run within the same php version or differnt one and which php version the php os vendor or plesk installed and have you tried to use another php version too?
 
Back
Top