*** FATAL CONFIG FILE ERROR ***

[singhaniashrinkhala]

After adding the path to the LibRadarData.rdb as suggested in the documentation, I get this error when I ran the command below:

redis-server tool/redis.conf &

ERROR:

FATAL CONFIG FILE ERROR Reading the configuration file, at line 80

'protected-mode yes' Bad directive or wrong number of arguments

Path added is :

dir /home/fringi/Desktop/RA/redis-3.2.7

[pkumza]

How about showing me lines 60-100 of your config file?As I know it is a Redis configuration issue.

I could not reappear this error in my environment. Last time I met probably the same bug because I use an old version of Redis. I use default 'apt-get install' and get a pretty old version. I suggest the version redis>=3.2.0. Do not use 3.0.x or older versions.

If there's no many security problems, you could just remove the line 80 and see what happened next.

[singhaniashrinkhala]

### 

# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bind 127.0.0.1

# Protected mode is a layer of security protection, in order to avoid that
# Redis instances left open on the internet are accessed and exploited.
#
# When protected mode is on and if:
#
# 1) The server is not binding explicitly to a set of addresses using the
#    "bind" directive.
# 2) No password is configured.
#
# The server only accepts connections from clients connecting from the
# IPv4 and IPv6 loopback addresses 127.0.0.1 and ::1, and from Unix domain
# sockets.
#
# By default protected mode is enabled. You should disable it only if
# you are sure you want clients from other hosts to connect to Redis
# even if no authentication is configured, nor a specific set of interfaces
# are explicitly listed using the "bind" directive.
protected-mode yes

# Accept connections on the specified port, default is 6379 (IANA #815344).
# If port 0 is specified Redis will not listen on a TCP socket.
port 6379

# TCP listen() backlog.
#
# In high requests-per-second environments you need an high backlog in order
# to avoid slow clients connections issues. Note that the Linux kernel
# will silently truncate it to the value of /proc/sys/net/core/somaxconn so
# make sure to raise both the value of somaxconn and tcp_max_syn_backlog
# in order to get the desired effect.
tcp-backlog 511

# Unix socket.
#
# Specify the path for the Unix socket that will be used to listen for
# incoming connections. There is no default, so Redis will not listen
# on a unix socket when not specified.
#
# unixsocket /tmp/redis.sock
# unixsocketperm 700

# Close the connection after a client is idle for N seconds (0 to disable)

[singhaniashrinkhala]

Also, I downloaded version 3.2.7

[pkumza]

Oh, it seems quite the same. I've tried a new test on a new Macbook but it works well. It works well also on my Ubuntu system. Redis version 3.2.5 3.2.7 3.2.8 are all tested.

I'm so sorry I have no idea what happend to your Redis configuration. Maybe you could refer to some Redis professional?

And... have you tried remove line 80?

[pkumza]

Seems that you have already solved this problem too.