Friday, September 04
Sometime Simpler Is Better
Two virtual machines, each with 3 cores and 4GB RAM, running CentOS 7.
[Edit: Wait, Kururu is on CentOS 6. Well, near enough.]
Kururu is running under OpenVZ:
While Rere is running on KVM:
Also, Kururu didn't have 3 cores and 4GB of RAM. It had 1 core, and 1GB. I changed it to take this screenshot - but check the uptime.
Posted by: Pixy Misa at
08:52 PM
| Comments (6)
| Add Comment
| Trackbacks (Suck)
Post contains 56 words, total size 1 kb.
1
Pixy, just now I was trying to upload a bunch of images and got a lot of error 500's. And as I load your page, none of the images are loading.
Posted by: Steven Den Beste at Sunday, September 06 2015 02:02 PM (+rSRq)
2
I just got another one:
Traceback (most recent call last):
File "/usr/local/lib/python2.6/site-packages/cherrypy/_cprequest.py", line 606, in respond
cherrypy.response.body = self.handler()
File "/usr/local/lib/python2.6/site-packages/cherrypy/_cpdispatch.py", line 25, in __call__
return self.callable(*self.args, **self.kwargs)
File "Minx.py", line 170, in default
return go(cherrypy)
File "Minx.py", line 121, in go
raise
File "Minx.py", line 112, in go
return Page.go(cp)
File "/var/minx/live1.1/Page.py", line 408, in go
page.Tags()
File "/var/minx/live1.1/Page.py", line 233, in Tags
site_stats.hincrby(key, 'hits', 1)
File "/usr/local/lib/python2.6/site-packages/redis/client.py", line 1391, in hincrby
return self.execute_command('HINCRBY', name, key, amount)
File "/usr/local/lib/python2.6/site-packages/redis/client.py", line 394, in execute_command
return self.parse_response(connection, command_name, **options)
File "/usr/local/lib/python2.6/site-packages/redis/client.py", line 404, in parse_response
response = connection.read_response()
File "/usr/local/lib/python2.6/site-packages/redis/connection.py", line 316, in read_response
raise response
ResponseError: OOM command not allowed when used memory > 'maxmemory'.
Posted by: Steven Den Beste at Sunday, September 06 2015 02:03 PM (+rSRq)
3
Sorry about that, the cache server ran out of memory. Fixed now.
Posted by: Pixy Misa at Sunday, September 06 2015 03:53 PM (PiXy!)
4
Found the problem - I was using the cache server as a handy place to store real-time stats, but they didn't expire, so over several months the cache would slowly fill up with out-of-date data.
Fortunately, the cache we're using (Redis) has a setting that just says "throw out the oldest data no matter what", so with one quick change I've fixed the problem for good.
Redis is pretty neat.
Fortunately, the cache we're using (Redis) has a setting that just says "throw out the oldest data no matter what", so with one quick change I've fixed the problem for good.
Redis is pretty neat.
Posted by: Pixy Misa at Sunday, September 06 2015 03:57 PM (PiXy!)
5
I was using
Posted by: zabetheny at Saturday, September 19 2015 01:17 PM (UVB6W)
6
the problem for good
Posted by: Lbertine24 at Monday, September 21 2015 12:45 PM (JGoEa)
51kb generated in CPU 0.0201, elapsed 0.1259 seconds.
58 queries taking 0.1178 seconds, 351 records returned.
Powered by Minx 1.1.6c-pink.
58 queries taking 0.1178 seconds, 351 records returned.
Powered by Minx 1.1.6c-pink.