• 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

Often blank page with SB modules

papak

Basic Pleskian
Hello,

We have just updated SB to 4.2 and now we have the problem with published modules such guestbook, gallery etc. Often accessing any of modules show blank page but sometimes are working. The error message in logs are ever the same:

==> /var/www/vhosts/domain.com/statistics/logs/access_log <==
80.218.246.199 - - [30/Mar/2008:16:38:55 +0200] "GET /page3.php HTTP/1.1" 500 308 "http://www.domain.com/page2.php" "Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13"

==> /var/www/vhosts/domain.com/statistics/logs/error_log <==
[Sun Mar 30 16:38:55 2008] [error] [client 80.218.246.199] PHP Warning: main(SB/Modules.php) [<a href='function.main'>function.main</a>]: failed to open stream: No such file or directory in /var/www/vhosts/domain.com/httpdocs/init.php on line 24, referer: http://www.domain.com/page2.php
[Sun Mar 30 16:38:55 2008] [error] [client 80.218.246.199] PHP Fatal error: main() [<a href='function.require'>function.require</a>]: Failed opening required 'SB/Modules.php' (include_path='.:.:/usr/share/pear') in /var/www/vhosts/domain.com/httpdocs/init.php on line 24, referer: http://www.domain.com/page2.php

==> /var/www/vhosts/domain.com/statistics/logs/access_log <==
80.218.246.199 - - [30/Mar/2008:16:38:56 +0200] "GET /page3.php HTTP/1.1" 500 308 "http://www.domain.com/page2.php" "Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.8.1.13) Gecko/20080311 Firefox/2.0.0.13"

==> /var/www/vhosts/domain.com/statistics/logs/error_log <==
[Sun Mar 30 16:38:56 2008] [error] [client 80.218.246.199] PHP Warning: main(SB/Modules.php) [<a href='function.main'>function.main</a>]: failed to open stream: No such file or directory in /var/www/vhosts/domain.com/httpdocs/init.php on line 24, referer: http://www.domain.com/page2.php
[Sun Mar 30 16:38:56 2008] [error] [client 80.218.246.199] PHP Fatal error: main() [<a href='function.require'>function.require</a>]: Failed opening required 'SB/Modules.php' (include_path='.:.:/usr/share/pear') in /var/www/vhosts/domain.com/httpdocs/init.php on line 24, referer: http://www.domain.com/page2.php

We checked check.php for SB and everything is Ok. Other requirements for publishing SB are met.

We checked all settings many times and nothing found. Comically the problem is gone for a while after restarting apache, but after half hour or hour is back.

Any idea or help would be greatly appreciated.

Best regards,
Mike
 
Which PHP version do you use on the server? If this is PHP 5.2.5 then you can try following solutions:

1. Downgrade PHP to 5.2.4
2. As I understand you use Plesk on the same server. So following modification should be done in vhost.conf file for domain:

echo 'php_admin_value include_path
"/var/www/vhosts/domain.com/httpdocs/:.:./include:/usr/share/pear:/usr/share/php"'
> /var/www/vhosts/domain.com/conf/vhost.conf

As I understand this is related to PHP bugs:
http://bugs.php.net/bug.php?id=43755
http://bugs.php.net/bug.php?id=43677

Hope it helps.
 
Hello Dmitry,

Thank you. We downgraded to PHP to 5.2.4 and it seems to work fine, but this broken many things and Plesk too. It would be appreciated in the future if you allready know about bugs such this, to publish in Sitebuilder KB or here. We can't know if Sitebuilder have problem with any PHP bug or not. You need only few minutes for this and we can wait with PHP update on the server.

Thanks in advance.

Best regards,
Mike
 
Thank you for your suggestion, Mike. I am trying to post available solutions directly into KB. In this case PHP downgrade not so simple case for many customers and it could affect something else. It is also hard to describe this process in details as it depends on OS, other applications installed..etc. So this article was not added yet. I am going to collect necessary information and post it in nearest time.
 
Hi, Dmitry. I am getting the same problem: blank page in whatever special page like galleries, forum, etc. Normal html pages work correctly.

If I include a special page like gallery I get the following error:

PHP SQLite extension does not support UTF-8 encoding on the publishing server. Text information on the site may be displayed incorrectly. 2 Cannot update modules data.

If I publish a domain without any special page only html pages, sitbuilder is able to publish the site with out any warning.
 
"PHP SQLite extension does not support UTF-8 encoding" means that UTF-8 encoding does not supported in sqlite extensions which is installed on your published server. Try to use following article for checking requirements on publishing host: http://kb.swsoft.com/en/1812. Check which PHP version is used there. If it is PHP 5.2.5 blank pages can be caused by this installation. In this case PHP downgrade should be done to 5.2.4 version for example. Let me know about the results.
 
