Forums / Install & configuration / infinite installation loop

infinite installation loop

Author Message

Nicolas Heiringhoff

Thursday 16 September 2004 4:54:35 am

I am not installing eZ publish for the first time, so i wonder what went wrong this time: on one of our new linux servers i end up in an infinite installation loop. I select the site ("plain" for example) and eZ publish tells me, that the installation is finished. When I try to access the user site I always get the installation setup screen. Infact eZ does not create the site with the folders, etc that I have choosen. We have tried it on a local Windows machine and everything is fine. Any hints for me? I can not figure out what is wrong!

http://www.heiringhoff.de

Bård Farstad

Friday 17 September 2004 12:49:17 am

This sounds like the setup is not able to write the file settings/override/site.ini.append after installation. Could you check that this file exists and contains CheckValidity=false?

--bård

Documentation: http://ez.no/doc

Nicolas Heiringhoff

Friday 17 September 2004 1:12:52 am

Hello bård,

thanks for your reply. settings/override/site.ini.append exists, but it is empty.
Which rights should it have? After the non-finished installation it has 666. Is this okay, or should it be 777?

Nico

http://www.heiringhoff.de

Sven O. Rimmelspacher

Sunday 19 September 2004 1:06:25 pm

PMFJI, but I have the same problem. I tried it several times (with the newest download of ez) and got also the infinite loop.
The file settings/override/site.ini.append you mentioned above does not even exist here, the folder is completely empty.

Sven

Nicolas Heiringhoff

Monday 20 September 2004 2:03:43 am

Since we have tried to install eZ on our new webserver for almost 20 times without success, (with different minor ideas of what might have gone wrong) we will now reinstall the OS (SUSE Linux 9.0) on the Webserver and try again.
We have an "Strato High End Server" (just as an info for users, who might have the same problem).

http://www.heiringhoff.de

Kåre Køhler Høvik

Monday 20 September 2004 3:56:13 am

Sven : sounds like a permissions problem.

Nicolas : permission 666 is ok. Which version of apache/PHP are you using ?

Kåre Høvik

Nicolas Heiringhoff

Monday 20 September 2004 5:07:02 am

we are using Apache Version 2.0.48 and

# rpm -qa --last | grep php
apache2-mod_php4-4.3.3-50 Mon May 10 13:59:08 2004
mod_php4-core-4.3.3-50 Mon May 10 13:59:05 2004
phpdoc-4.3.0-37 Mon May 10 13:57:09 2004

OS is SUSE 9.0

http://www.heiringhoff.de

Nicolas Heiringhoff

Tuesday 21 September 2004 2:03:41 am

Well, nothing new here. We installed the Server completly new, but we end up in the same installation loop again. We set the rights to 777. The funny thing is, that we have another server with exact the same OS and PHP and Apache versions (it is the same "Strato High End Server Package" with an smoothly runnning eZ Publish 3.4.1 version. Now that we have run out of ideas, we'll just wait for 3.4.2. or even 3.5.

http://www.heiringhoff.de

Nicolas Heiringhoff

Tuesday 21 September 2004 7:36:03 am

I am sorry for this kind of monologue here.

Maybe it will help someone else in the end.

I actually stumbled over a little difference between our two servers:
the one that creates the "infinite installation loop" uses a slightly different php-version:

# rpm -qa --last | grep php
mod_php4-core-4.3.3-177 Mon Sep 20 15:07:52 2004
apache2-mod_php4-4.3.3-177 Mon Sep 20 15:07:49 2004
phpdoc-4.3.0-37

But it this really the cause for the loop?
It seems like the setup-script that creates the folders and the other stuff, does not work or does not have the rights to work properly.

I compared the rights in /kernel/setup and they are the same on both servers.

Hm.

http://www.heiringhoff.de

Marco Zinn

Tuesday 21 September 2004 1:38:55 pm

Nicolas,
this is really strange.
That sound like some permission problem or maybe some file handling problem (as the file exists, but it empty).
Some special things about the path's ? Too long? Weird (german) characters somewhere? Different virtual Host setup (safe mode, openbase_dir, something that could affect the filesystem functions)?
Can you create or edit the site.ini.append manually?

Marco
http://www.hyperroad-design.com

Nicolas Heiringhoff

Wednesday 22 September 2004 7:03:54 am

Yes, we can edit the site.ini.append.php with pico.

We have inserted some echo commands in the ezdir.php in the function doMkdir

function doMkdir( $dir, $perm )
{
include_once( "lib/ezutils/classes/ezdebugsetting.php" );

$oldumask = umask( 0 );
if ( ! @mkdir( $dir, $perm ) )
{
umask( $oldumask );
// eZDebug::writeError( "Couldn't create the directory \"$dir\".", "eZDir::doMkdir()" );
echo "<br>+-<br>| whoami=" . exec('whoami') . "<br>";
echo "| pwd =" . exec('pwd') . "<br>";
echo "| id =" . exec('id') . "<br>+--<br>";
echo "Couldn't create the directory \"$dir\" with ";
printf("0%o<br>", $perm);

return false;
}
umask( $oldumask );

return true;
}

It returns the following output (example) when the installer is finished (after the click on the "send registration" button:


+-
| whoami=e20090401372142
| pwd =/home/i/iddis.de/ezpublish-3.4.1
| id =uid=500(e20090401372142) gid=60006(www) groups=60006(www)
+--
Couldn't create the directory "design/news" with 0777

so the installer script seems not to be able to create the the proper site.ini.append.php
and the directories of the choosen installation (for example "corporate")

we set the rights of the design, settings and var directories to 777.

There has to be some kind of other restriction to the setup script, but which?

For today we run out of new ideas.

http://www.heiringhoff.de

Kåre Køhler Høvik

Wednesday 22 September 2004 7:14:40 am

Whats the access rights for the design catalog set to ?

Kåre Høvik

Nicolas Heiringhoff

Wednesday 22 September 2004 7:34:30 am

well, actually I do not know where to look for the rights of the "design catalog"

http://www.heiringhoff.de

Nicolas Heiringhoff

Friday 24 September 2004 6:52:32 am

Finally we found a solution to our installation problem.
Our user did have the right to login. We used "YaST" to compare the rights of the user. The settings were:
"Login-Shell
/sbin/nologin"

We changed that to
"Login-Shell
/bin/bash"

an now it works.

Nico

http://www.heiringhoff.de

mathew moule

Sunday 13 December 2009 3:19:59 pm

where did you find Login-shell etc as i cant find it. Im having the same problem, either no install or plain package just loops. This cms looks like the best thing in the world, but its a ttal PITA to install.