Topic: Updates not working.

[ansentry]

Two weeks ago I installed 8.0beta7 onto a HP DC7800 machine and then did a restore (150GB) all went well, except that updates are not working. I am not receiving any emails re updates (my backup emails are working fine) “Update are available” not appearing in Software Installer.

 I have ran yum clean all and then yum update – response is “No Packages marked for Update”.

At the same location I loaded a machine with 8.0beta7 and using yum update it downloaded and installed updates fine.

I also have a machine running 8.0beta7 at my home/office and it updates fine.

This is what I'm getting when I run "yum update" from the NON updating machine

[root@sme7 ~]# yum update
Loaded plugins: fastestmirror, protect-packages, smeserver
Loading mirror speeds from cached hostfile
 * smeaddons: distro.ibiblio.org
 * smeextras: distro.ibiblio.org
 * smeos: distro.ibiblio.org
 * smeupdates: distro.ibiblio.org
Setting up Update Process
No Packages marked for Update

This is what I get when I run "yum update" from my home/office machine (this one is updating fine)

[root@sme7 ~]# yum update
Loaded plugins: fastestmirror, protect-packages, smeserver
Loading mirror speeds from cached hostfile
 * base: mirror.optus.net
 * smeaddons: sme-mirror.firewall-services.com
 * smeextras: sme-mirror.firewall-services.com
 * smeos: sme-mirror.firewall-services.com
 * smeupdates: sme-mirror.firewall-services.com
 * updates: mirror.optus.net
Excluding Packages from CentOS - os
Finished
Excluding Packages from CentOS - updates
Finished
Setting up Update Process
No Packages marked for Update

Any help would be appreciated, I have not filled out a bug report as yet. With 2 machines running fine I thought there may be something I can do to fix the faulty updater.

[janet]

ansentry

Two weeks ago I installed 8.0beta7 onto a HP DC7800 machine and then did a restore (150GB) all went well, except that updates are not working.

Restore from what, sme 7.5.1 or ...?

Seems as if some of your repos may be disabled
Show output of
db yum_repositories show base
db yum_repositories show updates

If status = disabled then enable with

db yum_repositories setprop base status enabled
db yum_repositories setprop updates status enabled
signal-event yum-modify

If above scenario exists, then please report as a bug, sme8 repos should be enabled as default and not follow the sme7 settings

[ansentry]

Mary,

Thanks for your reply. Yes the "not working" machine was restored from 7.5.1. The machine that is my home office one was also restored from 7.5.1 and it is updating fine.

Here are the results of running:
db yum_repositories show base
db yum_repositories show updates

Machine that is not doing updates

RESULT OF: db yum_repositories show base

base=repository
    BaseURL=http://vault.centos.org/4.9/os/$basearch
    EnableGroups=no
    Exclude=initscripts,libgsf
    GPGCheck=yes
    MirrorList=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
    Name=CentOS - os
    Visible=yes
    status=disabled

RESULT OF:db yum_repositories show updates

updates=repository
    BaseURL=http://vault.centos.org/4.9/updates/$basearch
    EnableGroups=no
    Exclude=initscripts,libgsf
    GPGCheck=yes
    MirrorList=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
    Name=CentOS - updates
    Visible=yes
    status=disabled
   
RESULT OF db yum_repositories base setprop status enabled
   
    usage:
    /sbin/e-smith/db dbfile keys
    /sbin/e-smith/db dbfile print [key]
    /sbin/e-smith/db dbfile show [key]
    /sbin/e-smith/db dbfile get key
    /sbin/e-smith/db dbfile set key type [prop1 val1] [prop2 val2] ...
    /sbin/e-smith/db dbfile setdefault key type [prop1 val1] [prop2 val2] ...
    /sbin/e-smith/db dbfile delete key
    /sbin/e-smith/db dbfile printtype [key]
    /sbin/e-smith/db dbfile gettype key
    /sbin/e-smith/db dbfile settype key type
    /sbin/e-smith/db dbfile printprop key [prop1] [prop2] [prop3] ...
    /sbin/e-smith/db dbfile getprop key prop
    /sbin/e-smith/db dbfile setprop key prop1 val1 [prop2 val2] [prop3 val3] ...
    /sbin/e-smith/db dbfile delprop key prop1 [prop2] [prop3] ...
   

RESULT OF: db yum_repositories updates setprop status enabled

usage:
    /sbin/e-smith/db dbfile keys
    /sbin/e-smith/db dbfile print [key]
    /sbin/e-smith/db dbfile show [key]
    /sbin/e-smith/db dbfile get key
    /sbin/e-smith/db dbfile set key type [prop1 val1] [prop2 val2] ...
    /sbin/e-smith/db dbfile setdefault key type [prop1 val1] [prop2 val2] ...
    /sbin/e-smith/db dbfile delete key
    /sbin/e-smith/db dbfile printtype [key]
    /sbin/e-smith/db dbfile gettype key
    /sbin/e-smith/db dbfile settype key type
    /sbin/e-smith/db dbfile printprop key [prop1] [prop2] [prop3] ...
    /sbin/e-smith/db dbfile getprop key prop
    /sbin/e-smith/db dbfile setprop key prop1 val1 [prop2 val2] [prop3 val3] ...
    /sbin/e-smith/db dbfile delprop key prop1 [prop2] [prop3] ...

I THEN RAN:signal-event yum-modify

I THEN RAN: signal-event post-upgrade; signal-event reboot

After the reboot I ran (separately)
db yum_repositories show base
db yum_repositories show updates
Nothing has changed. It is still says:  status=disabled (on both)

[janet]

ansentry

Oops sorry there was a typo mistake in the commands, do

db yum_repositories setprop base status enabled
db yum_repositories setprop updates status enabled
signal-event yum-modify
perhaps also add in
yum clean all

It sounds like you did not correctly update your sme7.5.1 box, there were further updates released re yum issues and Centos end of life.
Please refer to a sticky post in the sme 7 forums.

I think sme8 repos should be enabled as default and not follow the sme7 settings so it might be a good idea that you report this as a bug

[ansentry]

Mary,

Thanks for your reply, however I can see any difference in the commands you posted;

db yum_repositories setprop base status enabled (new)
db yum_repositories setprop base status enabled (original)

db yum_repositories setprop updates status enabled (new)
db yum_repositories setprop updates status enabled (original)

signal-event yum-modify (new)
signal-event yum-modify (original)

[janet]

ansentry

I modified my earlier post so the error was not accidently used by other people.
Originally the setprop & base or updates keys were swapped, check your command history to see (press up arrow).
You used:

RESULT OF db yum_repositories base setprop status enabled
RESULT OF: db yum_repositories updates setprop status enabled

so repeat the process with the correct commands

[ansentry]

Mary,

Thank you very much for your help, ran the commands and now the server is downloading updates.

Thanks again.