Capsule server won't sync the repo contents

Hi,

I have a remote capsule server running in another site, it works well for a
while, but when we lately added a CentOS7.1 products, we found that the
capsule server didn't sync the new product repo, in the task list, I found
couple of "Generate Capsule Metadata and Sync" task were on running status
and result was pending, I don't know what they are pending on, can any one
point me to the correct direction on how to trouble shoot this?

Thanks
Sinux

BTW, I am running katello 2.2

··· On Thursday, August 6, 2015 at 1:51:50 PM UTC+8, sinux shen wrote: > > Hi, > > I have a remote capsule server running in another site, it works well for > a while, but when we lately added a CentOS7.1 products, we found that the > capsule server didn't sync the new product repo, in the task list, I found > couple of "Generate Capsule Metadata and Sync" task were on running status > and result was pending, I don't know what they are pending on, can any one > point me to the correct direction on how to trouble shoot this? > > Thanks > Sinux >

Have a look in the

Infrastructure -> Smart Proxies -> your capsule -> Lifecyle Environments

I had a problem with that a few weeks ago. The orgs LE wasn't selected for
the capsule and the content wasn't syncing.

··· On Thursday, 6 August 2015 02:52:33 UTC-3, sinux shen wrote: > > BTW, I am running katello 2.2 > > On Thursday, August 6, 2015 at 1:51:50 PM UTC+8, sinux shen wrote: >> >> Hi, >> >> I have a remote capsule server running in another site, it works well for >> a while, but when we lately added a CentOS7.1 products, we found that the >> capsule server didn't sync the new product repo, in the task list, I found >> couple of "Generate Capsule Metadata and Sync" task were on running status >> and result was pending, I don't know what they are pending on, can any one >> point me to the correct direction on how to trouble shoot this? >> >> Thanks >> Sinux >> >

Hi, Danilo,

I checked and confirmed that I already have both LE (prod and library) set
for my remote capsule, but doesn't work.

··· On Friday, August 7, 2015 at 2:31:12 AM UTC+8, Danilo Sousa wrote: > > Have a look in the > > Infrastructure -> Smart Proxies -> your capsule -> Lifecyle Environments > > I had a problem with that a few weeks ago. The orgs LE wasn't selected for > the capsule and the content wasn't syncing. > > On Thursday, 6 August 2015 02:52:33 UTC-3, sinux shen wrote: >> >> BTW, I am running katello 2.2 >> >> On Thursday, August 6, 2015 at 1:51:50 PM UTC+8, sinux shen wrote: >>> >>> Hi, >>> >>> I have a remote capsule server running in another site, it works well >>> for a while, but when we lately added a CentOS7.1 products, we found that >>> the capsule server didn't sync the new product repo, in the task list, I >>> found couple of "Generate Capsule Metadata and Sync" task were on running >>> status and result was pending, I don't know what they are pending on, can >>> any one point me to the correct direction on how to trouble shoot this? >>> >>> Thanks >>> Sinux >>> >>

Can you look at the data for the task that is stuck in pending? Do you see
any errors or is it just constantly polling? Did you at any time
re-register the capsule?

··· On Fri, Aug 7, 2015 at 3:52 AM, sinux shen wrote:

Hi, Danilo,

I checked and confirmed that I already have both LE (prod and library) set
for my remote capsule, but doesn’t work.

On Friday, August 7, 2015 at 2:31:12 AM UTC+8, Danilo Sousa wrote:

Have a look in the

Infrastructure -> Smart Proxies -> your capsule -> Lifecyle Environments

I had a problem with that a few weeks ago. The orgs LE wasn’t selected
for the capsule and the content wasn’t syncing.

On Thursday, 6 August 2015 02:52:33 UTC-3, sinux shen wrote:

BTW, I am running katello 2.2

On Thursday, August 6, 2015 at 1:51:50 PM UTC+8, sinux shen wrote:

Hi,

I have a remote capsule server running in another site, it works well
for a while, but when we lately added a CentOS7.1 products, we found that
the capsule server didn’t sync the new product repo, in the task list, I
found couple of “Generate Capsule Metadata and Sync” task were on running
status and result was pending, I don’t know what they are pending on, can
any one point me to the correct direction on how to trouble shoot this?

Thanks
Sinux


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.


Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

Hi Eric,

So sorry for the late response, I was stuck on some other project and just
went back, so I actually have tons of pending task saying: Generate Capsule
Metadata and Sync {"local"=>"en"} status was pause and result was pending.

Checking the errors on one of the paused pending task:

Action:

Actions::Pulp::Consumer::SyncNode

Input:

{"consumer_uuid"=>"7ff3babd-788e-49a7-bc92-be135054b508",
"repo_ids"=>["odw-centos71-os_x86_64"],
"remote_user"=>"admin",
"remote_cp_user"=>"foreman_admin",
"locale"=>"en"}

Output:

{"pulp_tasks"=>
[{"exception"=>nil,
"task_type"=>nil,
"_href"=>"/pulp/api/v2/tasks/ce30ca45-49bb-4a57-ae7d-0c6f8798220b/",
"task_id"=>"ce30ca45-49bb-4a57-ae7d-0c6f8798220b",
"tags"=>
["pulp:consumer:7ff3babd-788e-49a7-bc92-be135054b508",
"pulp:action:unit_update"],
"finish_time"=>nil,
"_ns"=>"task_status",
"start_time"=>nil,
"traceback"=>nil,
"spawned_tasks"=>[],
"progress_report"=>{},
"queue"=>"agent.dq",
"state"=>"accepted",
"worker_name"=>"agent",
"result"=>nil,
"error"=>nil,
"_id"=>{"$oid"=>"55d6259097f57923b2d9e4c7"},
"id"=>"55d6259097f57923b2d9e4c7"}],
"poll_attempts"=>{"total"=>3198, "failed"=>0}}

Exception:

StandardError: Abnormal termination (previous state: suspended)

Backtrace:

/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.8/lib/dynflow/execution_plan/steps/error.rb:12:innew'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.8/lib/dynflow/world.rb:204:in block (2 levels) in consistency_check' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.8/lib/dynflow/world.rb:202:ineach'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.8/lib/dynflow/world.rb:202:in block in consistency_check' /opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.8/lib/dynflow/world.rb:193:ineach'
/opt/rh/ruby193/root/usr/share/gems/gems/dynflow-0.7.8/lib/dynflow/world.rb:193:in consistency_check' /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.13/lib/foreman_tasks/dynflow.rb:50:inblock in initialize!'
/opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.13/lib/foreman_tasks/dynflow.rb:40:in tap' /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.13/lib/foreman_tasks/dynflow.rb:40:ininitialize!'
/opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.13/lib/foreman_tasks/engine.rb:77:in block in <class:Engine>' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:ininstance_exec'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:in run' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:55:inblock in run_initializers'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:in each' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:inrun_initializers'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:136:in initialize!' /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/railtie/configurable.rb:30:inmethod_missing'
/usr/share/foreman/config/environment.rb:12:in <top (required)>' /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:inrequire'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in require' /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inblock in require'
/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in load_dependency' /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inrequire'
/opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.13/lib/foreman_tasks/dynflow/daemon.rb:15:in run' /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.13/lib/foreman_tasks/dynflow/daemon.rb:50:inblock in run_background'
/opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/application.rb:249:in call' /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/application.rb:249:inblock in start_proc'
/opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/daemonize.rb:197:in call' /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/daemonize.rb:197:incall_as_daemon'
/opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/application.rb:253:in start_proc' /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/application.rb:293:instart'
/opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/controller.rb:70:in run' /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons.rb:195:inblock in run_proc'
/opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/cmdline.rb:109:in call' /opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons/cmdline.rb:109:incatch_exceptions'
/opt/rh/ruby193/root/usr/share/gems/gems/daemons-1.1.4/lib/daemons.rb:194:in run_proc' /opt/rh/ruby193/root/usr/share/gems/gems/foreman-tasks-0.6.13/lib/foreman_tasks/dynflow/daemon.rb:43:inrun_background'
/usr/bin/foreman-tasks:5:in `<main>'

I think it might be something happened on the forman server that running on
our RHEV and I used to created a snapshot and rollback at that point, and
the sync status might be broken because of that, still, just guess, not
quite sure about that.

··· On Thursday, August 13, 2015 at 9:04:41 PM UTC+8, Eric Helms wrote: > > Can you look at the data for the task that is stuck in pending? Do you see > any errors or is it just constantly polling? Did you at any time > re-register the capsule? > > On Fri, Aug 7, 2015 at 3:52 AM, sinux shen > wrote: > >> Hi, Danilo, >> >> I checked and confirmed that I already have both LE (prod and library) >> set for my remote capsule, but doesn't work. >> >> >> On Friday, August 7, 2015 at 2:31:12 AM UTC+8, Danilo Sousa wrote: >>> >>> Have a look in the >>> >>> Infrastructure -> Smart Proxies -> your capsule -> Lifecyle Environments >>> >>> I had a problem with that a few weeks ago. The orgs LE wasn't selected >>> for the capsule and the content wasn't syncing. >>> >>> On Thursday, 6 August 2015 02:52:33 UTC-3, sinux shen wrote: >>>> >>>> BTW, I am running katello 2.2 >>>> >>>> On Thursday, August 6, 2015 at 1:51:50 PM UTC+8, sinux shen wrote: >>>>> >>>>> Hi, >>>>> >>>>> I have a remote capsule server running in another site, it works well >>>>> for a while, but when we lately added a CentOS7.1 products, we found that >>>>> the capsule server didn't sync the new product repo, in the task list, I >>>>> found couple of "Generate Capsule Metadata and Sync" task were on running >>>>> status and result was pending, I don't know what they are pending on, can >>>>> any one point me to the correct direction on how to trouble shoot this? >>>>> >>>>> Thanks >>>>> Sinux >>>>> >>>> -- >> 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. >> > > > > -- > Eric D. Helms > Red Hat Engineering > Ph.D. Student - North Carolina State University >