Closed AngellusMortis closed 11 years ago
Could not reproduce. I've 3 servers running just fine. http://puu.sh/4MxB0.png Edit: I am using Windows though which I seem to have skipped over the first time I read your post.
That is on Windows. It works fine in Windows for me too. I am having problems on CentOS using mono.
are you running out of memory and swapping?
How would I check that?
It is unlikely it is happening though. The server has 3GB of RAM.
you can try 'sar -r 1 1' , or if you don't have it you can try 'free'
3GB may be enough, depending on what else runs on that machine.
Yep. That is the problem. I also have a Web server and such on the my VPS so they were going over the 3GB. It looks like the 1.2 takes much more RAM now. I use to be able to run TShock on 512MB dedicated, now it looks like it uses around 600MB-1200MB now.
Maybe you could try to catch it running out of memory and safely save the world/throw error message before crashing? The worlds were crashing without saving, it was instantaneous.
Anyways, thanks for the help.
I'm running the whole time since a 2nd server since tShock updated to 1.2. Both are working very well and I ran earlier the 2nd server for testing... There shouldn't be a '2-instances-problem'.
Waiting till tShock will be stable and more plugin updates to shut down the main server.
So, I am running TShock 4.2-pr14 (latest) on CentOS with mono. I have two separate "installs" of TShock in two different directories with two different worlds, configurations and everything for each. One is bound on port 7777 and the other port 7778. Whenever both of them is running at the same time, the server on port 7777 just stops running for seemingly no reason. There is no error messages in either of the server logs, nothing.
I think it has something to do with the SQLite storage adapter. After resetting the server on 7778 completely, it worked until I tried to add a user.I can switch to using MySQL, but these are rather small scale servers (mostly personal) and I do not see that as necessary; I should be able to use SQLite.EDIT: It seems it has nothing to do with the SQLite, when I run it with MySQL, problem still occurs.