GoDaddy Hosting Transition Gone Bad - View My Log File?


Over the weekend, we made a server switch from GoDaddy hosting our site, to hosting it on our GoDaddy Virtual Dedicated Server. Since the propagation went through, we've run into serious issues of the site being completely inaccessible. Unfortunately, our knowledge of log reading is nil, so we're hoping it's appropriate to post the latest errors and to determine what the main culprits seem to be.

You can access the log file here (same file, 2 places, in case one doesn't work)

For some background
-nameservers were changed to virtual dedicated server approx Saturday, 11/27, 7pm PST (Los Angeles)
-propagation seemed solid by Sunday 11am
-started adding multiple subdomains with PHP support on Sunday evening...  this seemed to tax the system so that we couldn't access any sites on the server; we deleted most of the subdomains, and the sites were again accessible
-Monday, the sites on our server have been inaccessible all day, presumably because there is more traffic? if we reboot the server, the sites become accessible again, but only for a matter of time

On Monday, Noon PST, we switched back the Nameservers to the GoDaddy host (away from our Vir Ded Server), in an urgent attempt to get our sites accessible again.

Any ideas on what is behind these issues?

Can I provide more data?

Who is Participating?
nociSoftware EngineerCommented:
Is the virtual system running the same tools & php as the other one?

From the logs:
php support?
 PHP Fatal error:  Call to undefined function bcadd() in /var/www/vhosts/ :
 PHP Fatal error:  Call to undefined function session_pagestart() in /var/www/vhosts/ on line 65
Did you get everything over?

Missing files:
 File does not exist: /var/www/vhosts/
 PHP Warning:  main() [<a href='function.include'>function.include</a>]: Failed opening '../../../' for inclusion
 script '/var/www/vhosts/' not found or unable to stat

Did you really copy EVERYthing over, is the same kind of environment available
(php with the same support..)

You copy everything before going live with:
copy everything, install the right php, possibly other tools etc.

then you can test this with a test client, where you add the ip address of your new server to the /etc/hosts file with the old name, probably ''
(or equivalent in windows) and test from that system, if everything works => cutover the DNS.

runningoneAuthor Commented:
Please look at the bottom of the log file where there are the same errors repeating over and over again.

For example

[client] script '/var/www/vhosts/' not found or unable to stat

It is showing that all of these files do not exist, but that is impossible. They are and were there.

Also, why would it find all of the files fine after doing a reboot?


p.s.  Admin, Please do not close this topic. Thx
nociSoftware EngineerCommented:
Might it be possible that the filesystem where /var/www/..... was mounted was unavailable at the time
you checked out the environment, (at the time the errors occurred?) (i.e. dismounted)
After a reboot (and a remount) the files would be available again.

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

runningoneAuthor Commented:
How would a dismounting happen?  There was nothing we did manually to force a dismount so unless it occurred automatically. there was no dismounting.
nociSoftware EngineerCommented:
Besides a dismount other options are:
Invalid symbolic links, renamed directories etc.  but they don't resolve over a reboot.
a change of fstab before the session with the errors, a reboot
can result in such a list of errors, repairing the fstab and rebooting can repair.. (guessing wildly from now on).

Errors on a file system might prevent it from mounting, mostly you end up in single user mode
during booting (without anything started) That does depend on the boot scripts of the machine though.

Not found and cannot stat might also be a problem with ownership and access rights higher up the tree, although
I would expect to see an access denied message then.

Running on a virtual server might also mean that the host system has the underlyng storage unavailable for backup f.e.
But that would limit the problems to a restricted time period.
nociSoftware EngineerCommented:
are these NFS mounted disks?, where the server went MIA?

It has been quite a while.  Any update?

EE Cleanup Volunteer
runningoneAuthor Commented:
Cyclops, we need to do some more research. Please keep the issue open. Thanks.
No problem, just remember when an expert asks a question to please respond, even if it is just to say that you are working on it.  Also, please give periodic updates so that everyone knows that the Q isn't abandoned.

Thank you,

EE Cleanup Volunteer
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.