Created
April 10, 2019 18:31
-
-
Save nmattam/8ec723bb637f98391a69ae6ea4caf274 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
==> f_default: * ruby_block[restart-splunk-for-ulimit] action run | |
==> f_default: [2019-04-10T18:22:04+00:00] INFO: ruby_block[restart-splunk-for-ulimit] called | |
==> f_default: | |
==> f_default: - execute the ruby block restart-splunk-for-ulimit | |
==> f_default: | |
==> f_default: [2019-04-10T18:22:04+00:00] INFO: ruby_block[restart-splunk-for-ulimit] sending touch action to file[splunk-marker] (immediate) | |
==> f_default: Recipe: cerner_splunk::_restart_marker | |
==> f_default: * file[splunk-marker] action touch | |
==> f_default: [2019-04-10T18:22:04+00:00] INFO: file[splunk-marker] updated atime and mtime to 2019-04-10 18:22:04 +0000 | |
==> f_default: | |
==> f_default: - update utime on file /var/chef/cache/.restart_splunk | |
==> f_default: | |
==> f_default: Recipe: cerner_splunk::_start | |
==> f_default: * ruby_block[start-splunk] action run | |
==> f_default: [2019-04-10T18:22:04+00:00] INFO: ruby_block[start-splunk] called | |
==> f_default: | |
==> f_default: | |
==> f_default: - execute the ruby block start-splunk | |
==> f_default: | |
==> f_default: [2019-04-10T18:22:04+00:00] INFO: ruby_block[start-splunk] sending start action to service[splunk] (immediate) | |
==> f_default: Recipe: cerner_splunk::_install | |
==> f_default: * service[splunk] action start | |
==> f_default: [2019-04-10T18:22:36+00:00] INFO: service[splunk] started | |
==> f_default: | |
==> f_default: - start service service[splunk] | |
==> f_default: | |
==> f_default: | |
==> f_default: [2019-04-10T18:22:38+00:00] INFO: service[splunk] sending delete action to file[splunk-marker] (immediate) | |
==> f_default: Recipe: cerner_splunk::_restart_marker | |
==> f_default: | |
==> f_default: * file[splunk-marker] action delete | |
==> f_default: bash: line 4: 6522 Killed chef-client --config /tmp/vagrant-chef/client.rb --json-attributes /tmp/vagrant-chef/dna.json --log_level info --force-formatter | |
Chef never successfully completed! Any errors should be visible in the | |
output above. Please fix your recipes so that they properly complete. |
Author
nmattam
commented
Apr 10, 2019
•
==> f_default: - restore selinux security context
==> f_default:
==> f_default:
==> f_default: * directory[/testlogs/one] action create
==> f_default: [2019-04-10T17:49:30+00:00] INFO: directory[/testlogs/one] created directory /testlogs/one
==> f_default:
==> f_default:
==> f_default: - create new directory /testlogs/one
==> f_default: [2019-04-10T17:49:30+00:00] INFO: directory[/testlogs/one] owner changed to 1000
==> f_default: [2019-04-10T17:49:30+00:00] INFO: directory[/testlogs/one] group changed to 1000
==> f_default: [2019-04-10T17:49:30+00:00] INFO: directory[/testlogs/one] mode changed to 750
==> f_default:
==> f_default:
==> f_default: - change mode from '' to '0750'
==> f_default: - change owner from '' to 'vagrant'
==> f_default:
==> f_default: - change group from '' to 'vagrant'
==> f_default:
==> f_default: - restore selinux security context
==> f_default:
==> f_default:
==> f_default: * template[/testlogs/one/access1.log] action create
==> f_default: [2019-04-10T17:49:30+00:00] INFO: template[/testlogs/one/access1.log] created file /testlogs/one/access1.log
==> f_default: - create new file /testlogs/one/access1.log
==> f_default: [2019-04-10T17:49:30+00:00] INFO: template[/testlogs/one/access1.log] updated file contents /testlogs/one/access1.log
==> f_default: bash: line 4: 6511 Killed chef-client --config /tmp/vagrant-chef/client.rb --json-attributes /tmp/vagrant-chef/dna.json --log_level info --force-formatter
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment