Forums / Install & configuration / permission issues during installation, followed by memory limit issues

permission issues during installation, followed by memory limit issues

Next topic

Author	Message
Jeffrey Ort	Wednesday 23 June 2004 10:24:51 pm This has been my first installation. I wish it has gone smoother, because I love what I have seen with the product, but I have continual issues. After my install, I received the Kernel 50 error, but was able to edit the .ini file to add the correct information. What was contained appeard to be the defaults. When logging in, I continually got the "Object not found" error. Although I had recursively set the mode of the directory to 777, I believe this had been a premissions issue, since the files simply were not there. Does anyone have any advice or suggestions how to properly prepare directory permissions for an install? Note, the fine tune reported no issues. Through great input from this forum, I was able to discover what was needed to force a reinstall, and several reinstalls later, things are now running, but with two issues: 1) I am getting an out of memory fatal error after some time. I have boosted the memory limit in my php.ini file to 24M, and still get this. 2) The installation is extremely slow. I am running on a virtual private server with 256M RAM, and there is no other traffic on this server (it is a test server). Loading the default "Gallery" page will take more than 60 seconds. Any help is greatly appreciated.
Balazs Halasy	Thursday 24 June 2004 4:19:14 am 1) Increase your PHP memory limit (set it to 0 / unlimited if this is possible). 2) Installation might be slow on some machines. Reason: template compilation is ON by default. This means that eZ publish not only shows but also compiles the templates that are requested - which leads to an extreme case (lot of I/O and CPU usage) when you're running the site for the first time or if/when you've cleared all the caches. Otherwise, the template compilation feature is quite fancy. So.. just sit back and relax, let it compile the things - after that: everything will be fater & smoother. :-)
Jeffrey Ort	Thursday 24 June 2004 8:51:51 am I will try to increase the memory limit. On compiling the templates though, shouldn't this only mean a performance hit the first time a page is viewed? It occurs everytime I view the same page? URL avaialble upon request, and thanks for the help.
Paul Borgermans	Thursday 24 June 2004 9:05:20 am Hi, Take a look at the template compiled files, you will understand why these take also quite a lot of memory to generate ... if I'm allowed to write this: it almost becomes a sort of assembler language implemented with PHP ;-) .. I'm amazed it still runs pretty fast. -paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans