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...
|
Threaded Mode
