Yes. But if everyone has these same reasons, we can’t do anything
I agree, it would be frustrating for you.
If MT wanted I could enable and create the output file every hour, perhaps this would give clues.
normis: I’ve also sent through a number of supout.rif’s and also participated and provided information to a number of other users who were also affected.
See - http://forum.mikrotik.com/viewtopic.php?f=2&t=22713&st=0&sk=t&sd=a&hilit=hotspot&start=50
How to replicate the problem yourself: Turn on transparent proxy and get 100 or more users to start using. Thats probably the easiest way to force it to crash. Alternatively you can put 500 users on a proxy without the transparent proxy turned on, then wait for 2-6 weeks for it to randomly crash (murphy’s law means it’s normally around 12 at night 
).
i can vouch for the problem describe by “omega-00”. very frustrating problem, given the fact that downgrading/upgrading and reverting back “Sometimes” “Fix” the problem, for a while, untill it occurs again…
feature suggestion that was available on previous versions, and removed on 3.x
Max object size:
Other suggestions: Use memory to stores metadata from the objects on cache, to speedup the access on disk.
Squid box for 150gb cache, is recommended at least 2g ram.
On my MT cache box, I´m almost 200gb full cache, but the memory used on router is very low.
I can imagine that seeking hard disk (sata) in this case takes a lot more of just querying the metadata and previously know where the object is.
best regards,
vince de luca
I have to say: When just used as a caching proxy server for a small number of users the proxy does work fine for me.
I currently have a 4gb proxy running of a usb drive on my mikrotik, currently using v3.16 with no problems, however if I try the same thing with any of my hotspot sites with lots of users (200+) and the transparent proxy turned on I see issues normally within 24 hours.
With the transparent proxy turned off I have systems running for up to 2 months maximum without seeing any issues.
On sites just using other router functionality I have uptimes of 4 months and more on v3.X with no issues
Since it is/was real Squid, why not to support proxy-mesh and so many other features that squid does ?
Why configuration options are so poor ?
At last give the opportunity to upload squid.conf inside mikrotik
Thats because RouterOS is RouterOS, not ProxyOS or SquidOS!
I agree but, using that logic, it shouldn’t have proxy at all.
My notice has to do with poor options in general. Do you want another example ?
→ Why TCP/UDP option is missing from OpenVPN ? It is just a line in the configuration file…
specifically for this case, did you send a supout.rif file to support? in any case, please make a new ticket and send some files. we will see what we can do
Hello Normis,
Just sent through another supout.rif regarding the proxy issue (which is now affecting v3.18)
Ticket number is 2009011466000074
Regards
Omega-00
Has this problem been resolved yet or are you still experiencing these problems with v3.20?
When you guys have problems with the proxy, is it enough to disable/enable the cache to have it start working again or is a complete reboot neccesary?
I’m just wondering because I’m just about to put an RB1000 in production in a rather big corporate network to be the default gw and also use it as a forwarding proxy and I really really don’t wanna have to reboot this device just because the proxy has a problem. Then I should get them 2 boxes right now and run the proxy forwarder in a seperate now that can be rebooted without affecting the normal routing out of the network.
Have yet to see any instances of that bug in 3.20 which I’m currently running at a site with 1300~ users spread over 2 devices.
Looks like its all good for that version.