Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redis does not start on redis-package for debian-7.11 #336

Closed
shortdudey123 opened this issue Apr 27, 2017 · 1 comment
Closed

Redis does not start on redis-package for debian-7.11 #336

shortdudey123 opened this issue Apr 27, 2017 · 1 comment
Milestone

Comments

@shortdudey123
Copy link
Contributor

Recipe: redisio::configure
 * service[redis6379] action nothing[2017-04-27T23:40:45+00:00] INFO: Processing service[redis6379] action nothing (redisio::configure line 47)
(skipped due to action :nothing)
 * service[redis6379] action start[2017-04-27T23:40:45+00:00] INFO: Processing service[redis6379] action start (redisio::configure line 47)

   
   ================================================================================
   Error executing action `start` on resource 'service[redis6379]'
   ================================================================================
   
   Mixlib::ShellOut::ShellCommandFailed
   ------------------------------------
   Expected process to exit with [0], but received '1'
   ---- Begin output of /etc/init.d/redis6379 start ----
   STDOUT: Starting Redis server...
   STDERR: *** FATAL CONFIG FILE ERROR ***
   Reading the configuration file, at line 82
   >>> 'tcp-keepalive 0'
   Bad directive or wrong number of arguments
   ---- End output of /etc/init.d/redis6379 start ----
   Ran /etc/init.d/redis6379 start returned 1
   
   Resource Declaration:
   ---------------------
   # In /tmp/kitchen/cache/cookbooks/redisio/recipes/configure.rb
   
    47:     service "redis#{server_name}" do
    48:       # don't supply start/stop/restart commands, Chef::Provider::Service::*
    49:       # do a fine job on it's own, and support systemd correctly
    50:       supports start: true, stop: true, restart: false, status: true
    51:     end
    52:   when 'upstart'
    53:     service "redis#{server_name}" do
    54:       provider Chef::Provider::Service::Upstart
    55:       start_command "start redis#{server_name}"
    56:       stop_command "stop redis#{server_name}"
    57:       restart_command "restart redis#{server_name}"
    58:       supports start: true, stop: true, restart: true, status: false
    59:     end
    60:   when 'systemd'
    61:     service "redis@#{server_name}" do
    62:       provider Chef::Provider::Service::Systemd
    63:       supports start: true, stop: true, restart: true, status: true
    64:     end
    65:   when 'rcinit'
    66:     service "redis#{server_name}" do
    67:       provider Chef::Provider::Service::Freebsd
    68:       supports start: true, stop: true, restart: true, status: true
    69:     end
    70:   else
    71:     Chef::Log.error('Unknown job control type, no service resource created!')
    72:   end
    73: end
    74: 
   
   Compiled Resource:
   ------------------
   # Declared in /tmp/kitchen/cache/cookbooks/redisio/recipes/configure.rb:47:in `block in from_file'
   
   service("redis6379") do
     action [:nothing, :start, :enable]
     supports {:start=>true, :stop=>true, :restart=>false, :status=>true}
     retries 0
     retry_delay 2
     default_guard_interpreter :default
     service_name "redis6379"
     enabled nil
     running nil
     masked nil
     pattern "redis6379"
     declared_type :service
     cookbook_name "redisio"
     recipe_name "configure"
   end
   
   Platform:
   ---------
   x86_64-linux
@shortdudey123 shortdudey123 added this to the 2.6.0 milestone Apr 27, 2017
@shortdudey123 shortdudey123 modified the milestones: 2.next, 2.6.0 May 9, 2017
shortdudey123 added a commit that referenced this issue May 10, 2017
@shortdudey123 shortdudey123 modified the milestones: 2.next, 2.6.1 May 10, 2017
@lock
Copy link

lock bot commented Nov 28, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Nov 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant