That is definitely a possibility. We have clients that do this on a regular basis when they’re expecting a temporary spike in traffic. Just put in a ticket and we can get this taken care of for you. It would be best if you arranged this before the actual time period that you needed it for as a short downtime is required in order to upgrade your VPS.
When dealing with a script issue the best way to get the error output is to simply execute the file that is having issues on the server itself. In this case, the hoops_web.py is erroring out so if you login via SSH to your account and execute the script it will return the actual error.
I can see by your account that the script is already chmod’d to 755, so running it by typing the following into my bash terminal returns the following error:
./hoops_web.py: line 19: syntax error near unexpected token `(‘
./hoops_web.py: line 19: `urls = (‘
In this way you can see that there’s a syntax error on line 19 of the script which will need to be resolved before it’ll work as intended.
Now, in regards to redirecting the stderr output to a file, you can do this by simply executing the script like so:
[~/public_html]# ./hoops_web.py 2> error.log
By appending the 2> error.log you’re telling bash that you want to redirect the stderr output to the file error.log, which you can then open in your text editor of choice.
Please see our Resource Usage Policy at http://www.site5.com/legal/resource-usage/standard/ for our guidelines on email under the “Email and Mailing Lists” section. Any and all email being sent from our shared/reseller servers falls under these guidelines.
Our VPS’s have a separate Resource Usage Policy at the following URL which is free of many of the limits of shared hosting: