I got some weird errors when trying to upgrade from 1.3 to 1.5 such as:
Warning: fopen(http://irmetta.mysite.com/wp-admin/upgrade.php?step=1) [function.fopen]: failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/qrcobry3/public_html/mysite/wp-admin/wpmu-upgrade-site.php on line 31
* http://atreyu.mysite.com/
Warning: fopen() [function.fopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/qrcobry3/public_html/mysite/wp-admin/wpmu-upgrade-site.php on line 31
Warning: fopen(http://atreyu.mysite.com/wp-admin/upgrade.php?step=1) [function.fopen]: failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/qrcobry3/public_html/mysite/wp-admin/wpmu-upgrade-site.php on line 31
* http://spandan.mysite.com/
Warning: fopen() [function.fopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/qrcobry3/public_html/mysite/wp-admin/wpmu-upgrade-site.php on line 31
Warning: fopen(http://spandan.mysite.com/wp-admin/upgrade.php?step=1) [function.fopen]: failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/qrcobry3/public_html/mysite/wp-admin/wpmu-upgrade-site.php on line 31
* http://clubthoughts.mysite.com/
Warning: fopen() [function.fopen]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/qrcobry3/public_html/mysite/wp-admin/wpmu-upgrade-site.php on line 31
Warning: fopen(http://clubthoughts.mysite.com/wp-admin/upgrade.php?step=1) [function.fopen]: failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/qrcobry3/public_html/mysite/wp-admin/wpmu-upgrade-site.php on line 31
* http://damialauren.mysite.com/
It did this through all the blogs - then said upgrade complete.. everything seems to work, and I am anxious to upgrade to 2.6.2, but if something is screwed up by this and I need to reinstall the backup database, guess it'd be best to find out now..
I sent the errors to my host support to see if they can shed some light on the issue. ( I had just moved my MU install to a new host - reinstalled, everything seemed fine, then during upgrade had above issue)
I may just try to do the next upgrade to 2.6.2 and see what happens.. Does anyone think I should be concerned about those errors?
