FAQ
From Fastsh.it
Contents |
[edit] I can't connect to my VPS, help!
What do you mean "can't connect"? How are you trying to connect and what type of error do you get? Please try these things before posting so you can help diagnose the problem.
- ping domain.fastsh.it from DOS/terminal
- Try logging in via FTP
- Try logging in via SSH (Putty or Terminal window)
Did these work? Is it just FreeNX that won't connect? NX is not the most reliable and this is across the board from our very first OVH server that I still use. Just give it time and try again later, there's no solution for it. NX is going to be replaced very soon with VNC instead which should prevent a lot of these RDP connection issues.
If nothing above works/responds, we can do a reboot (you will be able to do this yourself soon through an API). If you can't do anything but still have SSH access, login to your server and type 'sudo reboot' to restart your own VPS.
[edit] Why isn't my BitTorrent ratio going through the roof?
While a hosted server is great for achieving throughput when connected to similarly fast peers, it's not an instant fix for ratio.
There are a large number of factors that come into consideration with your BitTorrent speed, here's just a few that we have noticed:
- Number of active peers
- Number of active leechers
- Number of partial pack leechers/seeders
- Overall number of seeders
- Maximum download speed of the peers connected to you
- Client settings. Do you have a maximum upload set, number of active connections, disk cache settings etc? Each client has it's own settings and after tweaking them a number of users have fixed their speed issues. Read the Tutorials and other speed threads here to find common issues you are experiencing, and try what they have tried or has been suggested in the past.
[edit] Could not lock session directory: "/home/username/session/", held by "s-lu-0.fastsh.it:+1234".
This error is commonly encountered starting rtorrent after a crash, kill, reboot, or other unexpected termination where rtorrent fails to remove its lockfile. *FIRST* verify that rtorrent is not already running (perhaps in a screen?):
ps -ef | grep rtorrent
Look for an rtorrent process associated with your userID. If you don't see one, then the lock file is stale. To resolve the issue, remove the stale lockfile:
rm ~/session/*.lock
[edit] Is my box throttled since the recent network upgrade?
No. It's not.
I know "network upgrades" seem like a convenient explanation for random.torrent being slow for you, but it's not the explanation, it's baseless paranoia :P For example, s-lu-9 (suspected by multiple users to have been throttled, and not even impacted by the upgrades!):
6272349 9891033 10409684 7869096 6842214 <snip> 6760028 9585076 11184457 8486630 7463300 7943840 6841290 6441449
Each number is the average of traffic over a 10-second interval in bytes/sec. As you can see total upstream traffic is hitting over 11MB/sec at times. This is clearly not a throttled box.
To investigate the cumulative upstream for your own box, you can use the following shellcode snippet:
DT=10; while true; do X1=`cat /sys/class/net/eth0/statistics/tx_bytes`; sleep $DT; X2=`cat /sys/class/net/eth0/statistics/tx_bytes`; echo $(( (X2-X1)/DT )); done
Modify the value DT to change the sampling window. Change the "tx" to "rx" to monitor downstream traffic.
Unless the numbers you see from this seem to be limited to a maximum that is repeatable within a couple percent over numerous samples (and never exceeded by more than a couple percent), the box you are on is not throttled. If the numbers are not less than 6250000 in ALL samples, it is very unlikely that your box is throttled. If you happen to see figures on your box that do encounter the same maximum within a couple percent, please contact us for further investigation.
Figures cannot be collected for the VPS physical servers directly by domain users, but rest assured that we have not been able to identify any throttling currently occuring there either
[edit] Why is FTP so slow?
Bittorrent, by its nature, uses a lot of connections. Since bandwidth is distributed evenly between connections, this means that a single FTP connection is severely disadvantaged, resulting in slow speeds. To get around this, use an FTP client that supports multiple connections, such as CuteFTP (Windows only).
