I just installed redis 4.0.10-lp150.3.3.1 from openSUSE Leap 15.0 repository but I can't figure out how to start/use it. I installed it to use with a system called emoncms but that says: "redis enabled but not installed" I tried redis-cli: $ redis-cli Could not connect to Redis at 127.0.0.1:6379: Connection refused Could not connect to Redis at 127.0.0.1:6379: Connection refused not connected> same if I try as root. $ systemctl status redis Unit redis.service could not be found. $ man redis gives me the documentation for the perl binding that I also installed. So how do I get it working? Anybody know? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, 3 March 2019 17:51:03 EET Dave Howorth wrote:
I just installed redis 4.0.10-lp150.3.3.1 from openSUSE Leap 15.0 repository but I can't figure out how to start/use it.
So how do I get it working? Anybody know?
Have a look in /usr/share/doc/packages/redis/README.SUSE. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 03 Mar 2019 19:22:41 +0200 auxsvr <auxsvr@gmail.com> wrote:
On Sunday, 3 March 2019 17:51:03 EET Dave Howorth wrote:
I just installed redis 4.0.10-lp150.3.3.1 from openSUSE Leap 15.0 repository but I can't figure out how to start/use it.
So how do I get it working? Anybody know?
Have a look in /usr/share/doc/packages/redis/README.SUSE.
Thanks for the pointer. I don't understand why it says (step 2) to change these settings. What's wrong with them as is? I followed the rest of the instructions but using 'default' instead of 'otherapp' and I found some steps were already done. I don't know (also step 2, stupid step numbering) whether I want to use redis in combination with apache. emoncms does use apache and it does use redis, so does that mean I am 'using redis in combination with apache' or not? Oh, and lots of the steps in the readme are shown with a $ prompt but need to be run as root. So when I got to the end of the readme: # systemctl status redis Unit redis.service could not be found. # 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 Sun 2019-03-03 20:35:12 GMT; 5min ago Main PID: 30742 (code=exited, status=1/FAILURE) Mar 03 20:35:12 acer-suse systemd[1]: redis@default.service: Unit entered failed state. Mar 03 20:35:12 acer-suse systemd[1]: redis@default.service: Failed with result 'exit-code'. Mar 03 20:35:12 acer-suse systemd[1]: redis@default.service: Service RestartSec=100ms expired, scheduling restart. Mar 03 20:35:12 acer-suse systemd[1]: Stopped Redis. Mar 03 20:35:12 acer-suse systemd[1]: redis@default.service: Start request repeated too quickly. Mar 03 20:35:12 acer-suse systemd[1]: Failed to start Redis. Mar 03 20:35:12 acer-suse systemd[1]: redis@default.service: Unit entered failed state. Mar 03 20:35:12 acer-suse systemd[1]: redis@default.service: Failed with result 'exit-code'. So I still haven't got it to run. I don't understand why I don't use YaST to install it and then it's running? And if I need to tweak it then fine but at least it works out of the box. That's what happens on the competition (ubuntu or Rpi) AIUI. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
So when I got to the end of the readme:
# systemctl status redis Unit redis.service could not be found.
Right, it is actually redis@, i.e. with an instance identifier.
# 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 Sun 2019-03-03 20:35:12 [snip] state. Mar 03 20:35:12 acer-suse systemd[1]: redis@default.service: Failed with result 'exit-code'.
So I still haven't got it to run.
There will be some diagnostics somewhere, in the log maybe? If you can't find any, try starting redis from the command line. Look at 'systemctl cat redis@default' to see what you need to do.
I don't understand why I don't use YaST to install it and then it's running?
My guess - something missing in the config. It's just some application, YaST probably doesn't know much about it. -- Per Jessen, Zürich (12.7°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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! -- Per Jessen, Zürich (14.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 04 Mar 2019 08:42:57 +0100 Per Jessen <per@computer.org> 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@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
On Mon, 04 Mar 2019 08:42:57 +0100 Per Jessen <per@computer.org> 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?
I see redis running: # systemctl status redis@default ● redis@default.service - Redis Loaded: loaded (/usr/lib/systemd/system/redis@.service; disabled; vendor preset: disabled) Active: active (running) since Mon 2019-03-04 08:39:12 CET; 4h 2min ago Main PID: 28708 (redis-server) Tasks: 4 (limit: 4915) CGroup: /system.slice/system-redis.slice/redis@default.service └─28708 /usr/sbin/redis-server 127.0.0.1:6379 Mar 04 08:39:12 test99 systemd[1]: Started Redis.
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.
I don't think so, no. -- Per Jessen, Zürich (8.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 04 Mar 2019 13:15:25 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
On Mon, 04 Mar 2019 08:42:57 +0100 Per Jessen <per@computer.org> 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?
I see redis running:
Leap 15.0, right? What's the difference then. I shall have to investigate.
# systemctl status redis@default ● redis@default.service - Redis Loaded: loaded (/usr/lib/systemd/system/redis@.service; disabled; vendor preset: disabled) Active: active (running) since Mon 2019-03-04 08:39:12 CET; 4h 2min ago Main PID: 28708 (redis-server) Tasks: 4 (limit: 4915) CGroup: /system.slice/system-redis.slice/redis@default.service └─28708 /usr/sbin/redis-server 127.0.0.1:6379
Mar 04 08:39:12 test99 systemd[1]: Started Redis.
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.
I don't think so, no.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
I see redis running:
Leap 15.0, right? What's the difference then. I shall have to investigate.
Yep, Leap15. -- Per Jessen, Zürich (12.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 04 Mar 2019 16:00:35 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
I see redis running:
Leap 15.0, right? What's the difference then. I shall have to investigate.
Yep, Leap15.
Found the problem(s): -1- I did a cp rather than a mv to make default.conf (as directed by README.SUSE), so the ownership was wrong -2- I started it manually as root, so the ownership of the log file was wrong Duh! :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Quoting Dave Howorth <dave@howorth.org.uk>:
I just installed redis 4.0.10-lp150.3.3.1 from openSUSE Leap 15.0 repository but I can't figure out how to start/use it.
I installed it to use with a system called emoncms but that says: "redis enabled but not installed"
I tried redis-cli:
$ redis-cli Could not connect to Redis at 127.0.0.1:6379: Connection refused Could not connect to Redis at 127.0.0.1:6379: Connection refused not connected>
same if I try as root.
$ systemctl status redis Unit redis.service could not be found.
I found something similar on 42.3. I can start redis manually with the example configuration modified for the app I'm using it with. # redis-server /etc/redis/amethyst.conf Starting it with systemctl fails with messages similar to what you see on 15.0. I have not successfully debugged why. It's for a local application, I can restart it manually. HTH, Jeffrey -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 3 Mar 2019 17:29:09 -0600 "Jeffrey L. Taylor" <jeff.taylor@ieee.org> wrote:
Quoting Dave Howorth <dave@howorth.org.uk>:
I just installed redis 4.0.10-lp150.3.3.1 from openSUSE Leap 15.0 repository but I can't figure out how to start/use it.
I installed it to use with a system called emoncms but that says: "redis enabled but not installed"
I tried redis-cli:
$ redis-cli Could not connect to Redis at 127.0.0.1:6379: Connection refused Could not connect to Redis at 127.0.0.1:6379: Connection refused not connected>
same if I try as root.
$ systemctl status redis Unit redis.service could not be found.
I found something similar on 42.3. I can start redis manually with the example configuration modified for the app I'm using it with.
# redis-server /etc/redis/amethyst.conf
Ah ha. # redis-server default.conf runs and afterwards $ redis-cli 127.0.0.1:6379> so I guess it is running. emoncms is still giving me the same error though, so I'm not out of the woods yet. Thanks anyway. Some progress at least.
Starting it with systemctl fails with messages similar to what you see on 15.0. I have not successfully debugged why. It's for a local application, I can restart it manually.
HTH, Jeffrey
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 4 Mar 2019 11:41:30 +0000 Dave Howorth <dave@howorth.org.uk> wrote:
On Sun, 3 Mar 2019 17:29:09 -0600 "Jeffrey L. Taylor" <jeff.taylor@ieee.org> wrote:
Quoting Dave Howorth <dave@howorth.org.uk>:
I just installed redis 4.0.10-lp150.3.3.1 from openSUSE Leap 15.0 repository but I can't figure out how to start/use it.
I installed it to use with a system called emoncms but that says: "redis enabled but not installed"
I tried redis-cli:
$ redis-cli Could not connect to Redis at 127.0.0.1:6379: Connection refused Could not connect to Redis at 127.0.0.1:6379: Connection refused not connected>
same if I try as root.
$ systemctl status redis Unit redis.service could not be found.
I found something similar on 42.3. I can start redis manually with the example configuration modified for the app I'm using it with.
# redis-server /etc/redis/amethyst.conf
Ah ha. # redis-server default.conf runs and afterwards
$ redis-cli 127.0.0.1:6379>
so I guess it is running. emoncms is still giving me the same error though, so I'm not out of the woods yet.
Thanks anyway. Some progress at least.
Starting it with systemctl fails with messages similar to what you see on 15.0. I have not successfully debugged why. It's for a local application, I can restart it manually.
HTH, Jeffrey
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier. Now emoncms is still claiming it isn't running, even though I've separately run the PHP code it uses to check and that works fine. Every other test indicates that both redis and the Phpredis extension are working fine. The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default. So I'd like to see if I can start redis with that service name as an experiment, but I can't see how to do that. Does anybody know? How does the systemd service mechanism work with regards to getting the name of a service? TIA, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/03/2019 18.53, Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
redis@default? Not redis.default? I believe the former have no service file to modify directly, they are automatically created somehow. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
On 06/03/2019 18.53, Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
redis@default? Not redis.default?
'default' is the instance name. -- Per Jessen, Zürich (10.2°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
Now emoncms is still claiming it isn't running, even though I've separately run the PHP code it uses to check and that works fine. Every other test indicates that both redis and the Phpredis extension are working fine.
The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default.
Those are just names, emoncms is likely looking for a port or a unix service. There must some config for emoncms too? -- Per Jessen, Zürich (9.9°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 06 Mar 2019 19:07:14 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
Now emoncms is still claiming it isn't running, even though I've separately run the PHP code it uses to check and that works fine. Every other test indicates that both redis and the Phpredis extension are working fine.
The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default.
Those are just names, emoncms is likely looking for a port or a unix service. There must some config for emoncms too?
Thanks Per. emoncms is expecting it on the standard port - 127.0.0.1:6379 - which it is on. What's a unix service? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 6 Mar 2019 19:49:03 +0000 Dave Howorth <dave@howorth.org.uk> wrote:
On Wed, 06 Mar 2019 19:07:14 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
Now emoncms is still claiming it isn't running, even though I've separately run the PHP code it uses to check and that works fine. Every other test indicates that both redis and the Phpredis extension are working fine.
The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default.
Those are just names, emoncms is likely looking for a port or a unix service. There must some config for emoncms too?
Thanks Per. emoncms is expecting it on the standard port - 127.0.0.1:6379 - which it is on. What's a unix service?
To add, the point is that on raspbian (and presumably ubuntu and debian also) the service is called 'redis-server' rather than 'redis@default' so the various scripts that try to access redis-server status and suchlike will fail on openSUSE. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
On Wed, 6 Mar 2019 19:49:03 +0000 Dave Howorth <dave@howorth.org.uk> wrote:
On Wed, 06 Mar 2019 19:07:14 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
Now emoncms is still claiming it isn't running, even though I've separately run the PHP code it uses to check and that works fine. Every other test indicates that both redis and the Phpredis extension are working fine.
The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default.
Those are just names, emoncms is likely looking for a port or a unix service. There must some config for emoncms too?
Thanks Per. emoncms is expecting it on the standard port - 127.0.0.1:6379 - which it is on. What's a unix service?
To add, the point is that on raspbian (and presumably ubuntu and debian also) the service is called 'redis-server' rather than 'redis@default' so the various scripts that try to access redis-server status and suchlike will fail on openSUSE.
The idea is that tou can have multiple redis instances, just as you can with mysql, postfix, vpn and many other services. Scripts that rely on a hardcoded name of a systemd service and fail - it's their problem. -- Per Jessen, Zürich (15.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 06 Mar 2019 23:28:59 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
On Wed, 6 Mar 2019 19:49:03 +0000 Dave Howorth <dave@howorth.org.uk> wrote:
On Wed, 06 Mar 2019 19:07:14 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
Now emoncms is still claiming it isn't running, even though I've separately run the PHP code it uses to check and that works fine. Every other test indicates that both redis and the Phpredis extension are working fine.
The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default.
Those are just names, emoncms is likely looking for a port or a unix service. There must some config for emoncms too?
Thanks Per. emoncms is expecting it on the standard port - 127.0.0.1:6379 - which it is on. What's a unix service?
To add, the point is that on raspbian (and presumably ubuntu and debian also) the service is called 'redis-server' rather than 'redis@default' so the various scripts that try to access redis-server status and suchlike will fail on openSUSE.
The idea is that tou can have multiple redis instances, just as you can with mysql, postfix, vpn and many other services. Scripts that rely on a hardcoded name of a systemd service and fail - it's their problem.
Well right, and I've made that point to them but in the meantime I've got the problem of getting the existing software to run. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
On Wed, 06 Mar 2019 19:07:14 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
Now emoncms is still claiming it isn't running, even though I've separately run the PHP code it uses to check and that works fine. Every other test indicates that both redis and the Phpredis extension are working fine.
The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default.
Those are just names, emoncms is likely looking for a port or a unix service. There must some config for emoncms too?
Thanks Per. emoncms is expecting it on the standard port - 127.0.0.1:6379 - which it is on. What's a unix service?
Apologies, s/service/socket/. A daemon can also communicate via a unix socket. What exactly does emoncms complain about? and how? -- Per Jessen, Zürich (14.3°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 06 Mar 2019 23:26:20 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
On Wed, 06 Mar 2019 19:07:14 +0100 Per Jessen <per@computer.org> wrote:
Dave Howorth wrote:
So a little more information. I've now got it running under systemd as I mentioned above but apparently it's running as a service called redis@default as mentioned by Per earlier.
Now emoncms is still claiming it isn't running, even though I've separately run the PHP code it uses to check and that works fine. Every other test indicates that both redis and the Phpredis extension are working fine.
The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default.
Those are just names, emoncms is likely looking for a port or a unix service. There must some config for emoncms too?
Thanks Per. emoncms is expecting it on the standard port - 127.0.0.1:6379 - which it is on. What's a unix service?
Apologies, s/service/socket/. A daemon can also communicate via a unix socket.
What exactly does emoncms complain about? and how?
We just fixed it. I needed to restart apache to get phpredis loaded into it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2019-03-06 12:53 p.m., Dave Howorth wrote:
The only thing I can see that is different is that emoncms expects the redis service to be called redis-server, not redis@default. So I'd like to see if I can start redis with that service name as an experiment, but I can't see how to do that. Does anybody know? How does the systemd service mechanism work with regards to getting the name of a service?
I seem to recall that the @-notation has to do with instantiation of a series of things where multiple copies of the same service can be run. systemctl shows Getty on tty1, tt2 etc getty@tty1.service getty@tty2.service and similarly for disks systemd-fsck@dev-disk-by\x2dlabel-BOOT.service systemd-fsck@dev-disk-by\x2dlabel-TMP.service systemd-fsck@dev-vgmain-vHome.service user@0.service user@501.service I'm sure you can do the equivalent of systemctl start whatever@foo.service systemctl start whatever@bar.service See SYSTEMD.UNIT(5) under "String Escaping for Inclusion in Unit Names" https://www.freedesktop.org/software/systemd/man/systemd.unit.html which leads to https://www.freedesktop.org/software/systemd/man/systemd-escape.html# -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Anton Aylward -
auxsvr -
Carlos E. R. -
Dave Howorth -
Jeffrey L. Taylor -
Per Jessen