enabling new domain breaks entire web server

[alternapop]

i have 34 working virtual domains on my 10.5.7 Server. i’ve duplicated one of the working domains and edited “Domain Name”, “Host Description”, “Web Folder” and both log locations for a new (35th) virtual domain.

enabling this new domain brings down the web server so that ALL sites are unreachable:

“Safari can’t connect to the server…”

simply checking or unchecking the box next to this new domain, and clicking ‘Save’, changes whether the web server is reachable or not.

i can’t figure out what is causing this.

any ideas?

thanks!

[premiermac]

What’s in the logs? Generally apache is pretty good about pinpointing the problem if you read the logs.

[alternapop]

[QUOTE][u]Quote by: premiermac[/u][p]What’s in the logs? Generally apache is pretty good about pinpointing the problem if you read the logs.[/p][/QUOTE]

the logs haven’t been helpful yet.

it’s acting like there is some sort of hard limit of 34 enabled domains. if i disable a currently working domain and enable the new (35th) one that isn’t working, it starts working. once i enable a 35th domain, it stops working.

[premiermac]

So there’s nothing in /var/log/system.log that says “apache”? Crank up the log level and try again.

[alternapop]

there was a “too many open files” error.

googling “launchctl limit maxfiles” provided the solution.

running either of these two commands shows the default limit of 256:

ulimit -a
launchctl limit

i created a new file (/etc/launchd.conf) with only this line within it:

limit maxfiles 4096 unlimited

then ran:

launchctl limit maxfiles 4096 unlimited

the 4096 number is just a starting point for me. it could possibly be smaller or higher but i haven’t tested any performance improvements/issues yet.

[premiermac]

Brilliant! The logs almost always have the answer in them.

[Author]

Posts