Ask questions about dedicated servers here and we and other users will do our best to answer them. Please also refer to the self-help section for tutorials and answers to the most commonly asked questions.
moxie2020 wrote:Will rsyncing work if they are different bit types? If not I am fine with doing a reinstall but not sure how to do that remotely.
I suspect that it won't, but it's possible that it would. It's worth trying before you try a new install.
The new install would have to be done by choosing an .iso on the "Server control" page, booting from it, and following the various installation steps. Since we don't normally offer 32-bit distributions, you would need to open a support request to have us download the one you need for you and make it an option on the drop-down.
moxie2020 wrote:Will rsyncing work if they are different bit types? If not I am fine with doing a reinstall but not sure how to do that remotely.
I suspect that it won't, but it's possible that it would. It's worth trying before you try a new install.
The new install would have to be done by choosing an .iso on the "Server control" page, booting from it, and following the various installation steps. Since we don't normally offer 32-bit distributions, you would need to open a support request to have us download the one you need for you and make it an option on the drop-down.
Rsync did not work. I submitted a request.
I can't believe I am the only one having this issue with 64 bit Ubuntu, TF2 and Sourcemod. Even if the bots are the trigger it is pretty standard practice to keep bots on empty servers.
I have to imagine others are experiencing this issue and either manually restarting constantly or giving up. I did at least 20 clean installs from OS to Vanilla TF2 to TF2 plus Sourcemod with just included plugins and the crashes begin everytime I add sourcemod.
I haven't heard of it from others here, but Ubuntu 12.04 is still a fairly new OS, so the bulk of our customers are not running it. Additionally, for our managed servers, we use Gentoo.
Were you running all of the latest updates? If this is a bug that crops up under only a specific Ubuntu release, it might be an issue with a specific version of a library that they are including (possibly a newly-created one, or one that has been already fixed with another new version), and worth filing a bug report with Canonical.
