Thanks for your advive, however I already checked all those things:

1. In /home/user/php.ini:
   memory_limit = 256M
   upload_max_filesize = 64M
   post_max_size = 64M
   max_execution_time = 7200
   max_input_time = 600
2. phpinfo() shows that /home/user/php.ini is loaded
3. apache has been restarted
4. Checked and reset the permission on the /var directory+
5. I am not doing an installation, eZ Publish has been running for a long time. I just want to upload a new package. Furthermore, the script memory limit seems high enough.
6. I am not remotely fetching packages, I add them manually from the admin interface
7. I am already running the latest version of eZ Publish
8. Version 4.3 is installed
9. Nope, running CentOS
10. Any other ideas??????

Hi Jeroen

I frequently have issues with packages and try to avoid using them most of the time.

Anyway, what do your log files say ? Take a look at eZ Publish / Apache log files. You might want to log your PHP errors separately from Apache. To do so, in php.ini, log_errors must be on and error_log must point to a dedicated log file.

You might want to run top and ps to see what else is happening on the server.

The reply has been removed because of violation of forum rules.

The reply has been removed because of violation of forum rules.

You may want to consider using shared hosting.  It isn't that expensive, and then your site will be accessible from everywhere.

Make sure the php.ini you quote is the one in use - via a web page is the best way to make sure it is.

Check of course the server logs (apache, php, mysql, other), to see if there is any problem related eg. to fs permissions. When ez can not create caches results are unpredicatble.

ps @Betsy in my experience shared hosting is really a hit-and-miss with eZ, as the requirements of the CMS are pretty beefy, and most cheap shared-hosting plans do not meet all of them

@Gaetano - I agree, shared hosting is a gamble.  I've been running eZ on shared hosting for over seven years.  This year I upgraded to eZ5 and had to find a new hosting company.  I was fortunate to find one that runs it well.

Another serious risk of shared hosting is that you have no control over the server.  Many years ago, three important eZ installations went down because the hosting company updated PHP.  PHP upgrades may also cause .ini changes.

I use shared hosting because it is so inexpensive, and I can move the site quickly if necessary, but it isn't for the faint of heart.

Modified on Saturday 14 December 2013 2:33:45 am by Betsy Gamrat

The reply has been removed because of violation of forum rules.

The reply has been removed because of violation of forum rules.