After checking the logs, I found that the crash was due to the server going OOM. Apparently allocating 1.5GB of memory to the server isn't enough. This is getting kind of ridiculous... bukkit needs to tighten up their code.
not trying to act like I know what the server side minecraft is like, but my minecraft java environment regularly hits 1gb, so if anything is a problem with leaks I would first look at minecraft, not the good people at bukkit.
That's because the client side handles all the graphics. Graphics are memory and computationally intensive (thus the need for dedicated GPUs and whatnot). The server shouldn't be as bad. The fact that it's built in java doesn't help anything of course. Also, since the server is running bukkit, which is a complete rewrite of the minecraft code (afaik), it wouldn't be Mojang's fault anyway as it's the bukkit developers code.
I did some digging around and it seems the original developer of BigBrother abandoned it. Someone else took the project over but there are massive reports of their latest code being bad bad bad. Also possibly the cause of the server constantly going OOM. I took the server down, converted the BigBrother data to LogBlocks format and installed LogBlocks as it appears to be the better choice going forward. Things should be back up now.
Once again, bukkit managed to exhaust it's memory limit. I realized that I was not running the most recent recommended build of bukkit and updated it. Maybe that will help with the memory usage. If not, I'm going to have to look into getting more RAM for the server which is not necessarily something that I can afford right at the moment.
It's lagging out again already. Was able to 'build' one tree and cut it down, but within 30 seconds of that, I was unable to influence the environment at all again.
I don't know how or why... but it seems the vPlayersOnline plugin (the one that gives us /list functionality) caused your earlier problem. That plugin was abandoned a while ago so I removed it. Going to have to find a new plugin to replace it =/
I know when I first set up the server, it wasn't built in which is why I added the plugin. I'm pretty sure the plugin ran /who as an alias for /list, but I could be wrong.
Icrontian
edited April 2011
shrugs
I know when I first set up the server, it wasn't built in which is why I added the plugin. I'm pretty sure the plugin ran /who as an alias for /list, but I could be wrong.
Comments
I did some digging around and it seems the original developer of BigBrother abandoned it. Someone else took the project over but there are massive reports of their latest code being bad bad bad. Also possibly the cause of the server constantly going OOM. I took the server down, converted the BigBrother data to LogBlocks format and installed LogBlocks as it appears to be the better choice going forward. Things should be back up now.
I know when I first set up the server, it wasn't built in which is why I added the plugin. I'm pretty sure the plugin ran /who as an alias for /list, but I could be wrong.
I know when I first set up the server, it wasn't built in which is why I added the plugin. I'm pretty sure the plugin ran /who as an alias for /list, but I could be wrong.
Though it is more likely that it is I who is wrong
http://bit.ly/f4xk52
Pop it in your bin folder and you can still play on the server.
As soon as the bukkit team promotes a 1.5 build. See their website for updates. http://bukkit.org
What of it?
http://ci.bukkit.org/job/dev-CraftBukkit/733/