Hi Jess,
'redis-server' command is a blocked command, you should use 'redis-server &' to
run it backgroud.
Or you can use ssh tools to login into the node and start it manually.
Thanks,
Jinhua
原始邮件
发件人： <onap-helpd...@rt.linuxfoundation.org>
收件人：应允龙10191177
抄送人：傅锦华10108953 <onap-discuss@lists.onap.org>张茂鹏10030173
日 期 ：2017年08月23日 14:05
主 题 ：[ONAP Helpdesk #44472] [ONAP Helpdesk][help]About redis node for python
project
Thanks Yunlong,
here is my latest job:
https://jenkins.onap.org/job/vfc-gvnfm-vnflcm-master-lcm-verify-python/27/console
I have actually added a "redis-server" command to ensure the service is running
and I get the following information:
06:01:03 2016:C 23 Aug 06:01:03.687 # oO0OoO0OoO0Oo Redis is starting
oO0OoO0OoO0Oo
06:01:03 2016:C 23 Aug 06:01:03.687 # Redis version=4.0.1, bits=64,
commit=00000000, modified=0, pid=2016, just started
06:01:03 2016:C 23 Aug 06:01:03.687 # Warning: no config file specified, using
the default config. In order to specify a config file use redis-server
/path/to/redis.conf
06:01:03 2016:M 23 Aug 06:01:03.691 * Running mode=standalone, port=6379.
06:01:03 2016:M 23 Aug 06:01:03.691 # WARNING: The TCP backlog setting of 511
cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower
value of 128.
06:01:03 2016:M 23 Aug 06:01:03.692 # Server initialized
06:01:03 2016:M 23 Aug 06:01:03.692 # WARNING overcommit_memory is set to 0!
Background save may fail under low memory condition. To fix this issue add
'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the
command 'sysctl vm.overcommit_memory=1' for this to take effect.
06:01:03 2016:M 23 Aug 06:01:03.692 # WARNING you have Transparent Huge Pages
(THP) support enabled in your kernel. This will create latency and memory usage
issues with Redis. To fix this issue run the command 'echo never >
/sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your
/etc/rc.local in order to retain the setting after a reboot. Redis must be
restarted after THP is disabled.
06:01:03 2016:M 23 Aug 06:01:03.692 * Ready to accept connections
The job seems to get stuck there.
I am concerned about the warnings marked in the log. Do you know if maybe extra
configuration is missing?
thanks!
Jess
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
