Oscar Carlsson wrote on 07/01/08 23:32:
> ...you were very correct - I didn't have CacheMiddleware loaded, and when I
> loaded it...
> Everything worked.
>
> Thanks for all your help! :-)
>
> Oscar
> (I feel a bit stupid, tho)
Hacking for to long without a break, ey?
Guess we've all been
...you were very correct - I didn't have CacheMiddleware loaded, and when I
loaded it...
Everything worked.
Thanks for all your help! :-)
Oscar
(I feel a bit stupid, tho)
On Tue, Jul 1, 2008 at 11:10 PM, Steven Armstrong <[EMAIL PROTECTED]> wrote:
>
> Oscar Carlsson wrote on 07/01/08 19:02:
>
Oscar Carlsson wrote on 07/01/08 19:02:
> Heh, ops!
>
> That was a typo, but even after fixing it, nothing changed :(
> (still no change in memory usage, that is)
>
Looking at your dpaste entry again it seems you haven't configured the
cache middleware.
> Here is the ZeroDivisionError, btw:
I can connect to the daemon, and it's memory usage went up a bit (from 0.2%
to 0.4%)
>>> print mc.get('foo')
bar
But after restarting apache and loading the page in a browser, memcache
doesn't get any bigger. And if I restart the memcache daemon and then
restart apache again, memcache stays on
Oscar Carlsson wrote on 07/01/08 21:48:
> I've checked the following logs, but nothing turned up:
> /var/log/nginx*
> /var/log/httpd* (apache)
>
> Previously, when something went wrong with the app, all error messages
> appeared in /var/log/httpd-error.log, but this time - nothing.
>
> This is
I've checked the following logs, but nothing turned up:
/var/log/nginx*
/var/log/httpd* (apache)
Previously, when something went wrong with the app, all error messages
appeared in /var/log/httpd-error.log, but this time - nothing.
This is all the output I get when I restart apache (apachectl
Oscar Carlsson wrote on 07/01/08 19:02:
> Heh, ops!
>
> That was a typo, but even after fixing it, nothing changed :(
> (still no change in memory usage, that is)
>
> Here is the ZeroDivisionError, btw:
> http://dpaste.com/60185/
>
> Oscar
>
The python-memcached client fails silently if it
Heh, ops!
That was a typo, but even after fixing it, nothing changed :(
(still no change in memory usage, that is)
Here is the ZeroDivisionError, btw:
http://dpaste.com/60185/
Oscar
On Tue, Jul 1, 2008 at 6:47 PM, Brian Luft <[EMAIL PROTECTED]> wrote:
>
> In your settings file you have
In your settings file you have indicated that memcached is running on
port 112211 but your process listing shows it running on 11211.
-Brian
On Jul 1, 9:34 am, "Oscar Carlsson" <[EMAIL PROTECTED]> wrote:
> Hi!
>
> For some reason, django doesn't seem to add anything to my memcache - the
>
Hi,
just a quick note... the port (112211) wrong only on your email, or in
the settings file too?
> CACHE_BACKEND = 'memcached://127.0.0.1:112211/'
Paolo
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
Hi!
For some reason, django doesn't seem to add anything to my memcache - the
process is using 0.2% RAM (seems to be the absolute minimum on my system,
FreeBSD 7 with 512 MByte RAM) and never starts using more memory.
Why is this? I have no idea where to begin debug this, nothing ever shows up
11 matches
Mail list logo
