Hi,
I also had to roll back : nordugrid bdii was crashing very hard : it was leaving lock and pid files behind (as always when there is a crash...), thus preventing any further restarts.
I personally downgraded this way :
# yum downgrade openldap-servers-2.4.23-34.el6_5.1 openldap-2.4.23-34.el6_5.1 openldap-clients-2.4.23-34.el6_5.1
And then I made sure the ARC ldap is not updated until further notice :
# yum versionlock openldap{,-clients,-servers}
Loaded plugins: priorities, protectbase, security, versionlock
Adding versionlock on: 0:openldap-2.4.23-34.el6_5.1
Adding versionlock on: 0:openldap-clients-2.4.23-34.el6_5.1
Adding versionlock on: 0:openldap-servers-2.4.23-34.el6_5.1
versionlock added: 3
Done... for now.
Regards
-----Message d'origine-----
De : LHC Computer Grid - Rollout [mailto:[log in to unmask]] De la part de Stephen Jones
Envoyé : mardi 6 octobre 2015 17:25
À : [log in to unmask]
Objet : Re: [LCG-ROLLOUT] TOP BDII issues with CentOS 6.7 (openldap-servers-2.4.40-5.el6.x86_64)
Hi Winnie,
On 10/06/2015 02:01 PM, Winnie Lacesso wrote:
> But we haven't restarted bdii & slapd has been running 17days.
You had a close shave there. At present, you are precariously perched on
the rim of disaster.
> It's quite dangerous, and it was messy to roll it back.
> I'm back to openldap-servers-2.4.23-34.el6_5.1.x86_64 and it look stable
> now.
> We were considering just "yum history undo 236":
Run APEL now, to make sure all your accounting is sent over before
anything else. Also, suspend autoupdates, else you'll wind up doing a
lot of work for nothing!
Next, if you haven't rebooted it, why bother doing anything? A new
version will come out in due course, so wait until it shows up and go
straight to that. That's safer than any other option, assuming you don't
need to reboot (or have a reboot imposed upon you!) That way, there's no
downtime and hardly any work. But it leaves your system temporarily
inconsistent. Do you care?
If you _must_ roll it back, it would be great if this "yum history"
thingie works. I've never heard of it - I rolled it back the old
fashioned way, i.e. I removed the broken openldap, openldap-servers and
openldap-clients, and all dependencies (i.e. bdii, nordugrid-arc-arex,
nordugrid-arc-aris , nordugrid-arc-compute-element,
nordugrid-arc-ldap-infosys.) Then I reinstalled openldap* back to the
older, working version, then rolled the dependencies back on to the same
versions that they were before I did anything. It seems to have worked,
although I had to localinstall one package which seemed reluctant to go
in from the yum repo.
BTW: my saviour was "repoquery --show-duplicates packagename"
Cheers,
Steve
--
Steve Jones [log in to unmask]
Grid System Administrator office: 220
High Energy Physics Division tel (int): 43396
Oliver Lodge Laboratory tel (ext): +44 (0)151 794 3396
University of Liverpool http://www.liv.ac.uk/physics/hep/
|