Web proxy cache

RouterOS General
1

I’ve noticed one of my routers isn’t as fast as it used to be and am investigating to find out what the problem is.

The router is a 433AH with a 4GB microSD card. The unit is running transprent web proxy, with unlimited cache on the SD card. The router is also running User Manager.

If I set the value of the web cache to “none” the end user’s internet experience is good. If I switch the web cache on, the end user’s internet experience is pretty awful.

My whole network runs on ROS 3.22

Any ideas why?

More importanly, any ideas why just this router? I have several that have the exact same configuration. The others are going quite nicely, but this one’s lagging.

help... until now i'M not contenting of my cache work!!!!
compatible microSD
SLOW Webproxy cache with CompactFlash
2

Please see this http://wiki.mikrotik.com/wiki/Supported_Hardware#Memory_cards + http://wiki.mikrotik.com/wiki/Image:Proxy_not_caching_with_incompatible_storage.gif
maybe its a microSD card problem?

Please post some screenshots of the proxy etc.

3

Basically the same as the link.

But mine gets better, I’m getting lots and LOTS of these in my syslog - after which the machine reboots itself.

What do I do?

2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/1/1d/1dfbd559d4ea666b2d22b84f2c1b9f95’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/1/1f/1ffa6b2703a2f08ef3da41c546add7ab’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/2/24/244978fe22f4a306569785dda424f632’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/2/27/27bf9f2e64ce9b41623942f28e52e480’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/2/2c/2c19b7e6e3b732e84269b5aade902a5b’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/2/2c/2c7a63e49dbf62467c97d0be736b984f’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/3/34/34e655098147688302f5a383376fb892’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/3/36/365549b97c9d79bab6538da296a8790f’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/3/38/38582c5e28d11be4e63f74e75459f8f7’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/3/3c/3ca99b179e559876e186ccf82e9d6c30’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/3/3c/3c83d11bde0a23f92253173b5b6a45a1’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/3/3f/3fa5474c661f1c54a7a30c3f3e8d9fde’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/3/3f/3f7f37fa53ab0b10ae1dd15bb5a4add9’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/4/41/4185d180d61132fb6d4fe4e1c3cd6ebb’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/4/46/465d2bd9e3d1fcb2a3d5f63ecf6e46d6’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/4/4a/4a12ffa4e543ffbd8de077a6811861e2’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/4/4b/4b2695b2e08af9708d5c14cc1241fecb’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/4/4b/4b1c097814211c3b6cf06cdb2f033141’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/5/50/50b969ab03c1546a860d88ddeb733d4b’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/5/51/51d7cd6deecee5e58798d09db5c39c51’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/5/53/537367da2f5afc628e9ee617244acbd1’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/5/56/568da7c2ac7b0f37e7c943a18242ca1d’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/5/5b/5b55ef5ace9dc714e349ac67c694baa5’) failed: Stale NFS file handle
2009-04-22 21:09:28 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/5/5c/5c4b852e66e2bbb0505c9d769475950d’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/b/b4/b451e1a8d3333f324ffeb1bc2d85702b’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/d/d0/d0d11b3a41336c21684fb339bc29cbea’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/d/d3/d35dc41f865b82632020e0f299b12a04’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/d/dd/ddd47a0ce4ae35e7c8d09a13d0c4bade’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/d/dd/dd8469834628fe662a000368da461f8f’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/e0/e04e969f7bd5f57f05033ed1314df66c’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/e1/e1f0da2c0977090763c8448bb6dfc1d0’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/e1/e1604f2596df88aafbf3c57213957953’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/e3/e39f724e1737f8bb5890c28012c9e4b6’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/e4/e4a9b12df02064c74379a3001401b921’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/ec/ec273a41bdf19dc51f23e8076e4afd62’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/ed/ed9bae65909c7c29d707ee736a1f2028’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/ef/efa3fee4d966e737c79029c717a24e3d’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/e/ef/efbc3f8af8646350f7a72affc3a2f93d’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/f/f0/f06995feb9803dd37b809df29b38d864’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/f/f7/f7c3210cb9fffdcb59acbcc15f0730b0’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/f/f9/f94b7d27bec524b4d28275d0c1c03661’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/f/fa/fa0c419d66166e2ca7b65a47558ddb8e’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/f/fb/fb3cefe086508f72717e4a1e0d8d062c’) failed: Stale NFS file handle
2009-04-22 21:09:29 Local7.Debug 192.168.75.254 web-proxy,error CC_HP-1: stat(‘/mnt/disk2/microSD-proxy/f/fd/fd43513616d0d358cfa4bfff880f2849’) failed: Stale NFS file handle