follow up , Blank page sb

Dmitry,

I have maneshed to get help on installing 5.2.6 wint cent os5x64 with some rpms y found , but are having a problem with the Sqlite 2.X extencions with this php , any suggestions on where can i get some RPM's for sqlite 2.x for php 5.2.X ??

thank you.



If you are talking about this bug http://bugs.php.net/bug.php?id=43755 it should be corrected in 5.2.6 as it claims in bug.
 
Together with PHP 5.2.x usually goes PDO_SQLITE. This is a driver that implements the PHP Data Objects (PDO) interface to enable access to SQLite 3 databases. This extension provides an SQLite v3 driver for PDO. SQLite V3 is not compatible with the bundled SQLite 2 in PHP 5.

So right now appropriate sqlite 2.x extension should be installed. It is possible to compile this extension manually. Try, for example, following solution:

http://adminforces.com/index.php?vi...-from-the-source&option=com_content&Itemid=64

Here you can find explanation why old sqlite 2.x is still in use:

http://forum.swsoft.com/showthread.php?t=51256&highlight=sqlite

Actually, I do not know the place where it is possible to get compiled sqlite.so for newest PHP versions, so most probalby you will need to compile it. This is actually not so hard procedure, so you can try.
Hope this helps.
 
no luck

Hi Dmitry , thanks for the tips.

Imanaged to install sqlite with no problems i think but now i get this error with the check.php: folder_permissions_data=fail

And when i try to publised to a site via the sitebuilder y get this error:
Cannot update modules data

Any Ideas.

thanks



Together with PHP 5.2.x usually goes PDO_SQLITE. This is a driver that implements the PHP Data Objects (PDO) interface to enable access to SQLite 3 databases. This extension provides an SQLite v3 driver for PDO. SQLite V3 is not compatible with the bundled SQLite 2 in PHP 5.

So right now appropriate sqlite 2.x extension should be installed. It is possible to compile this extension manually. Try, for example, following solution:

http://adminforces.com/index.php?vi...-from-the-source&option=com_content&Itemid=64

Here you can find explanation why old sqlite 2.x is still in use:

http://forum.swsoft.com/showthread.php?t=51256&highlight=sqlite

Actually, I do not know the place where it is possible to get compiled sqlite.so for newest PHP versions, so most probalby you will need to compile it. This is actually not so hard procedure, so you can try.
Hope this helps.
 
You should ignore folder_permissions_data=fail this message. As for error for modules, try to check Sitebuilder admin CP -> Logs section for more exactly errors after publication. Let me know which message can you see right after publication try.
 
this are the logs

Dmitry,

When i pueblishes i get this :
The site has been published with errors.
Cannot update modules data.

And in the log i get this.

