wifang / mollify

Automatically exported from code.google.com/p/mollify
0 stars 0 forks source link

Unable to continue installation with backend installer. #449

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. After setting up the MySQL tables and mollify user, backend installer 
verifies the details of the database it will install in. It displays Host name, 
database name and the user correctly, however when I click the green "Continue 
Installation" button it comes up with a blank page.
2. Checking the MySQL tables I see it has created a "mollify_install_test" 
table with an "id" field inside.

What is the expected output? What do you see instead?
A page after clicking continue installation, and for it to propagate the 
necessary tables, fields, data, etc into mollify MySQL.

What version of the product are you using? On what operating system?
Mollify 1.8.9.3 on CentOS Linux 6.3

Please provide any additional information below.

Original issue reported on code.google.com by m4cr0...@gmail.com on 2 Jun 2013 at 2:42

GoogleCodeExporter commented 9 years ago
Sounds like something went wrong during db permission tests (those test tables 
are for this, and should be deleted after the test). Could you check your PHP 
error log what is the reason?

Original comment by samuli.j...@gmail.com on 3 Jun 2013 at 5:35

GoogleCodeExporter commented 9 years ago
Just added some permissions in mysql db (which allowed the process to 
continue), went through setting up admin credentials then attempted to open the 
backend/admin config panel, the header graphic is there with the logout link on 
the right, yet nothing else, completely blank below.

As for the error log:
The check.php reports - "Configuration file does not end with PHP end tag 
("?>"). Remove all characters after that tag."
However the file does end with that tag (minus quotes).

The debug log: 
{"code":100,"error":"Unauthorized request","details":"","trace":["MySQLi DB: 
mollify@localhost:mollify()","VERSION: 1.8.9.3 SERVER: {HTTP_DNT:1, 
HTTP_COOKIE:testing=1; sid=dd4be57efb10b2f2fb215f89dfd5bf61, 
SCRIPT_FILENAME:\/var\/www\/html\/Mollify\/backend\/r.php, 
SERVER_PROTOCOL:HTTP\/1.1, REQUEST_METHOD:GET, QUERY_STRING:, 
REQUEST_URI:\/Mollify\/backend\/r.php\/debug, 
SCRIPT_NAME:\/Mollify\/backend\/r.php, PATH_INFO:\/debug, 
PATH_TRANSLATED:\/var\/www\/html\/debug, 
PHP_SELF:\/Mollify\/backend\/r.php\/debug, REQUEST_TIME:1370242392}","SETTINGS: 
{debug:1, debug_log:\/mollify\/debug.log}","CONFIGURATION PROVIDER 
(MySQLConfiguration): supported features={0:change_password, 1:descriptions, 
2:administration, 3:user_groups, 4:permission_inheritance} auth=1","FEATURES: 
{limited_http_methods:, file_upload:1, folder_actions:1, file_upload_progress:, 
zip_download:, change_password:1, descriptions:1, administration:1, 
user_groups:1, mail_notification:, retrieve_url:, folder_protection:, 
guest_mode:}","FILESYSTEM: allowed_file_upload_types={}","SESSION: is_active=, 
user=NULL, data={}","AUTH: is_authentication_required=1, 
is_authenticated=","REQUEST: method=get, path={0:debug}, ip=<<MY IP>>, 
params={}, data=","SERVICE (DebugServices): is_auth_required=1","DB QUERY: 
select id from session where last_access < 20130603075312","ServiceException: 
UNAUTHORIZED=","{0:{file:\/var\/www\/html\/Mollify\/backend\/r.php, line:57, 
function:processRequest, class:MollifyBackend, type:->, 
args:{0:Request}}}","RESPONSE error {0:100, 1:Unauthorized request, 2:401} "]}

Original comment by m4cr0...@gmail.com on 3 Jun 2013 at 7:02

GoogleCodeExporter commented 9 years ago
Make sure the configuration.php does not have _anything_ after the "?>", no 
spaces or line breaks.

Original comment by samuli.j...@gmail.com on 3 Jun 2013 at 7:04

GoogleCodeExporter commented 9 years ago
There was an extra line, woops.
"Configuration file OK"

Despite this, the admin page is still the same.

Original comment by m4cr0...@gmail.com on 3 Jun 2013 at 7:10

GoogleCodeExporter commented 9 years ago
Try dropping all the tables in case it ended up in state which installer does 
not recognize (is there any errors in the log?), and run the installer with 
empty db

Original comment by samuli.j...@gmail.com on 3 Jun 2013 at 7:26

GoogleCodeExporter commented 9 years ago
Tried this twice just now to no avail, redid my admin credentials yet there is 
still nothing on the backend/admin webapge. The debug log which I posted half 
an hour ago is still the same as it is now (after refresh), 

Original comment by m4cr0...@gmail.com on 3 Jun 2013 at 7:36

GoogleCodeExporter commented 9 years ago
Actually the log you posted means that debug url requires admin user, it is not 
the log itself. You should get the log file from server

Original comment by samuli.j...@gmail.com on 3 Jun 2013 at 8:03

GoogleCodeExporter commented 9 years ago
Admin user, right, so how would I identify myself as admin to the r.php file?

Original comment by m4cr0...@gmail.com on 3 Jun 2013 at 12:04

GoogleCodeExporter commented 9 years ago
What I tried to tell is that the debug url is tool that require admin user 
(because it can contain sensitive data and should not be revealed to anyone 
knowing the url), and in this case it's not an option since you cannot log in. 

Instead, you have to get the actual log file from the server filesystem.

Original comment by samuli.j...@gmail.com on 3 Jun 2013 at 12:39

GoogleCodeExporter commented 9 years ago
Any progress on this?

Original comment by samuli.j...@gmail.com on 11 Jun 2013 at 5:59

GoogleCodeExporter commented 9 years ago
Haven't had the chance, will be able to continue this on Thursday/Friday, 
thanks for your concern!

Original comment by m4cr0...@gmail.com on 11 Jun 2013 at 7:25

GoogleCodeExporter commented 9 years ago
Closing as there is no futher info

Original comment by samuli.j...@gmail.com on 7 Sep 2013 at 9:28