• 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

most of the websites messed up

F

flupke

Guest
happened since 2 days, most of the sites impacted,those with photo gallery or eshop, it starts with the same issue, hereafter a concrete example, this occurs for website YYYYYYYYYY but SB also refers to XXXXXXXX, does it mix sites? Can I rebuild the data of Sitebuilder? Republishing A FEW TIMES seems to solve the problem for that website, until another site is impacted, it looks like a chain reaction.

---------- typical error -------------

Warning: main() [function.main]: open_basedir restriction in effect.
File(/var/www/vhosts/XXXXXXXXX/httpdocs//init.php) is not within the
allowed path(s): (/var/www/vhosts/YYYYYYYYY/httpdocs:/tmp)
in /var/www/vhosts/YYYYYYYYYYY/httpdocs/page12.php on line 2

Warning: main(init.php) [function.main]: failed to open stream:
Operation not permitted in
/var/www/vhosts/YYYYYYYYYYYYY/httpdocs/page12.php on line 2

Fatal error: main() [function.require]: Failed opening required
'init.php'
(include_path='/var/www/vhosts/XXXXXXX/httpdocs/:.:./include:/usr/share/pear:/usr/share/php') in /var/www/vhosts/YYYYYYYYYYy/httpdocs/page12.php on line
2


------------ another error -----------
The ionCube PHP Loader (v 3.1.15 or newer) is not installed at the target server.

everything was ok since the upgrade to v4.2, we didn't change anything else since then, neither in plesk, neither on apache or linux, nothing.
 
I now suspect the VPS, it happened that the error (see below) spontaneously happens on the published website. I click the browser refresh button a few times and then suddenly the page comes out. I check the error logs, could find any warning or error, could it be a PHP memory limitation problem, what log can I look at?

---------- typical error -------------

Warning: main() [function.main]: open_basedir restriction in effect.
File(/var/www/vhosts/XXXXXXXXX/httpdocs//init.php) is not within the
allowed path(s): (/var/www/vhosts/YYYYYYYYY/httpdocs:/tmp)
in /var/www/vhosts/YYYYYYYYYYY/httpdocs/page12.php on line 2

Warning: main(init.php) [function.main]: failed to open stream:
Operation not permitted in
/var/www/vhosts/YYYYYYYYYYYYY/httpdocs/page12.php on line 2

Fatal error: main() [function.require]: Failed opening required
'init.php'
(include_path='/var/www/vhosts/XXXXXXX/httpdocs/:.:./include:/usr/share/pear:/usr/share/php') in /var/www/vhosts/YYYYYYYYYYy/httpdocs/page12.php on line
2
 
Probably this is PHP 5.2.5 issue. Which version do you have installed? If you have 5.2.5 version it is suggested to downgrade it to 5.2.4 at least as PHP 5.2.5 version have some issues which can affect Sitebuilder and Plesk. For more details you can check this forum as this issue was already discussed in Sitebuilder and Plesk threads.
 
We have 5.0.4 (Fedora 4 32 bits ).
Everything was ok, we upgraded to SB 4.2 2 weeks ago, after 2 weeks now we start having problems, the published web sites don't shoe well all the time (see typical error here above), pressing the refresh button a few times an then the site appears. It seems that the impacted web sites are those with eshop and photo gallery.

Should I upgrade to 5.2.4? NB: everyhing was well with SB 4.0 & SB 4.1
 
Could you please put /usr/local/sitebuilder/resources/publish/check.php and phpinfo.php file into /var/www/vhosts/XXXXXXXXX/httpdocs/ directory and let me know the link so I could check php information and output from check.php script?

phpinfo.php
<?php phpinfo(); ?>

As I understand this is the same server Plesk+Sitebuilder installation. Were there any more changes on this server except Sitebuilder update to 4.2 version?
 
yes, same server for plesk 8.1 & SB 4.2 in a VPS (Fedora 4 32 bits)
no changes done beside upgrade 4.1 --> 4.2

I will copy the 2 files, I kep you informed (do you have a private contact?)
 
see private message please (I respect my customers but not listing their websites here)
 
no, no vhost file.

will try to workaround, but why doesn't it always happen, when I visit the published website, I can reproduce the error by clicking a few times the refresh button. The error happens at some time of the day, as example right now everythig is fine.

I think I will open a ticket.
 
Dmity, I thought you would be interested by an update: I found out that this is link to a nasty bug related to Apache-PHP: the Apache threads sometimes don't cleanup the memory space before servicings another http request, the consequence is that open_basedir was set the settings of a previously visited website, different from the site being serviced.

Temporary solution is to reduce MaxRequesPerChild in httpd.conf, so the Apache child process will be freshly restarted ore often, reducing the probability to have the problem.

So the issue is not related to SB but to the hosting environement, SB was a victim of the problem.

The solution is to upgrade PHP.

Regards

Flupke
 
Back
Top