AFP548 Changing the world one server at a time.

Peformance Cache Questions

Home › Forums › OS X Server and Client Discussion › Web › Peformance Cache Questions

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • March 10, 2006 at 12:12 pm #365630
    davidelbert
    Participant

    Hi-
    I’ve been trying to understand and correct some problems I am having with caching and the use of port 16080 with my Tiger server implementation. With the performance cache turned on, web access is redirected from port 80 to port 16080. That’s a problem for me because of firewall settings beyond my control.

    My question really is: what is the performance cache? We turn it off and on with a checkbox in the site options pane, but what part of apache is this? is it the mod_proxy cache? What and where is the config file for it?

    And a big question: How do I clear this cache?

    Thanks for any help or insight anyone can offer.

    March 10, 2006 at 2:09 pm #365632
    davidelbert
    Participant

    Actually, just turning off the cache doesn’t solve the problem. The site still tries to redirect one of my wordpress blogs that it was moving to port 16080. It seems to have left some configuration behind that I have to clear. But if I don’t know where it is, I can’t clear it.

    March 10, 2006 at 6:43 pm #365642
    davidelbert
    Participant

    only one site, so that doesn’t seem to be the trick.

    there is a cache config file at: /private/etc/webperfcache/webperfcache.config that gets changed when I toggle the cache on/off in the Site Options. Basically, it just seems to add a line at the very end that says:

    WebPerfCacheListenAddress 0.0.0.0:80 16080 * “/var/log/httpd/access_log” fixed “%{PC-Remote-Adde}i %l %u %t \”%r\” %>s %b”

    I guess if no one knows of another config file, or the details of this one, I will have to take it apart and try to understand it… 163 lines 😢

    March 10, 2006 at 7:47 pm #365643
    davidelbert
    Participant

    Well, my immediate problem is solved. The error was some strange interaction with wordpress configuration settings. The settings files had picked up the :16080 port and saved it, so the server at large was working on port 80 once the performance cache was off, but the blogs were all redirectin themselves to a port that was not functional.

    I will never understand the crosstalk that made that happen, but now that it is ferreted out and fixed, things are working smoothly.

    I will continue to wonder a bit about the performance cache, but it won’t keep me up nights!

    Thanks for listening and offering advice. 😛

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.