Koozali.org formerly Contribs.org

Standby machine for disaster recovery restore ?

Offline ReetP

  • *
  • 2,146
Re: Standby machine for disaster recovery restore ?
« Reply #30 on: December 08, 2018, 02:22:42 AM »
Get your prod box right first.

You should be able to remove and then reinstall the contribs from the smecontribs repo. You then know you have the right versions.

Make sure you have no relevant custom templates that might affect it.

After that sort Affa.
...
1. Read the Manual
2. Read the Wiki
3. Don't ask for support on Unsupported versions
4. I have a job, wife, and kids and do this in my spare time. If you want something fixed, please help.

Bugs are easier than you think: http://wiki.contribs.org/Bugzilla_Help

If you love SME and don't want to lose it, join in: http://wiki.contribs.org/Koozali_Foundation

Re: Standby machine for disaster recovery restore ?
« Reply #31 on: December 10, 2018, 10:27:50 AM »
Get your prod box right first.

Thank you.  I'll look at it this week and see if I can get it finalised.

Re: Standby machine for disaster recovery restore ?
« Reply #32 on: December 15, 2018, 09:12:59 PM »
A quick update. 

On the production server I uninstalled and installed roundcube and fetchmail, specifying the smecontribs repro in the examples above. However some packages were still pointing back to the stephdl repro so I reinstalled those as well. With hindsight perhaps I should have used the "--disablerepo=stephdl" command.

Anyway, this didn't resolve the missing packages on the backup so I've installed them by hand, so now when I run 

Code: [Select]
/sbin/e-smith/audittools/newrpms  The items on the production box are noted on the backup, and both using either the smecontribs or epel repros.

Fingers crossed that both boxes should now the the same...

The one issue is that if I run a yum info command on the new roundcube and fetchmail, they are noted in Red.  Do I need to explicitly or permanently enable the smecontibs repro with a command ?

Re: Standby machine for disaster recovery restore ?
« Reply #33 on: December 19, 2018, 02:42:12 PM »
Another quick question,   The Missing RPMs email is clear except for :

Code: [Select]
* The following packages are installed on both,
* the source 172.16.16.75 and on this backup host,
* but the version does not match:
*
gpg-pubkey-f5194398-527516a9

I've tried
Code: [Select]
yum info gpg-pubkey but is not finding anything. A quick read up suggests that it's indicative of a missing package. I have 12 of these on the production box but only 11 on the backup.

the output from
Code: [Select]
/sbin/e-smith/audittools/newrpms  shows the same packages on the backup as the production (backup has more).  Is there any other way to check on installed packages ?
« Last Edit: December 19, 2018, 05:00:49 PM by david000 »

Offline TerryF

  • grumpy old man
  • *
  • 1,115
Re: Standby machine for disaster recovery restore ?
« Reply #34 on: December 19, 2018, 11:15:31 PM »
Is there any other way to check on installed packages ?

Couple of ways..

# yum list installed
can list package multiple times

# rpm -qa
--
qui scribit bis legit

Re: Standby machine for disaster recovery restore ?
« Reply #35 on: December 20, 2018, 01:10:24 PM »
Couple of ways..

# yum list installed
can list package multiple times

# rpm -qa

Thank you.