4

Try “Clear Cache” from the proxy, or Format from “Stores” :slight_smile: If it does not work after that - replace the microSD.

5

Both disc write options fail due to the drive being “busy”. We’re waiting for the rain to stop so we can go and remove the microSD. I don’t understand why it worked so well until I upgraded to 3.22

6

Maybe the microSD is at the end of its life? How long have it served your caching needs? Has it been used for something else before that?

7

Commissioned on 27 Jan 2009. Brand new, out of the box.

8

It will not hurt to test with an earlier version. Upload the old packages and it should downgrade OK.

9

But not over 146 RB’s :frowning:

We have a policy of running the same version on all our boards and our client boards.

The card’s on my desk. I’ll pop it into a phone later and see if it works properly there.

10

Why not downgrade only the problematic RB?

Did you put another in the RB, does it work now?

You can test it with a mircoSD to SD adapter on a PC as well, since there you have more control to format it and speed test it, see bad sectors etc.

11

It goes against our company policy to run different versions of operating systems in production enviroment. I just run the place. I don’t decide policies.

I left it out. With so many web pages being dynamic these days, I think the days of web proxy cache may well be behind us.

My widescreen Dell laptop with the inbuild SD reader has a blown screen and my multi card reader is out with one of the techs. I’ll give it a shot when the reader’s back.

The card appears to work fine in my phone though. I initialised it and it’s happy.

12

There are times in life when policies must me worked-around in my opinion.

Anyway,

Web Proxy Cache is still very very very usable and quality of the end user experience is much higher due to Web Proxy Cache!

Can’t you see “Hits sent to clients” how big that number gets on some proxies? It means it is working well :wink:

13

I have one ROS machine on my network that’s based on Intel hardware (P4 1GB RAM) with a 250GB SATA proxy with 6 radios (that go on to other APs) and that also provides IP to about 40 networks via UTP / fibre. It’s connected to the outside world via 4 x 2Mb leased lines to our traffic provider - so it’s a big machine.

Anyway, it runs web proxy and obviously there’s a lot of traffic going through the proxy. There were 194 “hits sent to clients” on the proxy since the router was last rebooted some time in February 2009.

Web proxy is also processor intensive. We’ll probably disable them throughout the organisation in the next month or so.

14

Something is wrong. Hits sent to clients should be A LOT. Like 2 gigabytes of data for example. And in my experience, what I saw, is tha MT 3.20+ Web Proxy uses very little resources.

15

I managed to get the microSD card into it’s adapter and into my SD card reader.

It’s FUBAR and is going back to the suppliers on Tuesday.

It appears that these solid state drives only have a finite life. Each sector can only be written and overwritten a certain number of times before it’s useless. That is why the space on memory sticks decreases. So I’m thinking maybe one of the critical sectors on the card was written to one time too many by RouterOS, so that’s the end of the card.

Either way, I’ve been doing a bit of further research on web proxy cache at the various places where we break out to the internet. Some places have very high hit ratios, some have very low hit ratios. I’m putting it down to demographics. Older people have different browsing patters to young people. Oldies get more cache hits while the facebook generation get less cache hits.

Yes, I know it doesn’t make sense, but this is what I see when I log into routers and compare them with each other.

16

Sure. Just run the cache near the border gw so it catches http requests by all users. So if one users visits site and causes a bunch of objects get cached, the next user visiting that site could get them from cache. I would even go so far as to request my upstream ISP to run a high performance big drive cache proxy.

17

I have six border gateways in two different countries.

18

The Web Proxy Cache must be in a place where the end user has high speed to it and at the same time - the more users go through a cache proxy - the better. So 6 proxies in your case maybe ?

19

We are actually running more than 6 proxies, but as I said previously it’s something we are looking at scaling down on.

For example, if we have an access point using a P4 with 1GB of RAM, ROS Level 5 and 4 x 90 degree 2.4GHz sectoral, 4 x 90 degree 5GHz sectoral and 5GHz NStream (this is a typical medium site with 10 radios) back to one of the our gateways, we’ll have at least 60GB of SATA proxy. We’ve only ever once used solid state memory and that was with the RB433AH on a microsite and that failed.

We have a very large MikroTik network.

20

I have same problem with my RB450G and two microSD cards (one SDHC 4gb, and another SD 2gb)
http://forum.mikrotik.com/t/rb450g-microsd-errors-help/27993/1
nobody answers me!