6/16/2008 10:59:05 AM admin 201.170.142.183 Show view /Admin/Site/Edit
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Must be moved via redirect
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Action status: 2; Target: /Admin/Site/Edit?siteId=c70202eaa19d7778856c8aeb72604ff3; Messages: The specified site location has been checked. Publishing is available....
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Publication process finished....
System 6/16/2008 10:59:04 AM admin 201.170.142.183 The site 'amanteacida.com.mx' has been published, but with errors....
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Site entry has been prepared....
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Publication list has been saved....
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Site has been saved....
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Unnecessary files have been erased....
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Cannot update modules data....
System 6/16/2008 10:59:04 AM admin 201.170.142.183 Request result is: <pre>bool(false)...
Modules 6/16/2008 10:59:04 AM admin 201.170.142.183 Invalid server response: http/1.0 500 internal server error ...
Modules 6/16/2008 10:59:03 AM admin 201.170.142.183 HTTP connection has been established with host amanteacida.com.mx
Modules 6/16/2008 10:59:03 AM admin 201.170.142.183 Connection to 'http://amanteacida.com.mx/' is very slow. Total time to establish connection is 15 seconds.
System 6/16/2008 10:58:48 AM admin 201.170.142.183 Request prepared: <pre>array(4) {...
System 6/16/2008 10:58:48 AM admin 201.170.142.183 New RPC transport created....
System 6/16/2008 10:58:48 AM admin 201.170.142.183 Site publications have been updated....
System 6/16/2008 10:58:48 AM admin 201.170.142.183 Update storage states request prepared for: <pre>array(4) {...
System 6/16/2008 10:58:48 AM admin 201.170.142.183 Check and repair broken repositories request prepared for: <pre>array(4) {...
System 6/16/2008 10:58:48 AM admin 201.170.142.183 Clear repository request prepared for: <pre>array(0) {...
System 6/16/2008 10:58:48 AM admin 201.170.142.183 Modules folders have been created....
Modules
System 6/16/2008 10:58:31 AM admin 201.170.142.183 Publication process started....
System 6/16/2008 10:58:29 AM admin 201.170.142.183 Checking target finished....
System 6/16/2008 10:58:29 AM admin 201.170.142.183 Target environment has been checked successfully....
System 6/16/2008 10:58:26 AM admin 201.170.142.183 Request to main check script result: <pre>string(508) &quot;HTTP/1.1 200 OK ...
Modules 6/16/2008 10:58:26 AM admin 201.170.142.183 Connection to 'http://amanteacida.com.mx/' is very slow. Total request time is 15 seconds. The size of transferred data is 508 bytes.
Modules 6/16/2008 10:58:26 AM admin 201.170.142.183 HTTP connection has been established with host amanteacida.com.mx
Modules 6/16/2008 10:58:26 AM admin 201.170.142.183 Connection to 'http://amanteacida.com.mx/' is very slow. Total time to establish connection is 15 seconds.
Modules
6/16/2008 10:58:11 AM admin 201.170.142.183 New RPC transport created....
System 6/16/2008 10:58:11 AM admin 201.170.142.183 Main check script has been uploaded via FTP....
System 6/16/2008 10:58:11 AM admin 201.170.142.183 Checking of target environment started....
System 6/16/2008 10:58:11 AM admin 201.170.142.183 Connection to target checked....
System 6/16/2008 10:58:07 AM admin 201.170.142.183 Dangling block modules have been removed....
System 6/16/2008 10:58:07 AM admin 201.170.142.183 Publication settings checked....
System 6/16/2008 10:58:07 AM admin 201.170.142.183 Publication settings are valid....
System 6/16/2008 10:58:07 AM admin 201.170.142.183 Checking target started....
System 6/16/2008 10:58:07 AM admin 201.170.142.183 Try to execute action /Admin/Site/Publish



Thank you for your imput


You should ignore folder_permissions_data=fail this message. As for error for modules, try to check Sitebuilder admin CP -> Logs section for more exactly errors after publication. Let me know which message can you see right after publication try.
 
It seems the main reason for failed publication is following error:

Modules 6/16/2008 10:59:04 AM admin 201.170.142.183 Invalid server response: http/1.0 500 internal server error ...

As I understand PHP was updated to 5.2.6 version, is that right? Try to check apache error logs on destination server. Can you see anything there? It is hard to say exactly what can be the reason for this.
 
Segmentation fault

As far as I'm concerned, publication works but I sometimes get a blank page when visiting the published site. Apache error logs say :

[Fri Jun 20 15:19:19 2008] [notice] child pid 68208 exit signal Segmentation fault (11)
[Fri Jun 20 15:19:24 2008] [notice] child pid 68210 exit signal Segmentation fault (11)
[Fri Jun 20 15:19:28 2008] [notice] child pid 68211 exit signal Segmentation fault (11)
[Fri Jun 20 15:19:31 2008] [notice] child pid 68212 exit signal Segmentation fault (11)
[Fri Jun 20 15:19:34 2008] [notice] child pid 68213 exit signal Segmentation fault (11)
[Fri Jun 20 15:19:34 2008] [notice] child pid 68206 exit signal Segmentation fault (11)
[Fri Jun 20 15:26:30 2008] [notice] child pid 68207 exit signal Segmentation fault (11)

...even when the page is not blank. Tested with PHP 5.2.6 and PHP 5.2.4.

check.php :

ioncube=ok os= phpVersion=5.2.4 mbstring=ok zlib=ok session=ok dom=ok domxml_xslt=ok sqlite=2.8.17 sqliteEncoding=UTF-8 gd_png=ok gd_gif=ok gd_jpg=ok gd_wbmp=ok gd=2.0.34 safe_mode=ok mail=ok curl=ok serverApi=Apache Handler folder_permissions_data=fail

Any ideas ?
 
no luck

Dmitry,

I dint found any problem in the destination server.

I found out that the page with the photogalley dosent display the pictures or any information , it only displays the template , it looks like SB inst publishing the sqlite database.

Is there a way to fix this.

At this point i am willing to pay for assitance , how can we contact you.

thanks


It seems the main reason for failed publication is following error:

Modules 6/16/2008 10:59:04 AM admin 201.170.142.183 Invalid server response: http/1.0 500 internal server error ...

As I understand PHP was updated to 5.2.6 version, is that right? Try to check apache error logs on destination server. Can you see anything there? It is hard to say exactly what can be the reason for this.
 
Back
Top