Moving servers

I’m sorry if this has been covered before, I’ve even seen a website on the internet with this exact problem.

I have a perfect working site on a test server so all I have to do is copy the files across, sort out a few minor configuration problems and I’m up and running, right? Well wrong I think.

I copied all the files across to the new server and I got a blank manager page. I tried reinstalling and that was successful but still no manager.

If I just try and access the site I get

« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »

PHP error debug
Error: Unknown: open_basedir restriction in effect. File(/home/xx/xx/xx/assets/plugins/phx/phx.parser.class.inc.php) is not within the allowed path(s): (/var/www/vhosts/xxxx/httpdocs:/tmp)
Error type/ Nr.: Warning - 2
File: /var/www/vhosts/xxxxx/httpdocs/xxxx/manager/includes/document.parser.class.inc.php(746) : eval()’d code
Line: 10

Parser timing
MySQL: 0.0015 s (3 Requests)
PHP: 0.0340 s
Total: 0.0355 s


I’ve tried for a few hours to find a solution and right now I just want to cry.

Is there some change I need to make to the servers php.ini file or is it something else. The whole process of producing a website with problems with neither rhyme nor reason has driven me absolutely to distraction.

Anyone got any clues where I should even look to solve this? I’m done, I really am.

Mark

Not my words:

You’ve probably set the open_basedir directive somewhere. That restricts
PHP access to certain directories. Check php.ini and your Apache config
files (http.conf, .htacces, etc).

Can you access the php.ini file on your server?

Quote from: jusmeig at Sep 17, 2009, 08:08 AM

Not my words:

You’ve probably set the open_basedir directive somewhere. That restricts
PHP access to certain directories. Check php.ini and your Apache config
files (http.conf, .htacces, etc).

Can you access the php.ini file on your server?

Yes I can. The open_basedir seems to be commented out in php.ini. Although editing it by vi would not really be my first choice. I will check the Apache files next. I’m pretty sure it’s not the .htaccess file so that leaves http.conf which I will check now. Turned error reporting on briefly and the manager is throwing 6 of these.

It seems to be Plesk that is introducing this problem of open_basedir and in spite of producing a vhost.conf
file I cannot solve the problem. Anyone had any experience of this on 1&1?

I don’t even know why Plesk would want to over-ride these settings. It’s a rubbish file manager too.

Mark

OK I think I have a handle on what the problem is but no solution.

I’m hosted by 1&1 at the moment. It is a dedicated server. It has Plesk on it.

I have worked on my CMS project for six months virtually solidly. 1&1 is probably going to have to be the server for reasons I won’t go into. So I really need a fix for this.

http://modxcms.com/forums/index.php?topic=25366.0
discussed this but the hack doesn’t work, although it did at least let me see the manager (just not log in, see the error message or do anything useful).

I have tried various versions of this:

<Directory /srv/www/vhosts/$domain.com/subdomains/$subDomName/httpdocs>
<IfModule sapi_apache2.c>
php_admin_flag engine on
php_admin_flag safe_mode off
php_admin_value open_basedir "/srv/www/vhosts/$domain.com/httpdocs:/srv/www/vhosts/$domain.com/subdomains/$subDomName/httpdocs:/tmp"
</IfModule>
<IfModule mod_php5.c>
php_admin_flag engine on
php_admin_flag safe_mode off
php_admin_value open_basedir "/srv/www/vhosts/$domain.com/httpdocs:/srv/www/vhosts/$domain.com/subdomains/$subDomName/httpdocs:/tmp"
</IfModule>
</Directory>


in the conf/vhost.conf, one of which crashed the server completely. This ought to be the trivial solution to the problem but I cannot get it to work. I tried a single domain one too, this is the last one I tried because the person in the posting seemed to believe it worked http://enarion.net/web/plesk/subdomains-and-open_basedir/.

Incidently I also did a clean install of modx in another directory with an empty database, the default page came up but no manager still.

This is pretty much failure is not an option for me, the consequences could be fairly huge if I don’t.

So I’m pretty much begging for a conf/vhost.conf file that 100% works and is tested or a core hack of modx that is 100% reliable. If I was done last night, I’m really done now, tried my very best with the 1&1 helpdesk, but essentially they said it was my problem. Whereas I think it’s 1&1’s problem or Plesk’s.

Really can anyone help me out?

I think I may have worked out the problem. Old software on our server. Something that never occurred to me at all given what we’re paying for it.

And apparently it’s near impossible to update on 1&1. At least not with the tech support I’ve had.