Mailinglist Archive: opensuse (389 mails)

< Previous Next >
Re: [opensuse] redis
On Mon, 04 Mar 2019 08:42:57 +0100
Per Jessen <per@xxxxxxxxxxxx> wrote:

Per Jessen wrote:

My guess - something missing in the config. It's just some
application, YaST probably doesn't know much about it.

On my sandbox system:

zypper in redis syslog-ng-redis
cd /etc/redis
mv default.conf.example default.conf
systemctl start redis@default

Et voila!

On my system I can do that too. And my default.conf.example and
default.conf are identical. But then

# systemctl start redis@default
# systemctl status redis@default
● redis@default.service - Redis
Loaded: loaded (/usr/lib/systemd/system/redis@.service; enabled;
vendor preset: disabled)
Drop-In: /etc/systemd/system/redis@default.service.d └─limits.conf
Active: failed (Result: exit-code) since Mon 2019-03-04 11:30:36
GMT; 5s ago Process: 4970
ExecStart=/usr/sbin/redis-server /etc/redis/default.conf (code=exited,
status=1/FAILURE) Main PID: 4970 (code=exited, status=1/FAILURE)

Mar 04 11:30:35 acer-suse systemd[1]: redis@default.service: Unit
entered failed state. Mar 04 11:30:35 acer-suse systemd[1]:
redis@default.service: Failed with result 'exit-code'. Mar 04 11:30:36
acer-suse systemd[1]: redis@default.service: Service RestartSec=100ms
expired, scheduling restart. Mar 04 11:30:36 acer-suse systemd[1]:
Stopped Redis. Mar 04 11:30:36 acer-suse systemd[1]:
redis@default.service: Start request repeated too quickly. Mar 04
11:30:36 acer-suse systemd[1]: Failed to start Redis. Mar 04 11:30:36
acer-suse systemd[1]: redis@default.service: Unit entered failed state.
Mar 04 11:30:36 acer-suse systemd[1]: redis@default.service: Failed
with result 'exit-code'.

So what's the status on your system?

PS I don't have syslog-ng-redis since I don't want to log to redis but
I don't see why that should matter. If I try to install it I see a
conflict (with non-selectable text - thanks again YaST!)



--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups