SharedMemory issues

[John Adams]

This does not appear to be getting the attention it deserves. Real pain in the ass having to wait til your server starts completely, to take it down, then restart it because of this mysterious error. I can't even tell you something is actually wrong, just the message states to restart the servers.

All you Windows-hating NIX gods out there, have no advice for us? I'd like to see this resolved as well. Do we need a bigger shmmax now?

[cubber]

I had this corrected on my box for quite a while by upping the value, then after an update it reappeared. No matter how high I put the setting it always pops back up. I just have bitten the bullet and now just accept it as a process I need to do each time I have to start the server after a reboot.

It does suck! and has been a known bug for about a year now. I don't even start my login server anymore until after I run the server once to get rid of the error. Then I put up my login server and restart the server clean.

What I want to know is what does the startup script actually do to "fix" the issue when it errors, and has you restart after saying:

"we can build it stronger faster... restart all servers"

Couldn't this "adjustment" be applied right from the start to prevent this from happening? Obviously something is fixing the issue after the first run, so you can run it a second time without the error...

[cubber]

On a side note if you watch your crashlog file you will see a crash reported when the startup happens and you get to the error point. Then the server actually goes through the process of restarting itself, so you really don't need to stop then start it again. I just do it for sake of cleanliness.