# Repeated server error 500 after 013.1 upgrade

**URL:** <https://community.learningequality.org/t/repeated-server-error-500-after-013-1-upgrade/1431>\
**Category:** Kolibri\
**Tags:** installation\
**Created:** [February 17, 2020, 10:22am UTC](https://community.learningequality.org/t/repeated-server-error-500-after-013-1-upgrade/1431 "2020-02-17T10:22:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cjackson](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.learningequality.org/cjackson/32/240_2.png) [@cjackson](https://community.learningequality.org/u/cjackson)\
**Post date:** [February 17, 2020, 10:22am UTC](https://community.learningequality.org/t/repeated-server-error-500-after-013-1-upgrade/1431/1 "2020-02-17T10:22:50Z")

</div>

Following a successful upgrade to v 0.13.1 yesterday, we now have consistent Server 500 errors. The record of the error that repeats with each server crash is below. It’s the same error that recurs each time. Is there a fix that I can implement? Kolibri cannot run for very long after each restart with this error.

ERROR 2020-02-17 09:08:49,530 exception Internal Server Error: /api/content/contentnode\_slim/  
Traceback (most recent call last):  
File “/usr/lib/python3/dist-packages/kolibri/dist/django/core/handlers/exception.py”, line 41, in inner  
response = get\_response(request)  
File “/usr/lib/python3/dist-packages/kolibri/dist/django/utils/deprecation.py”, line 142, in **call**  
response = self.process\_response(request, response)  
File “/usr/lib/python3/dist-packages/kolibri/dist/django/middleware/cache.py”, line 99, in process\_response  
cache\_key = learn\_cache\_key(request, response, timeout, self.key\_prefix, cache=self.cache)  
File “/usr/lib/python3/dist-packages/kolibri/dist/django/utils/cache.py”, line 402, in learn\_cache\_key  
cache.set(cache\_key, headerlist, cache\_timeout)  
File “/usr/lib/python3/dist-packages/kolibri/dist/redis\_cache/backends/base.py”, line 30, in wrapped  
return method(self, client, key, \*args, \*\*kwargs)  
File “/usr/lib/python3/dist-packages/kolibri/dist/redis\_cache/backends/base.py”, line 274, in set  
result = self.\_set(client, key, self.prep\_value(value), timeout, \_add\_only=False)  
File “/usr/lib/python3/dist-packages/kolibri/dist/redis\_cache/backends/base.py”, line 267, in \_set  
return client.set(key, value, nx=\_add\_only, ex=timeout)  
File “/usr/lib/python3/dist-packages/kolibri/dist/redis/client.py”, line 1451, in set  
return self.execute\_command(‘SET’, \*pieces)  
File “/usr/lib/python3/dist-packages/kolibri/dist/redis/client.py”, line 775, in execute\_command  
return self.parse\_response(connection, command\_name, \*\*options)  
File “/usr/lib/python3/dist-packages/kolibri/dist/redis/client.py”, line 789, in parse\_response  
response = connection.read\_response()  
File “/usr/lib/python3/dist-packages/kolibri/dist/redis/connection.py”, line 642, in read\_response  
raise response  
redis.exceptions.ResponseError: MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.  
INFO 2020-02-17 09:10:39,237 system Initiating shutdown of Kolibri

---

<div class="post-metadata">

**Author:** ![jredrejo](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.learningequality.org/jredrejo/32/561_2.png) [@jredrejo](https://community.learningequality.org/u/jredrejo)\
**Post date:** [February 17, 2020, 12:08pm UTC](https://community.learningequality.org/t/repeated-server-error-500-after-013-1-upgrade/1431/2 "2020-02-17T12:08:43Z")

</div>

> [@cjackson](#):
>
> redis.exceptions.ResponseError: MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk

Hello Chris, the error dump you pasted here indicates there’s an error in the service used for caching: `redis`. It’s not a kolibri error itself.  
It seems some of the redis files have now wrong permissions and can’t be written. The redis log can provide more information to know where the problem is exactly, please, can you attach it here? it’s the file` /var/log/redis/redis-server.log` in your server.

In the meantime, while this problem is solved, you can disable this kind of caching, in the file `options.ini` placed in your `.kolibri` folder you’ll have these two lines:

```auto
[Cache]
CACHE_BACKEND = redis

```

You can edit this file adding a `#` in front of the line with the `CACHE_BACKEND` text. This will tell kolibri not to use redis for caching. The application performance will be a bit worse but kolibri will work having this service down.