After a week of complete frustration, I finally got Drupal to work on VPS. I have to run suphp which wonderfully slows it down but it works. I don't mind a little slower as long as there are no more 503 errors.
There is one little bug though. When I run cron manually, it does actually run. It just doesn't send me to the admin/reports/system page -- it says http://example.com/admin/reports/system/run-cron page not found. We turned off the suphp and were running with DSO which caused a whole slew of other problems but the cron did complete and redirect to the proper page when it was finished.
I found a blurb on drupal.org that said to run suphp there can not be any php.ini directives in .htaccess. So I erased them and translated them to a php.ini file that is in the public_html directory. I think the whole system runs a little faster by a second or two.... not sure. Still it doesn't help the cron problem.
Does anybody have any thoughts on the subject? Better yet, how does a person install Drupal on a VPS? I've been having no luck what-so-ever!
Adam
Comments
ok
Installing Drupal on a VPS is easy, setting up a VPS however is not, believe me I know!
Ensuring your VPS is properly configured is not an easy task, for me anyway, maybe that's why hosting companies charge a premium?
Well.... thanks for bumping
Well.... thanks for bumping the post at least? So do you have any information that might be useful someone trying to set up a VPS? Or, do you know of any good posts out there with information that might help me learn to setup a VPS with Drupal on it by myself?
For the..
.. VPS google is your friend, do that first, then drupal is easy!
Nope, it's not easy. I've
Nope, it's not easy. I've been looking through the code. The problem seems to occur when system_run_cron() executes drupal_goto('admin/reports/status'). So my question now is what is the possible configuration of Apache that confuses the drupal_goto function? Drupal_goto('admin/content/comment') works. Don't know but whatever page it's building does not exist.
If that...
.. is the case, then I would suspect something is wrong with your VPS installalation. Try reaching the /admin/reports/status page in a browser.