install.php - [Critical error – bailing out]

Post

Posted
Rating:
#1713 (In Topic #384)

localhost installation "install.php" error

I just tried to do a local install and received the following error.



I opened install.php in gedit. Line 120 says:
'cms/pages/comcode/EN/.htaccess'=>1663488,

php5 is installed,
mysql is installed,

Obviously, I know very little about this - could someone please kindly assist me in troubleshooting & correcting this error?

Thank you.

Last edit: by 0ntheL4ppy

Post

Posted
Rating:
#1714
Hi,

This one is a bit tricky for us to debug, as something is going wrong in the installers startup – but I'm going to look into it in detail for you. Is this as soon as you open the installer, or on a particular step?

Post

Posted
Rating:
#1731
This happened at the start as soon as I opened the installer.

I put the address "http://localhost/install.php" into the address bar, pressed Enter, and the first thing which showed was that error page.

The system is a relatively fresh install of Linux Mint 17.3, single-user install with standard admin-rights.

I changed permissions for the two files [install.php, data.cms] to root but there was no change in behaviour.

Post

Posted
Rating:
#1742
Thanks. It's likely some kind of issue with the hosting, with Composr trying to show an error about it, but it happening too early. I should be able to review it on Wednesday when I finish what I'm currently working on.

Post

Posted
Rating:
#1745
Thank you, Chris.

Let me know if you need any further information.

Post

Posted
Rating:
#1754
I'm still a bit bogged down (implementing a big feature change for v11), but thanks I received the PT - will look at this soon :) .

Post

Posted
Rating:
#1755
Thanks Chris.

Cheers.

Post

Posted
Rating:
#1757
I love any topic that has references to v11 when v10 isn't properly out yet. I can't wait to install v11 about a week after v10 gets released :D

Post

Posted
Rating:
#1774
Ok, I've nearly caught up now :sinner: . It should be tomorrow when I can look at.

Post

Posted
Rating:
#1776

KingBast said

I love any topic that has references to v11 when v10 isn't properly out yet. I can't wait to install v11 about a week after v10 gets released :D

We'll see :lol: .

Post

Posted
Rating:
#1777
Thanks Chris.

Post

Posted
Rating:
#1781
Hi,

I know this is unlikely, but is it possible you've run out of disk space or disk quota?

Post

Posted
Rating:
#1782
It seems to be 1 of a couple of possibilities. Essentially a basic file operation failed, even creating a missing directory, or writing to a file, and that happened before a key system had loaded. I'm running tests.

Post

Posted
Rating:
#1783
I'm pretty sure setting 777 permissions on the install directory will fix it. You're installing on a Linux server without suexec and there's a poor assumption about file access that's sneaked in. It's meant to do a silent fail, but currently isn't.

Post

Posted
Rating:
#1787
Yeah, that's confirmed.

Workarounds:
  1. Use manual installer, chmod documented directories in advance of running installer
  2. Enable SuExec on server
  3. chmod main directory to 777 before running the installer

It's a recent bug. We're writing to a non-critical cache file and failing, while we used to just silently ignore that.
It will be fixed in the next RC, very soon.

Post

Posted
Rating:
#1791
Hi Chris, thank you for taking some time for this.

Workarounds:
  1. Use manual installer, chmod documented directories in advance of running installer
  2. Enable SuExec on server
  3. chmod main directory to 777 before running the installer


There's lots of space on this drive,
manual installer downloaded, extracted,
*** I'm not sure what you mean by "documented directories",
apache2-suexec, apache2-suexec-pristine installed,
777 is set for www [/var/www]
 

Post

Posted
Rating:
#1792

0ntheL4ppy said

Hi Chris, thank you for taking some time for this.

Workarounds:
  1. Use manual installer, chmod documented directories in advance of running installer
  2. Enable SuExec on server
  3. chmod main directory to 777 before running the installer


There's lots of space on this drive,
manual installer downloaded, extracted,
*** I'm not sure what you mean by "documented directories",
apache2-suexec, apache2-suexec-pristine installed,
777 is set for www [/var/www]
 

See list of permissions on:

Composr Tutorial: Advanced installation

Open Source CMS with advanced social, interactive and dynamic features. Fully flexible, themeable and extendible: suitable for building powerful websites.

View



Or just do "sh fixperms.sh" from bash, the script will handle it.

Post

Posted
Rating:
#1793
Hi, Chris, thanks again.

ran sh command [fixperms.sh],
verified file ownership of files [find . -user root -exec chown user '{}' \;],
verified 777 for www, 777 is set [stat -c "%a %n" /var/www],
localhost/installer.php … error … two instances of "Call to undefined function do_lang_tempcode()"


set 777 for www recursively … success, installer starts (pretty blue page),
I'll start again and 777 each folder, one by one, to locate where the permissions issue is and report back,
 

Post

Posted
Rating:
#1794
Quick reply as I'm on my phone…

Sources/files.php
Sources/files2.php

From our github should resolve if you want to confirm.  Just overwrite and ignore installer warning about them being corrupt

Post

Posted
Rating:
#1795
Hi Chris, Ok, so now it's not working at all.

When I put in install.php it takes me to a copy of your github/install.php source code page - except it's from within my local address of localhost/install.php (as seen below in the image).



I very much appreciate your assistance, but I can't afford to put any further time into this. I know it's still a work in progress so I'll check back another time and try again.

Again, thank you for your time and assistance.

Best of luck.
0 guests and 0 members have recently viewed this.