> Already restart the whole machine…
>
> Processing by ForemanTasks::TasksController#resume as HTML
> Parameters:
> {"authenticity_token"=>"WvcrrzSEvvrLUwprH5SRWR9QHVyseR0prikr5lkQ6us=",
> "id"=>"e4f1a1ff-c9b3-4b43-a03d-9476b9a2d93c"}
Can you confirm that the foreman-tasks service is running?
-Justin
···
On 03/04/2015 09:48 AM, Peter Santiago wrote:
Connection refused - “/usr/share/foreman/tmp/sockets/dynflow_socket”
(Errno::ECONNREFUSED)
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in initialize' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:innew’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in connect' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:91:inblock in on_message’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in block in assigns' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:intap’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in assigns' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:inmatch_value’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in block in match' /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:ineach’
/opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in match' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:79:inon_message’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in block in on_envelope' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:incall’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in evaluate_to' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:inon_envelope’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:72:in receive' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:inblock (2 levels) in run’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in loop' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:inblock in run’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in catch' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:inrun’
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:13:in block in initialize' /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:incall’
/opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
`block in create_with_logging_context’
Operation FAILED: Cannot do
Dynflow::Executors::Abstract::Execution[execution_plan_id:
ecf62e11-29e0-4685-88f7-ad47bc813264, finished:
#Dynflow::Future:0x0000000e74f230], no connection to a Listener
Rendered common/500.html.erb within layouts/application (5.4ms)
Rendered layouts/base.html.erb (1.3ms)
Completed 500 Internal Server Error in 44ms (Views: 23.9ms |
ActiveRecord: 1.8ms)
[root@llin417 ~]# katello-service status
qpidd (pid 2414) is running…
tomcat6 (pid 2253) is running… [ OK ]
mongod (pid 2808) is running…
elasticsearch (pid 2156) is running…
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 3516) is running…
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 3580) is running…
node reserved_resource_worker-1 (pid 3596) is running…
celery init v10.0.
Using configuration: /etc/default/pulp_workers, /etc/default/pulp_celerybeat
pulp_celerybeat (pid 3419) is running.
httpd (pid 2361) is running…
dynflow_executor is running.
dynflow_executor_monitor is running.
[root@llin417 ~]# /etc/init.d/foreman-tasks status
dynflow_executor is running.
dynflow_executor_monitor is running.
···
On Wednesday, March 4, 2015 at 11:03:13 PM UTC+8, jsherril wrote:
>
> On 03/04/2015 09:48 AM, Peter Santiago wrote:
>
> Already restart the whole machine...
>
> Processing by ForemanTasks::TasksController#resume as HTML
> Parameters:
> {"authenticity_token"=>"WvcrrzSEvvrLUwprH5SRWR9QHVyseR0prikr5lkQ6us=",
> "id"=>"e4f1a1ff-c9b3-4b43-a03d-9476b9a2d93c"}
>
>
> Can you confirm that the foreman-tasks service is running?
>
> -Justin
>
> Connection refused - "/usr/share/foreman/tmp/sockets/dynflow_socket"
> (Errno::ECONNREFUSED)
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
> `initialize'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
> `new'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
> `connect'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:91:in
> `block in on_message'
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in
> `block in assigns'
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
> `tap'
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
> `assigns'
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:in
> `match_value'
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in
> `block in match'
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
> `each'
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
> `match'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:79:in
> `on_message'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in
> `block in on_envelope'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in
> `call'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in
> `evaluate_to'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in
> `on_envelope'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:72:in
> `receive'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> `block (2 levels) in run'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> `loop'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> `block in run'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> `catch'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> `run'
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:13:in
> `block in initialize'
> /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
> `call'
> /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
> `block in create_with_logging_context'
> Operation FAILED: Cannot do
> Dynflow::Executors::Abstract::Execution[execution_plan_id:
> ecf62e11-29e0-4685-88f7-ad47bc813264, finished:
> #], no connection to a Listener
> Rendered common/500.html.erb within layouts/application (5.4ms)
> Rendered layouts/base.html.erb (1.3ms)
> Completed 500 Internal Server Error in 44ms (Views: 23.9ms | ActiveRecord:
> 1.8ms)
>
> --
> 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-user...@googlegroups.com .
> To post to this group, send email to forema...@googlegroups.com
> .
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
Also, please check /usr/share/foreman/tmp/pids/dynflow_executor.output (we already have an bug filed to have this file under /var/log/foreman), for enything interesting.
– Ivan
···
----- Original Message -----
> [root@llin417 ~]# katello-service status
> qpidd (pid 2414) is running...
> tomcat6 (pid 2253) is running... [ OK ]
> mongod (pid 2808) is running...
> elasticsearch (pid 2156) is running...
> celery init v10.0.
> Using config script: /etc/default/pulp_resource_manager
> node resource_manager (pid 3516) is running...
> celery init v10.0.
> Using config script: /etc/default/pulp_workers
> node reserved_resource_worker-0 (pid 3580) is running...
> node reserved_resource_worker-1 (pid 3596) is running...
> celery init v10.0.
> Using configuration: /etc/default/pulp_workers, /etc/default/pulp_celerybeat
> pulp_celerybeat (pid 3419) is running.
> httpd (pid 2361) is running...
> dynflow_executor is running.
> dynflow_executor_monitor is running.
> [root@llin417 ~]# /etc/init.d/foreman-tasks status
> dynflow_executor is running.
> dynflow_executor_monitor is running.
>
>
> On Wednesday, March 4, 2015 at 11:03:13 PM UTC+8, jsherril wrote:
> >
> > On 03/04/2015 09:48 AM, Peter Santiago wrote:
> >
> > Already restart the whole machine...
> >
> > Processing by ForemanTasks::TasksController#resume as HTML
> > Parameters:
> > {"authenticity_token"=>"WvcrrzSEvvrLUwprH5SRWR9QHVyseR0prikr5lkQ6us=",
> > "id"=>"e4f1a1ff-c9b3-4b43-a03d-9476b9a2d93c"}
> >
> >
> > Can you confirm that the foreman-tasks service is running?
> >
> > -Justin
> >
> > Connection refused - "/usr/share/foreman/tmp/sockets/dynflow_socket"
> > (Errno::ECONNREFUSED)
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
> > `initialize'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
> > `new'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
> > `connect'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:91:in
> > `block in on_message'
> > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in
> > `block in assigns'
> > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
> > `tap'
> > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
> > `assigns'
> > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:in
> > `match_value'
> > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in
> > `block in match'
> > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
> > `each'
> > /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
> > `match'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:79:in
> > `on_message'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in
> > `block in on_envelope'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in
> > `call'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in
> > `evaluate_to'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in
> > `on_envelope'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:72:in
> > `receive'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> > `block (2 levels) in run'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> > `loop'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> > `block in run'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> > `catch'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
> > `run'
> > /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:13:in
> > `block in initialize'
> > /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
> > `call'
> > /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
> > `block in create_with_logging_context'
> > Operation FAILED: Cannot do
> > Dynflow::Executors::Abstract::Execution[execution_plan_id:
> > ecf62e11-29e0-4685-88f7-ad47bc813264, finished:
> > #], no connection to a Listener
> > Rendered common/500.html.erb within layouts/application (5.4ms)
> > Rendered layouts/base.html.erb (1.3ms)
> > Completed 500 Internal Server Error in 44ms (Views: 23.9ms | ActiveRecord:
> > 1.8ms)
> >
> > --
> > 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-user...@googlegroups.com .
> > To post to this group, send email to forema...@googlegroups.com
> > .
> > Visit this group at http://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 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 http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
Starting listener
Everything ready
terminate called after throwing an instance of 'qpid::types::Exception'
what(): Failed to initialise SSL: Failed: NSS error [-8015]
(/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/sys/ssl/util.cpp:100)
(/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/client/SslConnector.cpp:149)
Starting Rails environment
/usr/share/foreman/app/models/concerns/encryptable.rb:10: warning: already
initialized constant ENCRYPTION_PREFIX
Starting listener
Everything ready
Lockfile /usr/share/foreman/tmp/dynflow_executor.lock is already present.
terminate called after throwing an instance of 'qpid::types::Exception'
what(): Failed to initialise SSL: Failed: NSS error [-8015]
(/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/sys/ssl/util.cpp:100)
(/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/client/SslConnector.cpp:149)
Starting Rails environment
/usr/share/foreman/app/models/concerns/encryptable.rb:10: warning: already
initialized constant ENCRYPTION_PREFIX
[root@llin417 ~]# hammer -u admin ping
[Foreman] password for admin:
candlepin:
Status: ok
Server Response: Duration: 275ms
candlepin_auth:
Status: ok
Server Response: Duration: 20ms
pulp:
Status: ok
Server Response: Duration: 53ms
pulp_auth:
Status: ok
Server Response: Duration: 49ms
elasticsearch:
Status: ok
Server Response: Duration: 37ms
foreman_tasks:
Status: FAIL
Server Response: Message: foreman-tasks service not running
···
On Wednesday, March 4, 2015 at 11:46:23 PM UTC+8, Ivan Necas wrote:
>
> Hi,
>
> What about `hammer ping`?
>
> Also, please check /usr/share/foreman/tmp/pids/dynflow_executor.output (we
> already have an bug filed to have this file under /var/log/foreman), for
> enything interesting.
>
> -- Ivan
>
> ----- Original Message -----
> > [root@llin417 ~]# katello-service status
> > qpidd (pid 2414) is running...
> > tomcat6 (pid 2253) is running... [ OK ]
> > mongod (pid 2808) is running...
> > elasticsearch (pid 2156) is running...
> > celery init v10.0.
> > Using config script: /etc/default/pulp_resource_manager
> > node resource_manager (pid 3516) is running...
> > celery init v10.0.
> > Using config script: /etc/default/pulp_workers
> > node reserved_resource_worker-0 (pid 3580) is running...
> > node reserved_resource_worker-1 (pid 3596) is running...
> > celery init v10.0.
> > Using configuration: /etc/default/pulp_workers,
> /etc/default/pulp_celerybeat
> > pulp_celerybeat (pid 3419) is running.
> > httpd (pid 2361) is running...
> > dynflow_executor is running.
> > dynflow_executor_monitor is running.
> > [root@llin417 ~]# /etc/init.d/foreman-tasks status
> > dynflow_executor is running.
> > dynflow_executor_monitor is running.
> >
> >
> > On Wednesday, March 4, 2015 at 11:03:13 PM UTC+8, jsherril wrote:
> > >
> > > On 03/04/2015 09:48 AM, Peter Santiago wrote:
> > >
> > > Already restart the whole machine...
> > >
> > > Processing by ForemanTasks::TasksController#resume as HTML
> > > Parameters:
> > > {"authenticity_token"=>"WvcrrzSEvvrLUwprH5SRWR9QHVyseR0prikr5lkQ6us=",
> > > "id"=>"e4f1a1ff-c9b3-4b43-a03d-9476b9a2d93c"}
> > >
> > >
> > > Can you confirm that the foreman-tasks service is running?
> > >
> > > -Justin
> > >
> > > Connection refused - "/usr/share/foreman/tmp/sockets/dynflow_socket"
> > > (Errno::ECONNREFUSED)
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
>
> > > `initialize'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
>
> > > `new'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
>
> > > `connect'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:91:in
>
> > > `block in on_message'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in
>
> > > `block in assigns'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
>
> > > `tap'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
>
> > > `assigns'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:in
>
> > > `match_value'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in
>
> > > `block in match'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
>
> > > `each'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
>
> > > `match'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:79:in
>
> > > `on_message'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in
>
> > > `block in on_envelope'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in
>
> > > `call'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in
>
> > > `evaluate_to'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in
>
> > > `on_envelope'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:72:in
>
> > > `receive'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>
> > > `block (2 levels) in run'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>
> > > `loop'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>
> > > `block in run'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>
> > > `catch'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>
> > > `run'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:13:in
>
> > > `block in initialize'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
>
> > > `call'
> > >
> /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
>
> > > `block in create_with_logging_context'
> > > Operation FAILED: Cannot do
> > > Dynflow::Executors::Abstract::Execution[execution_plan_id:
> > > ecf62e11-29e0-4685-88f7-ad47bc813264, finished:
> > > #], no connection to a Listener
> > > Rendered common/500.html.erb within layouts/application (5.4ms)
> > > Rendered layouts/base.html.erb (1.3ms)
> > > Completed 500 Internal Server Error in 44ms (Views: 23.9ms |
> ActiveRecord:
> > > 1.8ms)
> > >
> > > --
> > > 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-user...@googlegroups.com .
> > > To post to this group, send email to forema...@googlegroups.com
> > > .
> > > Visit this group at http://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 the Google
> Groups
> > "Foreman users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to foreman-user...@googlegroups.com .
> > To post to this group, send email to forema...@googlegroups.com
> .
> > Visit this group at http://groups.google.com/group/foreman-users.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
> Starting listener
> Everything ready
> terminate called after throwing an instance of 'qpid::types::Exception'
> what(): Failed to initialise SSL: Failed: NSS error [-8015]
> (/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/sys/ssl/util.cpp:100)
> (/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/client/SslConnector.cpp:149)
> Starting Rails environment
> /usr/share/foreman/app/models/concerns/encryptable.rb:10: warning: already
> initialized constant ENCRYPTION_PREFIX
> Starting listener
> Everything ready
> Lockfile /usr/share/foreman/tmp/dynflow_executor.lock is already present.
> terminate called after throwing an instance of 'qpid::types::Exception'
> what(): Failed to initialise SSL: Failed: NSS error [-8015]
> (/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/sys/ssl/util.cpp:100)
> (/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/client/SslConnector.cpp:149)
> Starting Rails environment
> /usr/share/foreman/app/models/concerns/encryptable.rb:10: warning: already
> initialized constant ENCRYPTION_PREFIX
And we have the winner ^^^^^. Seems like an issue connecting to the qpid.
Somebody with gutterball experience //cc dustin, might know more on that.
The service foreman-tasks status is not that valuable here, as it tries
to keep the service up: it if fails, it starts it again. There is room
for improving that.
– Ivan
···
----- Original Message -----
[root@llin417 ~]# hammer -u admin ping
[Foreman] password for admin:
candlepin:
Status: ok
Server Response: Duration: 275ms
candlepin_auth:
Status: ok
Server Response: Duration: 20ms
pulp:
Status: ok
Server Response: Duration: 53ms
pulp_auth:
Status: ok
Server Response: Duration: 49ms
elasticsearch:
Status: ok
Server Response: Duration: 37ms
foreman_tasks:
Status: FAIL
Server Response: Message: foreman-tasks service not running
On Wednesday, March 4, 2015 at 11:46:23 PM UTC+8, Ivan Necas wrote:
Hi,
What about hammer ping?
Also, please check /usr/share/foreman/tmp/pids/dynflow_executor.output (we
already have an bug filed to have this file under /var/log/foreman), for
enything interesting.
– Ivan
----- Original Message -----
[root@llin417 ~]# katello-service status
qpidd (pid 2414) is running…
tomcat6 (pid 2253) is running… [ OK ]
mongod (pid 2808) is running…
elasticsearch (pid 2156) is running…
celery init v10.0.
Using config script: /etc/default/pulp_resource_manager
node resource_manager (pid 3516) is running…
celery init v10.0.
Using config script: /etc/default/pulp_workers
node reserved_resource_worker-0 (pid 3580) is running…
node reserved_resource_worker-1 (pid 3596) is running…
celery init v10.0.
Using configuration: /etc/default/pulp_workers,
/etc/default/pulp_celerybeat
pulp_celerybeat (pid 3419) is running.
httpd (pid 2361) is running…
dynflow_executor is running.
dynflow_executor_monitor is running.
[root@llin417 ~]# /etc/init.d/foreman-tasks status
dynflow_executor is running.
dynflow_executor_monitor is running.
On Wednesday, March 4, 2015 at 11:03:13 PM UTC+8, jsherril wrote:
On 03/04/2015 09:48 AM, Peter Santiago wrote:
Already restart the whole machine…
Processing by ForemanTasks::TasksController#resume as HTML
Warning!Cannot do
Dynflow::Executors::Abstract::Execution[execution_plan_id:
0e2af595-8e76-4ec7-aef0-9f1b467e9dce, finished:
#<Dynflow::Future:0x0000000ec0f428>], no connection to a Listener
If you feel this is an error with Foreman itself, please open a new issue
with Foreman ticketing system
<Issues - Foreman>, You would probably need to
attach the Full trace
<https://llin417.xhl.chevrontexaco.net/foreman_tasks/tasks/8658b352-62d3-4508-9702-cbb1313cb316/resume#>
and relevant log entries. Dynflow::Error Cannot do Dynflow::Executors::Abstract::Execution[execution_plan_id:
0e2af595-8e76-4ec7-aef0-9f1b467e9dce, finished:
#<Dynflow::Future:0x0000000ec0f428>], no connection to a Listener
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall'
···
On Friday, March 6, 2015 at 2:49:35 PM UTC+8, Peter Santiago wrote:
>
> BTW.. Using RHEL 6.6
>
> Seems to be the same bug in http://projects.theforeman.org/issues/9068
>
> On Thursday, March 5, 2015 at 4:10:53 PM UTC+8, Ivan Necas wrote:
>>
>> ----- Original Message -----
>>
>> > Starting listener
>> > Everything ready
>> > terminate called after throwing an instance of 'qpid::types::Exception'
>> > what(): Failed to initialise SSL: Failed: NSS error [-8015]
>> > (/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/sys/ssl/util.cpp:100)
>> >
>> (/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/client/SslConnector.cpp:149)
>> > Starting Rails environment
>> > /usr/share/foreman/app/models/concerns/encryptable.rb:10: warning:
>> already
>> > initialized constant ENCRYPTION_PREFIX
>> > Starting listener
>> > Everything ready
>> > Lockfile /usr/share/foreman/tmp/dynflow_executor.lock is already
>> present.
>> > terminate called after throwing an instance of 'qpid::types::Exception'
>> > what(): Failed to initialise SSL: Failed: NSS error [-8015]
>> > (/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/sys/ssl/util.cpp:100)
>> >
>> (/builddir/build/BUILD/qpid-0.26/cpp/src/qpid/client/SslConnector.cpp:149)
>> > Starting Rails environment
>> > /usr/share/foreman/app/models/concerns/encryptable.rb:10: warning:
>> already
>> > initialized constant ENCRYPTION_PREFIX
>>
>>
>> And we have the winner ^^^^^. Seems like an issue connecting to the qpid.
>> Somebody with gutterball experience //cc dustin, might know more on that.
>>
>> The service foreman-tasks status is not that valuable here, as it tries
>> to keep the service up: it if fails, it starts it again. There is room
>> for improving that.
>>
>> -- Ivan
>>
>> > [root@llin417 ~]# hammer -u admin ping
>> > [Foreman] password for admin:
>> > candlepin:
>> > Status: ok
>> > Server Response: Duration: 275ms
>> > candlepin_auth:
>> > Status: ok
>> > Server Response: Duration: 20ms
>> > pulp:
>> > Status: ok
>> > Server Response: Duration: 53ms
>> > pulp_auth:
>> > Status: ok
>> > Server Response: Duration: 49ms
>> > elasticsearch:
>> > Status: ok
>> > Server Response: Duration: 37ms
>> > foreman_tasks:
>> > Status: FAIL
>> > Server Response: Message: foreman-tasks service not running
>>
>> > On Wednesday, March 4, 2015 at 11:46:23 PM UTC+8, Ivan Necas wrote:
>> > > Hi,
>> >
>>
>> > > What about `hammer ping`?
>> >
>>
>> > > Also, please check
>> /usr/share/foreman/tmp/pids/dynflow_executor.output (we
>> > > already have an bug filed to have this file under /var/log/foreman),
>> for
>> > > enything interesting.
>> >
>>
>> > > -- Ivan
>> >
>>
>> > > ----- Original Message -----
>> >
>> > > > [root@llin417 ~]# katello-service status
>> >
>> > > > qpidd (pid 2414) is running...
>> >
>> > > > tomcat6 (pid 2253) is running... [ OK ]
>> >
>> > > > mongod (pid 2808) is running...
>> >
>> > > > elasticsearch (pid 2156) is running...
>> >
>> > > > celery init v10.0.
>> >
>> > > > Using config script: /etc/default/pulp_resource_manager
>> >
>> > > > node resource_manager (pid 3516) is running...
>> >
>> > > > celery init v10.0.
>> >
>> > > > Using config script: /etc/default/pulp_workers
>> >
>> > > > node reserved_resource_worker-0 (pid 3580) is running...
>> >
>> > > > node reserved_resource_worker-1 (pid 3596) is running...
>> >
>> > > > celery init v10.0.
>> >
>> > > > Using configuration: /etc/default/pulp_workers,
>> > > > /etc/default/pulp_celerybeat
>> >
>> > > > pulp_celerybeat (pid 3419) is running.
>> >
>> > > > httpd (pid 2361) is running...
>> >
>> > > > dynflow_executor is running.
>> >
>> > > > dynflow_executor_monitor is running.
>> >
>> > > > [root@llin417 ~]# /etc/init.d/foreman-tasks status
>> >
>> > > > dynflow_executor is running.
>> >
>> > > > dynflow_executor_monitor is running.
>> >
>> > > >
>> >
>> > > >
>> >
>> > > > On Wednesday, March 4, 2015 at 11:03:13 PM UTC+8, jsherril wrote:
>> >
>> > > > >
>> >
>> > > > > On 03/04/2015 09:48 AM, Peter Santiago wrote:
>> >
>> > > > >
>> >
>> > > > > Already restart the whole machine...
>> >
>> > > > >
>> >
>> > > > > Processing by ForemanTasks::TasksController#resume as HTML
>> >
>> > > > > Parameters:
>> >
>> > > > >
>> {"authenticity_token"=>"WvcrrzSEvvrLUwprH5SRWR9QHVyseR0prikr5lkQ6us=",
>> >
>> > > > > "id"=>"e4f1a1ff-c9b3-4b43-a03d-9476b9a2d93c"}
>> >
>> > > > >
>> >
>> > > > >
>> >
>> > > > > Can you confirm that the foreman-tasks service is running?
>> >
>> > > > >
>> >
>> > > > > -Justin
>> >
>> > > > >
>> >
>> > > > > Connection refused -
>> "/usr/share/foreman/tmp/sockets/dynflow_socket"
>> >
>> > > > > (Errno::ECONNREFUSED)
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
>>
>> >
>> > > > > `initialize'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
>>
>> >
>> > > > > `new'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:142:in
>>
>> >
>> > > > > `connect'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:91:in
>>
>> >
>> > > > > `block in on_message'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:859:in
>>
>> >
>> > > > > `block in assigns'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
>>
>> >
>> > > > > `tap'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:858:in
>>
>> >
>> > > > > `assigns'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:138:in
>>
>> >
>> > > > > `match_value'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:116:in
>>
>> >
>> > > > > `block in match'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
>>
>> >
>> > > > > `each'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/algebrick-0.4.0/lib/algebrick.rb:115:in
>>
>> >
>> > > > > `match'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/executors/remote_via_socket/core.rb:79:in
>>
>> >
>> > > > > `on_message'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in
>>
>> >
>> > > > > `block in on_envelope'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in
>>
>> >
>> > > > > `call'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/future.rb:75:in
>>
>> >
>> > > > > `evaluate_to'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:80:in
>>
>> >
>> > > > > `on_envelope'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:72:in
>>
>> >
>> > > > > `receive'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>>
>> >
>> > > > > `block (2 levels) in run'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>>
>> >
>> > > > > `loop'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>>
>> >
>> > > > > `block in run'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>>
>> >
>> > > > > `catch'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:99:in
>>
>> >
>> > > > > `run'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.3/lib/dynflow/micro_actor.rb:13:in
>>
>> >
>> > > > > `block in initialize'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
>>
>> >
>> > > > > `call'
>> >
>> > > > >
>> /opt/rh/ruby193/root/usr/share/gems/gems/logging-1.8.1/lib/logging/diagnostic_context.rb:323:in
>>
>> >
>> > > > > `block in create_with_logging_context'
>> >
>> > > > > Operation FAILED: Cannot do
>> >
>> > > > > Dynflow::Executors::Abstract::Execution[execution_plan_id:
>> >
>> > > > > ecf62e11-29e0-4685-88f7-ad47bc813264, finished:
>> >
>> > > > > #], no connection to a Listener
>> >
>> > > > > Rendered common/500.html.erb within layouts/application (5.4ms)
>> >
>> > > > > Rendered layouts/base.html.erb (1.3ms)
>> >
>> > > > > Completed 500 Internal Server Error in 44ms (Views: 23.9ms |
>> > > > > ActiveRecord:
>> >
>> > > > > 1.8ms)
>> >
>> > > > >
>> >
>> > > > > --
>> >
>> > > > > 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-user...@googlegroups.com .
>> >
>> > > > > To post to this group, send email to forema...@googlegroups.com
>> >
>> > > > > .
>> >
>> > > > > Visit this group at http://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 the Google
>> Groups
>> >
>> > > > "Foreman users" group.
>> >
>> > > > To unsubscribe from this group and stop receiving emails from it,
>> send an
>> >
>> > > > email to foreman-user...@googlegroups.com .
>> >
>> > > > To post to this group, send email to forema...@googlegroups.com .
>> >
>> > > > Visit this group at http://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 the Google
>> Groups
>> > "Foreman users" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to foreman-user...@googlegroups.com .
>> > To post to this group, send email to forema...@googlegroups.com .
>> > Visit this group at http://groups.google.com/group/foreman-users .
>> > For more options, visit https://groups.google.com/d/optout .
>>
>
