500 player <cap?>

Not sure what the exact problem is but every time we reach 500 players the proxy just drops entirely and has to be restarted? I'm writting a script right now to auto restart it, but it seem really weird to me that it's dropping like that. Any info i can give you to help you figure out why this is happeneing? the server ip is play.baconmc.com if you want to see for yourself, just watch the number rise, at 500 the proxy drops, every server is fine, it's just the proxy.

I remember this happening before to someone, but I believe it was 250 players or 350. Just to double check, is there any errors on the crashes? Or does it just stop? And, how much ram are you giving the connect/proxy?

to be honest i don't know how to set the ram for the proxy to use with goLily it's on a 32 gig box with just the hub server and the hub itself is using 24 gigs

Well, that might not hurt to go check. But, the best thing to do would be to find out if there is an error when it crashes, and to get that error. Than we can identify this problem.

If golily saves logs somewhere i have not yet found it and it cancels too quick to see it, as for setting the ram for it i have checked all the documentation and it doesn't say anywhere how to designate how much ram is dedicated to it.

http://www.lilypadmc.org/threads/read-me-what-you-need-to-know-before-posting.353/

GoLily doesn't generate a log, however, I am assuming you are using screens, you can log everything that happens in a screen: "-L".

I did not believe it needed ram dedicated to it like with java, the previous poster made me think i might have been wrong. I have no idea how to get version with golily since apt-get doesn't include version numbers. the description of the issue is very adequate, as soon as 500 players connect the proxy completely stops. If i knew the reason why it was happening i wouldn't be opening a support ticket.

I did specifically ask in the starting post what you needed me to provide for you to help you get to the bottom of the issue. Coming back with an atitude of why I have made it impossible for you to work off it does not help the issue get resolved at all.

The_Zip thank you for that info, i didn't actually know about -L in screen to generate a log, does it accept arguments to log it to a sepcific location?

I do not believe there is, off of a quick google search I didn't seem to find a way to change the location. You can only change the name.

allright appreciate you looking into it. Soon as i get a log of what is happening i will make sure to post it, gotta get up to that player amount again though

I assume you are using linux.
I also assume you have FULL access to the startup script.

If this is true then use this:

#!/bin/bash
lilypad="{Lilypad Directory}"
log="Log_Dir/LilyPad-Connect.log"

cd $lilypad
./connect-linux-amd64 >> $log

{Then what ever else}
that will output it to the log file

yes and yes though mystartup script is very simplistic

# /bin/sh
while true
do
java -Xmx16G -jar spigot.jar nogui
echo brief pause
sleep 3
done

^startup.sh

screen -d -m -S hub ./startup.sh

you said it was lilypad having the problem not spigot

sorry the second half of your post didn't come through initially for some reason, i wasn't using a startup script of any sort for lily was just running it in a screen but i could set one up

You could, but if you already set up the screen logging into a file there is no need. However, @Creepers-Help suggestion can log it into a location that you want, therefor his solution might be the better so we can find this error.

Oh Sorry I miss understood, but yes it would be a smart idea to set one up for LilyPad also.

Hi there;

I have a few questions about the issue. When you say 500 players, do you mean legit *500* players, or maybe 499? 503? If its 500 its probably a software problem, if not I would assume its not.

What is the processor you run the proxy on? Is there any output to the console when this happens? Is it reproducible (preferably with Spigot's bot tool)?

If you can reproduce it, I'd like to see the output of the "debug" command. That prints out a few software stuff we might be able to use.
And this is for the proxy, right? Not the connect?

@boboman13 I believe it was the proxyHighlighted proxy)

However @diannafire lets just see a error so we can identify the problem and fix it.

Error during listen accept tcp [::]:25565: too many open files
Its off..sleeping for 5

this is the only error i get when it shuts down. version, was just downloaded with apt-get this morning.

and it is at exactly 500 players on the network

set the player limit to 499 and it still happened - so it's just around the 500 player mark

System:
CPUIntel Xeon
2x E5-2650v2
Cores/Threads16 / 32
Frequency /burst2.6 GHz+/ 3.4 GHz+
RAM128 GB DDR3 ECC

Free ram at time of latest crash 68g

hope this helps at all?