search

ezcommunity / ezupgrade

GNU General Public License v2.0
10 stars 3 forks source link

Fatal error when upgrading a site with a large number of siteaccesses #13

Open kristofferbrabrand opened 13 years ago

kristofferbrabrand commented 13 years ago

When upgrading a site with a large number of siteaccesses the upgrade process fails with the error "Too many open files". The problem occured when upgrading a site with > 175 siteaccesses to ez 3.10.1 and happened after running the upgrade scripts for 3.9.4.

jheba commented 13 years ago

Hello Kristoffer,

It does not look like direct ezupgrade issue. I suggest you to investigate it in your environment. Good starting point is to increase a file limit in your system (search for "Too many open files" in google and for ulimit)

kristofferbrabrand commented 13 years ago

I've increasedthe number of file descriptors in the system (OSX) without it making a difference – I for nothing else, the issue should be noted as a known bug. I do think, however, that ezupgrade should operate in such a way that it doesn't require so many files if that's possible.

jheba commented 13 years ago

May I ask how did you change the limit (what command), what limit did you set and how many files ezupgrade opens for 175 SAs?

Kind regards Jaroslaw

kristofferbrabrand commented 13 years ago

I set the maxfiles limit in /etc/launchd.conf as well as running the ulimit command. I've tried so many combinations that I'm not able to provide the specifics of the commands run.

K

Den 6. juni 2011 kl. 15.23 skrev jheba:

May I ask how did you change the limit (what command), what limit did you set and how many files ezupgrade opens for 175 SAs?

Kind regards Jaroslaw

Reply to this email directly or view it on GitHub: https://github.com/ezsystems/ezupgrade/issues/13#comment_1309109

jheba commented 13 years ago

Thanks for the response Kristoffer. I am wonder if the deamon has to be restarted to make system aware of the changes in /etc/launchd.conf. With reference to the ulimit command, according to this forum post >> https://discussions.apple.com/message/7412308#7412308 ulimit does not work with OSX Leopard - launchctl should be used instead.

Kind regards Jaroslaw

kristofferbrabrand commented 13 years ago

I've restarted both the deamon and the machine more than once since chaning launchd.conf file.

Den 7. juni 2011 kl. 15.42 skrev jheba:

Thanks for the response Kristoffer. I am wonder if the deamon has to be restarted to make system aware of the changes in /etc/launchd.conf. With reference to the ulimit command, according to this forum post >> https://discussions.apple.com/message/7412308#7412308 ulimit does not work with OSX Leopard - launchctl should be used instead.

Kind regards Jaroslaw

Reply to this email directly or view it on GitHub: https://github.com/ezsystems/ezupgrade/issues/13#comment_1315751

cgjengedal commented 13 years ago

Spoken to Netmaking about this one and they would lke to have a look at it. Note that ezupgrade is being maintained by Netmaking on behalf of eZ Systems, so the maintenance of these issues will handled slightly differently from the regular eZ System processes.