Topic: SME 8.0 beta6 : OpenUpload installs ok but webpage is blank

[confiarus]

Installed OpenUpload on 8.0beta6 and it installed ok.  When opening the page using the following format: "https://myserver.domain.tld/openupload", I get a blank browser page which shows "done" at the bottom of the browser screen.

Used both IE8 and Firefox 3.x and had same results.  This is the only contrib I'd installed after installing SME 8.0beta6 .

Tried also using the ip address of the server (ex: https://10.168.1.11/openload), but, still
had same result.

Anyone have any ideas?

[Stefano]

what about searching into /var/log/httpd/error_log file for any error?

[confiarus]

Thank you for your reply.  I am a linux server novice but trying to learn.  I looked at the log and it doesn't show any error related to openupload.  Apache is working because the default page will display when I open it up in a browser  (This website is currently under contruction page).

I still just get a page with an HTTP 500 error msg

[Stefano]

take a look into /var/log/httpd/access_log

[confiarus]

Looked into the log.  First, I tried to access the page and then captured the log.  The result is shown below for this access attempt:

rcs.local 10.168.1.122 - - [28/Apr/2011:11:01:15 -0700]
"GET /openupload HTTP/1.1" 301 239 "-" "Mozilla/4.0
 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727)"


rcs.local 10.168.1.122 - - [28/Apr/2011:11:01:15 -0700]
"GET /openupload/ HTTP/1.1" 302 - "-" "Mozilla/4.0
 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727)"


rcs.local 10.168.1.122 - - [28/Apr/2011:11:01:16 -0700]
"GET /openupload/index.php?action=login HTTP/1.1" 500 - "-" "Mozilla/4.0
 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727)"

[cactus]

take a look into /var/log/httpd/access_log

I think you mean the error_log files, access_log only log access related data errors are redirected to error_log.

[Stefano]

I think you mean the error_log files, access_log only log access related data errors are redirected to error_log.

Hi cactus..

as stated here there's no evidence of errors in error_log..

[cactus]

as stated here there's no evidence of errors in error_log..

Oops, missed that. That is strange though, normally errors are logged there.

To OP, are you sure you checked the error_log entries around the time you tried? The error_log files are rotated, which means that the error could be in an older copy of the error_log file, with a name like error_log.x (x being a number).

[confiarus]

Yes, I checked all error logs in the directory.  See below my notes,

*********************************************************
At 01:51:33
From browser on another computer, browsed to http://10.168.1.11 (the sme server) to establish timeline only.

error log result.... (don't have an web page setup, so, this is expected)

[Fri Apr 29 01:51:33 2011] [error] [client 10.168.1.100] File does not exist: /home/e-smith/files/ibays/Primary/html/favicon.ico

[root@sme8 httpd]#


At 01:54:00
From browser on another computer, browsed to https://10.168.1.11/openupload.  Got Http 500 error as before.

error log result....

[Fri Apr 29 01:51:33 2011] [error] [client 10.168.1.100] File does not exist: /home/e-smith/files/ibays/Primary/html/favicon.ico


This is the end of the log and no error was logged because nothing was appended to end of the log.
Also, I did an ls -l to find the most current error log in the directory to search for errors.

[Stefano]

ok..

open a shell and login as root

go to /etc/ and edit php.ini

changing from

Code: [Select]

display_errors                         = Off
display_startup_errors                 = Off

to

Code: [Select]

display_errors                         = On
display_startup_errors                 = On

save file

restart httpd service with

Code: [Select]

service httpd-e-smith restart

try again.. you should see the error

when everything is ok, do

Code: [Select]

expand-template /etc/php.ini
service httpd-e-smith restart

b]NOTE:[/b] manual editing of configuration files is usually not a good idea.. this time is for debugging purpose only

[cactus]

NOTE: manual editing of configuration files is usually not a good idea.. this time is for debugging purpose only

See also: http://wiki.contribs.org/PHP#Display_Error_Messages

[confiarus]

Thanks for reply.   I edited php.ini and browsed to https://10.168.1.11.   The browser displayed the errors below:
********************************************************************************
Warning: session_start() [function.session-start]: open(/var/lib/openupload/tmp/sess_6c24cc13b5f0621b3e26dbe0c9ee46e8, O_RDWR) failed: Permission denied (13) in /usr/share/openupload/lib/general.inc.php on line 5

Fatal error: Smarty error: unable to write to $compile_dir '/usr/share/openupload/templates_c'. Be sure $compile_dir is writable by the web server user. in /usr/share/openupload/lib/smarty/Smarty.class.php on line 1092

Warning: Unknown: open(/var/lib/openupload/tmp/sess_6c24cc13b5f0621b3e26dbe0c9ee46e8, O_RDWR) failed: Permission denied (13) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/openupload/tmp) in Unknown on line 0
***************************************************************************

Before I modified the "php.ini" file, I saved it to "php.old" with the thought that once I'm finished with the debugging, I'd copy the "php.old" back to "php.ini".  Is it okay to do that?

Also, can you explain what the "expand-template /etc/php.ini" does?   I don't understand "expand-template".  I googled it but its still not clear.   

[Stefano]

I googled it but its still not clear.   

don't google.. read the wiki, search the forum and, of course, read the documentation

[confiarus]

In my previous post, the browse to location was "https://10.168.1.11/openupload" instead of "https://10.168.1.11"....just forgot to type in all of the info...

[cactus]

Thanks for reply.   I edited php.ini and browsed to https://10.168.1.11.   The browser displayed the errors below:
********************************************************************************
Warning: session_start() [function.session-start]: open(/var/lib/openupload/tmp/sess_6c24cc13b5f0621b3e26dbe0c9ee46e8, O_RDWR) failed: Permission denied (13) in /usr/share/openupload/lib/general.inc.php on line 5

Fatal error: Smarty error: unable to write to $compile_dir '/usr/share/openupload/templates_c'. Be sure $compile_dir is writable by the web server user. in /usr/share/openupload/lib/smarty/Smarty.class.php on line 1092

Warning: Unknown: open(/var/lib/openupload/tmp/sess_6c24cc13b5f0621b3e26dbe0c9ee46e8, O_RDWR) failed: Permission denied (13) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/var/lib/openupload/tmp) in Unknown on line 0
***************************************************************************

I am under the impression that you did not set the proper PHPBaseDir for your ibay. It seems the code you are using is living outside the scope of your ibay. By a protection mechanism PHP is not authorized to execute or access code outside of the tree it is invoked from, in your case most likely the html folder of your ibay.
Can you elaborate some more on how you installed openupload and where you have put the files?

Before I modified the "php.ini" file, I saved it to "php.old" with the thought that once I'm finished with the debugging, I'd copy the "php.old" back to "php.ini".  Is it okay to do that?

It is not a bad thing, but there is no need to. SME Server has a mechanism that generates configuration files based on templates that are supplied with values from the internal configuration database, normally the admin does not see this as this is handled by the server-manager panels.

Also, can you explain what the "expand-template /etc/php.ini" does?   I don't understand "expand-template".  I googled it but its still not clear.

It is the SME Server instruction to regenerate the configuration file you specify, in your case /etc/php.ini.