Clear OS always showing "Operation too slow. Less than 1 bytes/sec"
Solution 1:
There are yum parameters you can tweak to prevent the timeout error.
timeout=300 # default is 30
minrate=100 # default is 1000
However, if the rate you are achieving is really lower than 1000 and doesn't pick up later in the transfer (for example, a virus scanning proxy) then the transfer time for 1 megabyte would be on the order of a half hour or an hour. But, if you make the timeout long enough, at least it will finish ... eventually. If your transfer speed is less than 1B/s (as seems to be the default minrate with clearos) then your transfer will pretty much never finish anyway, unless hopefully it's a virus scanning proxy trickling data to you.
I'm on Fedora 19 and strangely the minrate setting never took, but by setting the timeout to 5 minutes, I was able to download 12 MB package file. The file transferred in 1:36, but was going under 200 B/s for most of that time and suddenly finished very fast (once the proxy virus scanner finished with it).
The idea is that the proxy will trickle your file at a very low rate to prevent connection timeouts while it does the virus scan, then transfer it at full rate once the file checks out. However, if the trickle rate is lower than yum's minrate, then you end up timing out anyway.
Solution 2:
From man yum.conf:
minrate This sets the low speed threshold in bytes per second. If the server is sending data slower than this for at least
timeout' seconds, Yum aborts the connection. The default is1000'.timeout Number of seconds to wait for a connection before timing out. Defaults to 30 seconds. This may be too short of a time for extremely overloaded sites.
You can reduce minrate and/or increase timeoute. Just add/edit these parameters in /etc/yum.conf [main] section. For example:
[main]
...
minrate=1
timeout=300
Solution 3:
I had the exact same problem. In my case it turned out I had yum configured to use a local http proxy, and that proxy was not operating correctly.
It was solved by simply editing /etc/yum.conf and removing the line starting with "proxy=". Obviously another way would be to fix the proxy server.