Forums

Resolved
0 votes
Hello all,
I've search for a solution for the problem described here above. According to a post on the nexcloud website, installing a memcache server solves the problem
So, I decided to install redis as described on their website.
No problem for the installation, starting it.
According to the following information :

If you want to connect to Redis configured to listen on an Unix socket (which is recommended if Redis is running on the same system as Nextcloud) use this example config.php configuration:


I added the following to my /etc/nextcloud/config.php file :

'memcache.local' => '\OC\Memcache\Redis',
'redis' => [
'host' => '/var/run/redis/redis.sock',
'port' => 0,
'dbindex' => 0,
'password' => 'secret',
'timeout' => 1.5,
],


But, because of the line "'memcache.local' => '\OC\Memcache\Redis'" I can't launch the gui console anymore... so I removed it.

Does anyone know what should I write instead of '\OC\Memcache\Redis', ?

Per advance, thanks to all for your help :)
Thursday, November 07 2019, 09:43 PM
Share this post:
Responses (5)
  • Accepted Answer

    Friday, November 08 2019, 03:15 PM - #Permalink
    Resolved
    0 votes
    Have you seen Docs » Nextcloud configuration » Memory caching. I assume it is the same for 17. Did you start the redis server?
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 08 2019, 05:05 PM - #Permalink
    Resolved
    0 votes
    Hello Nick,
    thanks for the answer :) Yes this is the doc I used to install it on my COS System.

    Here's the error of the system :
    Error core OC\HintException: Memcache \OC\Memcache\Redis not available for local cache

    and is linked to tje memcache option... of course..
    "'memcache.local' => '\OC\Memcache\Redis'"

    It seems that the deamon is running :

    [root@srv-cos ~]# ps ax | grep redis
    2573 ? Ssl 2:02 /usr/bin/redis-server 127.0.0.1:6379
    27955 pts/0 S+ 0:00 grep --color=auto redis


    but not sure that memcache deamon is running (I removed the faulty line) :

    [root@srv-cos ~]# ps ax | grep memcached
    28016 pts/0 S+ 0:00 grep --color=auto memcached


    But if I add the faulty line, the result is exactly the same ...

    Thanks for your help :)
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 08 2019, 05:17 PM - #Permalink
    Resolved
    0 votes
    Their doc has a different config:
    'memcache.local' => '\OC\Memcache\APCu',
    'memcache.distributed' => '\OC\Memcache\Redis',
    'redis' => [
    'host' => '/var/run/redis/redis.sock',
    'port' => 0,
    'dbindex' => 0,
    'password' => 'secret',
    'timeout' => 1.5,
    ],
    And that is for using a socket. Have you checked the socket permission. Alternatively I guess you can use the port but you would have to specify it. 6379 in your config.

    Note I have no experience of this. I am only reading the doc.
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 08 2019, 05:50 PM - #Permalink
    Resolved
    0 votes
    Yes you're right, but with the configuration of the doc I get the same result ... :(

    I think the problem is as you said : the socket permission.

    But I'm really lost here.. doesnt know howto check that ... I'll have to make some research about that ;)
    Thanks for your help :)

    I think I found it in etc/redis.conf but no change ...

    #  unixsocket /tmp/redis.sock

    # My Modification
    unixsocket /var/run/redis/redis.sock
    unixsocketperm 700
    The reply is currently minimized Show
  • Accepted Answer

    Friday, November 08 2019, 06:17 PM - #Permalink
    Resolved
    0 votes
    The socket looks just like a file. You can do "ls -l /var/run/redis/redis.sock". The doc says you may have to add a user to a group, but note the user names and group names could be different in ClearOS than in the doc.
    The reply is currently minimized Show
Your Reply