sous-chefs / memcached Goto Github PK
View Code? Open in Web Editor NEWDevelopment repository for the memcached cookbook
Home Page: https://supermarket.chef.io/cookbooks/memcached
License: Apache License 2.0
Development repository for the memcached cookbook
Home Page: https://supermarket.chef.io/cookbooks/memcached
License: Apache License 2.0
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
Chef have released updated cookstyle rules, we should therefore run the auto fix against the cookbook
chef-workstation
cookstyle -a
Issue sprouted from sous-chefs/meta/issues/111. If not applicable then issue should be closed.
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
If the only thing in the .rubocop/yml
is Dangerfile
Run the latest cookstyle
Remove .rubpopo.yml
Issue sprouted from sous-chefs/meta/issues/108. If not applicable then issue should be closed.
As far as I can see there's no need for it at all. This alone is a reason to remove its installation from the recipe. The other reason is that it's not yet in Debian testing: https://tracker.debian.org/pkg/libmemcache
v3.0.1
v12.12.15
Ubuntu 14.04 LTS (Trusty Tahr)
I'm trying to use a custom log file by utilizing the logfilepath
and logfilename
node options.
Set the following options for the default recipe:
memcached: {
logfilepath: "/var/log/memcached",
logfilename: "memcached.log"
}
The log file is used.
The log file is not used. The issue is because the log settings are never actually used anywhere in this cookbook, likely a regression that wasn't caught. This can be fixed by modifying the cli options to the following after updating the individual resource properties:
def cli_options
options = "-m #{new_resource.memory} \
-U #{new_resource.udp_port} \
-p #{new_resource.port} \
-u #{new_resource.user} \
-l #{new_resource.listen} \
-c #{new_resource.maxconn} \
-I #{new_resource.max_object_size}"
if new_resource.experimental_options.any?
options << " -o #{new_resource.experimental_options.join(', ')}"
end
options << " -t #{new_resource.threads}" if new_resource.threads
if new_resource.logfilepath && new_resource.logfilename
options << " -vv >> #{new_resource.logfilepath.chomp('/')}/#{new_resource.logfilename} 2>&1"
end
options
end
I can create a pull request if you'd like.
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
On the repo, ensure that Dangerfile
matches https://github.com/sous-chefs/repo-management/blob/master/Dangerfile
Issue sprouted from sous-chefs/meta/issues/110. If not applicable then issue should be closed.
master
15.3.14
Ubuntu 18.04
When having both memcached and rabbitmq official cookbooks in your runlist they both try to edit the policy-d.rc file
Have memcached and rabbitmq official cookbooks in your run list, depending on the order they write a different policy-d.rc file
This cookbook should not touch policy-d.rc file
I expect that a cookbook only deals with its own resources and files. It should not start editing system files just to achieve some desired behaviour, if multiple cookbooks does this you end up with files changing on every run
Issue on rabbitmq cookbook: rabbitmq/chef-cookbook#536
The library helper functions are global and conflict with other cookbooks such as apache2.
Some helper functions such as lock_dir
conflict with the apache2 cookbook which can cause problems when both cookbooks are included in a run list. The primary issue is that the helper functions are not properly namespaced like the apache2 cookbook is.
The resolution is to properly namespace the helper functions so they don't get pulled in globally.
6.0.0
15
Ubuntu/Debian/CentOS
The cookbook does not actually start memcached unless a configuration change has occurred. I suggest changing action :enable to action [ :start, :enable ]
Shouldn't that be collapsed into debian
? 12.04 returns a family of debian
when I run ohai. Not sure if that's different for other versions of ohai
or the OS.
The current init script only works on RHEL. We need a universal script that supports both LSB implementations.
The previous cookbook defaulted to runit. We're still shipping it, but you'll need to specify it. We need to document that.
Release 3.0.2
chef-12.11.18-1.el6.x86_64.rpm
CentOS release 6.7 (Final)
run the recipe memcached::default
$ kitchen converge default-centos-67
memcached launches without errors
[vagrant@default-centos-67 ~]$ sudo /sbin/service memcached start
Starting memcached: chown: missing operand after `/var/run/memcached'
Try `chown --help' for more information.
the issue seems to be that the variable user in template is not defined?
the init.d script as a result has this invalid line:
chown /var/run/memcached
which is based on this line from template:
chown <%= @user %> /var/run/memcached
On Ubuntu 14.04 with memcached cookbook v1.7.2. I'm using the cookbook like this:
memcached_instance 'my_memcached'
.. with these attributes:
default['memcached']['memory'] = 64
default['memcached']['logfilename'] = 'memcached.log'
default['memcached']['port'] = 11211
default['memcached']['user'] = 'memcache'
After converge, I end up with two lots of memcached running. It's like the default Ubuntu installer is also starting up it's own init script?
$ ps aux | grep memcached
memcache 1619 0.0 0.0 325396 1184 ? Sl 23:01 0:00 /usr/bin/memcached -m 64 -p 11211 -u memcache -l 127.0.0.1
root 1707 0.0 0.0 168 4 ? Ss 23:02 0:00 runsv memcached-my_memcached
memcache 1718 0.0 0.0 54820 1024 ? Sl 23:02 0:00 /usr/bin/memcached -v -m 64 -U -p 11211 -u memcache -l 0.0.0.0 -c 1024
root 1745 0.0 0.0 184 4 ? S 23:02 0:00 svlogd -tt /var/log/memcached-my_memcached
There is a need to set up several Memcached instances using unix sockets.
Currently the cookbook supports such a deployment scenario only through setting extra_cli_options ("-a" and "-s" parameters).
It could be useful to support socket configuration resource properties.
Recipe Compile Error in /var/folders/7z/20ps8xf523v4n_1_03w4znyr0000gn/T/d20160118-8752-n1lw2d/cookbooks/memcached/resources/instance.rb
================================================================================
NoMethodError
-------------
undefined method `action' for #<Class:0x007fcd0aeaa5b8> action provider
Cookbook Trace:
---------------
/var/folders/7z/20ps8xf523v4n_1_03w4znyr0000gn/T/d20160118-8752-n1lw2d/cookbooks/memcached/resources/instance.rb:33:in `class_from_file'
Relevant File Content:
----------------------
/var/folders/7z/20ps8xf523v4n_1_03w4znyr0000gn/T/d20160118-8752-n1lw2d/cookbooks/memcached/resources/instance.rb:
26: property :user, String, default: nil
27: property :threads, [Integer, String], default: nil
28: property :max_object_size, String, default: '1m'
29: property :experimental_options, Array, default: []
30: property :ulimit, [Integer, String], default: nil
31: property :template_cookbook, String, default: 'memcached'
32:
33>> action :create do
34: include_recipe 'runit'
35: include_recipe 'memcached::package'
36:
37: runit_service instance_name do
38: run_template_name 'memcached'
39: default_logger true
40: cookbook template_cookbook
41: options(
42: memory: memory,
F
1.0.1
ubuntu 16
Linux vm-tst-ngapp4 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
vagrant chef-zero
installation
...
---- Begin output of /usr/bin/sv restart /etc/service/memcached-memcached ----
==> nextgen: STDOUT: timeout: down: /etc/service/memcached-memcached: 1s, normally up, want up
$ ls /etc/service/memcached-memcached
control env log memcache, memcached, nobody} run supervise
$ cat run
#!/bin/sh
exec 2>&1
exec chpst -u {["suse", "fedora", "rhel"]=>"memcached", "debian"=>"memcache", "default"=>"nobody"} /usr/bin/memcached -v -m 64 -U 11211 -p 11211 -u {["suse", "fedora", "rhel"]=>"memcached", "debian"=>"memcache", "default"=>"nobody"} -l 0.0.0.0 -c 1024
include memcached recipe
the service_user should return accordingly dependant on platform
runit script contains hash value, not result of value_for_platform_family
Not everyone wants to run runit. We should use the native init systems instead.
With the latest version of the cookbook (2.0.2) the service restarts on every chef run. It looks like this was introduced in version 2.0 but was not listed as a breaking change.
How I use it
total_memory = node['memory']['total']
memory = total_memory.split('kB')[0].to_i / 1024
if memory > 20_480
max_memory = 3072
else
max_memory = 256
end
node.force_default['memcached']['memory'] = max_memory
node.force_default['memcached']['port'] = 11_211
node.force_default['memcached']['udp_port'] = 11_211
node.force_default['memcached']['listen'] = '0.0.0.0'
node.force_default['memcached']['maxconn'] = 1024
include_recipe 'memcached'
memcached_instance 'memcached'
Log output showing stop/start
Recipe: memcached::package
* file[/usr/sbin/policy-rc.d with exit 101] action create (skipped due to not_if)
* apt_package[memcached] action install (up to date)
* file[/usr/sbin/policy-rc.d with exit 0] action create (up to date)
* group[memcache] action create (skipped due to not_if)
* user[memcache] action nothing (skipped due to action :nothing)
* service[memcached] action stop
- stop service service[memcached]
* service[memcached] action disable
- disable service service[memcached]
Recipe: memcached::configure
* directory[/var/log/] action create (up to date)
* template[/etc/memcached.conf] action create (up to date)
* service[memcached] action enable
- enable service service[memcached]
* service[memcached] action start
- start service service[memcached]```
The readme talks about memcached['logfilename'] but I do not see that variable used in memcached.conf.erb
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
As part of our build process we should build each possible operating system separately
dokken list
, you should see a list of builds with dokken as the providerdokken list -j | ./circleci_maker.rb > .circleci/config.yml
Issue sprouted from sous-chefs/meta/issues/112. If not applicable then issue should be closed.
Running client 11.14.6 and get this error with 1.8.0. chef-docker had similar issue and was fixed with
include Chef::Mixin::ShellOut
sous-chefs/docker#353
version 1.7.2 is successful
Output:
[2015-09-03T21:57:11+00:00] WARN: Current service[collectd]: /var/chef/cache/cookbooks/collectd/recipes/default.rb:138:in `from_file'
NoMethodError
No resource or method named shell_out' for
Chef::Recipe "package"'
Cookbook Trace:
/var/chef/cache/cookbooks/memcached/recipes/package.rb:23:in `from_file'
/var/chef/cache/cookbooks/memcached/recipes/default.rb:20:in `from_file'
Relevant File Content:
/var/chef/cache/cookbooks/memcached/recipes/package.rb:
16: # See the License for the specific language governing permissions and
17: # limitations under the License.
18: #
19:
20: # include epel on redhat/centos 5 and below in order to get the memcached packages
21: include_recipe 'yum-epel' if node['platform_family'] == 'rhel' && node['platform_version'].to_i == 5
22:
23>> if node['platform_family'] == 'debian' && shell_out('dpkg -l memcached | grep "^ii memcached"').error?
24: # dpkg, imma let you finish but don't start services automatically
25: # https://jpetazzo.github.io/2013/10/06/policy-rc-d-do-not-start-services-automatically/
26: execute 'disable auto-start' do
27: command 'echo exit 101 > /usr/sbin/policy-rc.d ; chmod +x /usr/sbin/policy-rc.d'
28: end
29:
30: package 'memcached' do
31: version node['memcached']['version']
32: action :install
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
This repository currently has no open or pending branches.
.github/workflows/ci.yml
sous-chefs/.github 3.1.1
actions/checkout v4
actionshub/chef-install 3.0.0
actionshub/test-kitchen 3.0.0
.github/workflows/stale.yml
actions/stale v9
Support for max_object_size variable in the Debian/Ubuntu startup script.
last one
12.18.31
centos/7
I'm trying to set two memcached instances.
I'm using berkshelf with this memcached.rb
file content:
include_recipe 'memcached'
memcached_instance 'mc1' do
memory 64
port 11211
udp_port 11211
action [:start, :enable]
end
memcached_instance 'mc2' do
memory 64
port 11212
udp_port 11212
action [:start, :enable]
end
Both instances are running on ghest.
Both seem to be installed as services:
Nevertheless, only one of them are running:
[vagrant@localhost ~]$ systemctl status memcached_mc1
โ memcached_mc1.service - memcached instance memcached_mc1
Loaded: loaded (/etc/systemd/system/memcached_mc1.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2017-02-22 11:55:18 UTC; 11min ago
Main PID: 13072 (memcached)
CGroup: /system.slice/memcached_mc1.service
โโ13072 /usr/bin/memcached -m 64 -U 11211 -p 11211 -u memcached -l 0.0.0.0 -c 1024 -I 1
[vagrant@localhost ~]$ systemctl status memcached_mc2
โ memcached_mc2.service - memcached instance memcached_mc2
Loaded: loaded (/etc/systemd/system/memcached_mc2.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Wed 2017-02-22 11:55:20 UTC; 11min ago
Process: 13359 ExecStart=/usr/bin/memcached -m 64 -U 11212 -p 11212 -u memcached -l 0.0.0.0 -c 1024 -I 1m (code=exited, status=71)
Main PID: 13359 (code=exited, status=71)
Where are log files located?
Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.
Update all CHANGELOGs to follow standard defined at https://keepachangelog.com/
Issue sprouted from sous-chefs/meta/issues/101. If not applicable then issue should be closed.
Hi,
when uploading memcached 1.9.0 with berkshelf to my chef-server, it get this error:
E, [2015-11-09T11:41:25.999906 #39632] ERROR -- : Ridley::Errors::HTTPBadRequest: {"error":["Invalid element in array value of 'templates'."]}
1.8.0 works without issues.
Including the default recipe yields a busted install on my Rhel 6.7 box:
================================================================================
Error executing action `restart` on resource 'service[memcached]'
================================================================================
Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of /sbin/service memcached restart ----
STDOUT: Stopping memcached: [FAILED]
Starting memcached: [FAILED]
STDERR: chown: invalid user: `memcached'
---- End output of /sbin/service memcached restart ----
Ran /sbin/service memcached restart returned 1
Resource Declaration:
---------------------
# In /tmp/kitchen/cache/cookbooks/memcached/recipes/configure.rb
22: service 'memcached' do
23: action :enable
24: supports :status => true, :start => true, :stop => true, :restart => true, :enable => true
25: end
26:
Compiled Resource:
------------------
# Declared in /tmp/kitchen/cache/cookbooks/memcached/recipes/configure.rb:22:in `from_file'
service("memcached") do
action [:enable]
updated true
supports {:status=>true, :start=>true, :stop=>true, :restart=>true, :enable=>true}
retries 0
retry_delay 2
guard_interpreter :default
service_name "memcached"
enabled true
pattern "memcached"
cookbook_name "memcached"
recipe_name "configure"
end
Running handlers:
[2015-11-02T12:38:22-08:00] ERROR: Running exception handlers
Running handlers complete
[2015-11-02T12:38:22-08:00] ERROR: Exception handlers complete
[2015-11-02T12:38:22-08:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
Attempting to start the service manually:
# service memcached start
Starting memcached: chown: invalid user: `memcached'
memcached
Looking for the user:
[root@host ~]# grep -i memcached /etc/passwd
[root@host ~]#
The installed version:
[root@host~]# rpm -qa | grep -i memcached
memcached-1.4.15-1.el6.x86_64
If the user is not created by design, that should be documented in the README,
I suspect its a reasonable assumption that the cookbook would create the user
Latest package from repoforge (1.4.14-1.el6.rfx) does not create a memcached user and therefore memcached will not start with default attributes.
Using CentOS 6.5 and Chef 11.12.8.
It's time to remove Runit support and instead rely on native init systems. This is something we're doing across all of our cookbooks to remove our dependency on the runit cookbook and to give users the native experience they expect.
version 5.0.1
version 12.18.31
CentOS Linux release 7.3.1611 (Core)
default['memcached']['version'] = '1.4.25-1.el7'
Upgrade of the cookbook fails when an instance of memcached is already running. It fails on 'user' resource.
Ran ["usermod", "-c", "Memcached", "-s", "/bin/false", "-d", "/nonexistent", "memcached"] returned 8
I expect the user is updated with no restart of memcached (or at least it should be configurable). Maybe we can ignore if some changes are not applied (we don't care of the home directory).
In our case, 'memcache' user and group already exist. They were created by the RPM package. Old version of the recipe (before b2e98e6) do not create/update the user because the group already exist. Recent versions try to update the user (in particular its home dir), but usermod cannot update the home directory when the user is logged (or it is executing memcached).
I don't think we should re-configure user or group in our case. But probably other packages do differently... I think we should provide more control on _package recipe. This could solve this issue and allows to customize the installation(for example let us install from a custom tarball).
Included memcached recipe in project recipe, used berks to gather dependencies.
NameError
---------
No resource, method, or local variable named `service_group' for `Chef::Recipe "package"'
Cookbook Trace:
---------------
/tmp/vagrant-chef/5c78b9cb779c90c4a149b7577fc0e343/cookbooks/memcached/recipes/package.rb:50:in `from_file'
/tmp/vagrant-chef/5c78b9cb779c90c4a149b7577fc0e343/cookbooks/memcached/recipes/default.rb:20:in `from_file'
/tmp/vagrant-chef/5c78b9cb779c90c4a149b7577fc0e343/cookbooks/project/recipes/default.rb:24:in `from_file'
Relevant File Content:
----------------------
/tmp/vagrant-chef/5c78b9cb779c90c4a149b7577fc0e343/cookbooks/memcached/recipes/package.rb:
43: else
44: package 'memcached' do
45: version node['memcached']['version']
46: action :install
47: end
48: end
49:
50>> group service_group do
51: system true
52: notifies :create, "user[#{service_user}]", :immediately
53: notifies :lock, "user[#{service_user}]", :immediately
54: not_if "getent passwd #{service_user}"
55: end
56:
57: user service_user do
58: system true
59: manage_home false
Contents of Chef stacktrace:
Generated at 2016-01-28 23:03:58 +0000
NameError: No resource, method, or local variable named `service_group' for `Chef::Recipe "package"'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/dsl/recipe.rb:104:in `rescue in method_missing'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/dsl/recipe.rb:99:in `method_missing'
/tmp/vagrant-chef/5c78b9cb779c90c4a149b7577fc0e343/cookbooks/memcached/recipes/package.rb:50:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/mixin/from_file.rb:30:in `instance_eval'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/mixin/from_file.rb:30:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/cookbook_version.rb:229:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:333:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:288:in `block in include_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:287:in `each'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:287:in `include_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/dsl/include_recipe.rb:26:in `include_recipe'
/tmp/vagrant-chef/5c78b9cb779c90c4a149b7577fc0e343/cookbooks/memcached/recipes/default.rb:20:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/mixin/from_file.rb:30:in `instance_eval'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/mixin/from_file.rb:30:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/cookbook_version.rb:229:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:333:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:288:in `block in include_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:287:in `each'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:287:in `include_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/dsl/include_recipe.rb:26:in `include_recipe'
/tmp/vagrant-chef/5c78b9cb779c90c4a149b7577fc0e343/cookbooks/project/recipes/default.rb:24:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/mixin/from_file.rb:30:in `instance_eval'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/mixin/from_file.rb:30:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/cookbook_version.rb:229:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:333:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context/cookbook_compiler.rb:140:in `block in compile_recipes'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context/cookbook_compiler.rb:138:in `each'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context/cookbook_compiler.rb:138:in `compile_recipes'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context/cookbook_compiler.rb:75:in `compile'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/run_context.rb:167:in `load'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/policy_builder/expand_node_object.rb:93:in `setup_run_context'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/client.rb:490:in `setup_run_context'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/client.rb:268:in `run'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application.rb:261:in `block in fork_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application.rb:249:in `fork'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application.rb:249:in `fork_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application.rb:215:in `block in run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/local_mode.rb:44:in `with_server_connectivity'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application.rb:203:in `run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application/solo.rb:286:in `block in interval_run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application/solo.rb:275:in `loop'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application/solo.rb:275:in `interval_run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application/solo.rb:253:in `run_application'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/lib/chef/application.rb:58:in `run'
/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.6.0/bin/chef-solo:25:in `<top (required)>'
/bin/chef-solo:54:in `load'
/bin/chef-solo:54:in `<main>'
This was tested inside a CentOS7 vagrant, Ubuntu 14.04 host.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.