Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
kristofferbrabrand opened this issue Jun 6, 2011 · 7 comments
Labels

Comments

@kristofferbrabrand
Copy link

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
Copy link

jheba commented Jun 6, 2011

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
Copy link
Author

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
Copy link

jheba commented Jun 6, 2011

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
Copy link
Author

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:
#13 (comment)

@jheba
Copy link

jheba commented Jun 7, 2011

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
Copy link
Author

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:
#13 (comment)

@cgjengedal cgjengedal reopened this Jun 15, 2011
@cgjengedal
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants