Closed Bug 873967 Opened 13 years ago Closed 12 years ago

Collectd dependency issue on socorroadm.stage.private.phx1.mozilla.com

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Usul, Assigned: Usul)

Details

---> Package yajl.x86_64 0:1.0.7-3.el6 will be updated --> Processing Dependency: libyajl.so.1()(64bit) for package: collectd-4.10.8-2.el6.x86_64 --> Finished Dependency Resolution Error: Package: collectd-4.10.8-2.el6.x86_64 (@epel) Requires: libyajl.so.1()(64bit) Removing: yajl-1.0.7-3.el6.x86_64 (@rhel-x86_64-server-6) libyajl.so.1()(64bit) Updated By: yajl-2.0.3-1.el6.x86_64 (mozilla) Not found You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest I was trying to upgrade the kernel ...
This is us, not webops. The work around is the following : 1) yum -y remove yajl-1.0.7-3.el6.x86_64 2) yum -y update 3) puppetctl run (to get back collectd with the right deps) 4) reboot.
Assignee: server-ops-webops → ludovic
Component: Server Operations: Web Operations → Server Operations
QA Contact: nmaul → shyam
(In reply to Shyam Mani [:fox2mike] from comment #1) > 1) yum -y remove yajl-1.0.7-3.el6.x86_64 > 2) yum -y update > 3) puppetctl run (to get back collectd with the right deps) What does puppet log when step 3) is run? This may be something we can fix in the manifests.
(In reply to Richard Soderberg [:atoll] from comment #2) > (In reply to Shyam Mani [:fox2mike] from comment #1) > > 1) yum -y remove yajl-1.0.7-3.el6.x86_64 > > 2) yum -y update > > 3) puppetctl run (to get back collectd with the right deps) > > What does puppet log when step 3) is run? This may be something we can fix > in the manifests. Richard, I think the issue here is that the epel.repo file on this server is not under puppet control and didn't contain the exclude=collectd* . As well, I am in the process of upgrading collectd. Which will avoid this issue in the future.
Ah, thanks, that's good to know.
This is fixed.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.