Author Topic: New Game Server (CyberRock) till problem arises - Thanks to a misunderstanding!  (Read 773 times)

cyber.rock92s

  • Guest
Due to some misunderstanding I had during the past days (it is solved now)- thank you so much "A-Man" for installing the dependencies! - I am in the position to host another game server, called CyberRock till any problem arises and/or the owner of the VPS decides otherwise. Please wish that it doesn't  happen for a long time.

This one has pitiful specs but still even large games should work well since tomreyn and I tested it the last time (last stable release) and it passed the test without much problem. The only difference is, this time 'round, I have changed the priority of the headless so if other processes need resources, they will be given priority. It's hosted in Netherlands.

Please do tell me if you are facing any problem with this game server - I would be happy to help. Also, I will be happy to add any content (techtree, map, tileset, etc.) if you provide me with a direct link to it. Please leave a reply here or contact me on megaglest's official freenode IRC channel #megaglest for any request/complaint. My nick on IRC is Cyber_Rock.

Good Luck And Have Fun

--Cyber Rock

UPDATE:

The initiative was a failure, or so it seems. Therefore, the server has been removed.
« Last Edit: 24 December 2013, 06:30:38 by cyber.rock92s »

titi

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 4,240
    • View Profile
    • http://www.titusgames.de
What was the problem that made you stop this service ?
Try Megaglest! Improved Engine / New factions / New tilesets / New maps / New scenarios

cyber.rock92s

  • Guest
The headless was not registering on master-server when a game closed even after I used your script. The only thing that it did was that the process was not closing and was eating up resources. I told the admin to close the headless for some time so that he could evaluate whether it was giving problem to other processes. I thought he closed the process but seems like he didn't, because, few days ago the admin complained that the VPS had no space left and I was using ~26 GB of space. I looked around in my account and saw that the log file was taking more than 25 GB space. Well, the admin was angry on the game, and on me for hosting it  :( , consequentially he told me that I should delete the game and that was the end of it.

Sorry for all the trouble.

Coldfusionstorm

  • Golem
  • ******
  • Posts: 868
    • View Profile
Im sorry for you, Sounds like a shitty admin, Your user account should not even be able to take up that much space. It's a pretty standard procedure at webhosting providers that your account can't exceed what you have signed up for. :/.
WiP Game developer.
I do danish translations.
"i break stuff"

tomreyn

  • MegaGlest Team
  • Airship
  • ********
  • Posts: 2,764
    • View Profile
    • MegaGlest - the free and open source cross platform 3D real-time strategy game
I think this admin is the one who has root access on the virtual server Cyber_Rock has a standard user account on. It's also my understanding that Cyber_Rock (CPU) limited the megaglest process on this server using the nice command to reduce its priority when it comes to distributing CPU cycles amongst the running processes. While this seemed necessary to run it next to the other processes running on this server, it may also have caused side effects like players getting disconnected in the middle of a game or the server having trouble publishing to the masterserver and may have triggered many other error conditions. All of which can be logged to disk if you do not ensure the gameserver will not log them (or output to standard output/error, which, if the process was run by cron, will result in those messages getting dispatched to the e-mail address of the user who started the process).

While I recommended against this setup as soon as I learnt this is a shared system running additional services on limited resources, I also appreciate Cyber_Rocks' eagerness and intentions, and am sorry to learn the initiative he took did not work out and resulted in bad feelings.

This said, at least unless the MegaGlest headless / dedicated server is redesigned, please be sure to only run it on systems where sufficient resources are available, and do not limit it (bandwidth limiting the FTP data channel is OK). That's >=1 CPU cores operating at >=1.5 GHz with >= 512 MB RAM on Linux running no other services, and >= 5 GB free disk space (potentially more if you will do logging or allow the game to write memory dumps to disk).
atibox: Ryzen 1800X (8 cores @3.6GHz), 32 GB RAM, MSI Radeon RX 580 Gaming X 8G, PCI subsystem ID [1462:3417], (Radeon RX 580 chipset, POLARIS10) @3440x1440; latest stable Ubuntu release, (open source) radeon (amdgpu) / mesa video driver
atibox (old): Core2Quad Q9400 (4 cores @2.66GHz), 8 GB RAM, XFX HD-467X-DDF2, PCI subsystem ID [1682:2931], (Radeon HD 4670, RV730 XT) @1680x1050; latest stable Ubuntu release, (open source) radeon / mesa video driver
notebook: HP envy13d020ng
internet access: VDSL2+

· · · How YOU can contribute to MG · Latest development snapshot · How to build yourself · Megapack techtree · Currently hosted MG games · · ·

 

anything