----- Original Message -----
From: “Denis Kot” denis.kot@gmail.com
To: “Foreman users” foreman-users@googlegroups.com
Sent: Monday, April 18, 2016 12:26:35 PM
Subject: [foreman-users] Re: No repors from salt minions
I don’t know if it’s related, but at same time I see this error in apache
error log:
App 23129 stdout:
App 22637 stderr: E, [2016-04-18T16:17:22.389408 #22685] ERROR –
/connector-database-core: No executor available (Dynflow::Error)
This probably means the foreman-tasks service isn’t started
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/dynflow-0.8.10/lib/dynflow/connectors/database.rb:142:in
`any_executor’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/dynflow-0.8.10/lib/dynflow/connectors/database.rb:134:in
`find_receiver’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/dynflow-0.8.10/lib/dynflow/connectors/database.rb:86:in
`handle_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/dynflow-0.8.10/lib/dynflow/actor.rb:6:in
`on_message’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/context.rb:46:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/executes_context.rb:7:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/dynflow-0.8.10/lib/dynflow/actor.rb:26:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/awaits.rb:15:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/sets_results.rb:14:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:38:in
`process_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:31:in
`process_envelopes?'
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:20:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/termination.rb:55:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/removes_child.rb:10:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
`pass’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/sets_results.rb:14:in
`on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:161:in
`process_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:95:in
`block in on_envelope’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:118:in
`block (2 levels) in schedule_execution’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
`block in synchronize’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
`synchronize’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
`synchronize’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:115:in
`block in schedule_execution’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/serialized_execution.rb:18:in
`call’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/serialized_execution.rb:18:in
`call’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/serialized_execution.rb:96:in
`work’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/serialized_execution.rb:77:in
`block in call_job’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:348:in
`call’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:348:in
`run_task’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:337:in
`block (3 levels) in create_worker’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:320:in
`loop’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:320:in
`block (2 levels) in create_worker’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:319:in
`catch’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/concurrent-ruby-1.0.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:319:in
`block in create_worker’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/logging-2.1.0/lib/logging/diagnostic_context.rb:450:in
`call’
App 22637 stderr:
/usr/share/foreman/vendor/ruby/2.0.0/gems/logging-2.1.0/lib/logging/diagnostic_context.rb:450:in
`block in create_with_logging_context’
понедельник, 18 апреля 2016 г., 16:52:27 UTC+2 пользователь Denis Kot > > > написал:
In foreman’s production.log I have:
2016-04-18T14:40:07 [app] [I] Started POST "/salt/api/v2/jobs/upload"
for
10.165.30.248 at 2016-04-18 14:40:07 +0000
2016-04-18T14:40:07 [app] [I] Processing by
ForemanSalt::Api::V2::JobsController#upload as JSON
2016-04-18T14:40:07 [app] [I] Parameters:
{“job”=>{“function”=>“state.highstate”, “result”=>{{"
srv-07.example.com
"=>…
…
2016-04-18T14:40:07 [app] [I] Processing job 20160418143315945873 from
Salt.
2016-04-18T14:40:07 [foreman-tasks/dynflow] [D] ExecutionPlan
b2be9e84-3c0c-40e6-859f-73554357605f pending >> planning
2016-04-18T14:40:07 [foreman-tasks/dynflow] [D] Step
b2be9e84-3c0c-40e6-859f-73554357605f: 1 pending >> running in phase
Plan Actions::ForemanSalt::ReportImport
2016-04-18T14:40:07 [foreman-tasks/dynflow] [D] Step
b2be9e84-3c0c-40e6-859f-73554357605f: 1 running >> success in phase
Plan Actions::ForemanSalt::ReportImport
2016-04-18T14:40:07 [foreman-tasks/dynflow] [D] ExecutionPlan
b2be9e84-3c0c-40e6-859f-73554357605f planning >> planned
2016-04-18T14:40:07 [app] [I] Completed 200 OK in 107ms (Views: 0.3ms |
ActiveRecord: 18.5ms)
But I don’t see this report associated to host srv-07.example.com in
Foreman. I have Foreman 1.11 and salt-plugin/proxy 5.0
–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/2EJoCWuXP04/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
