Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: anivio on September 25, 2010, 09:36:23 AM
-
Hi!
Every day i get an email that yum updates for samba and bzip are available but the sme server manager gives me the information that the system is up to date.
Whats right? What do i have to do?
Thank you.
-
What do i have to do?
You should probably wait 24-48hours to ensure all the mirrors have sync'd and after that you should report it in the bug tracker.
You may also find that if you have waited long enough for the mirrors to sync, a reboot of the server and a re-run of the updates will also resolve the issue.
I believe this question has arisen on a number of occasions previously. As search for "yum update" and similiar should return some instructions on running "yum clean all" and "yum update" from the command line which will also likely solve your problem.
HTH
P
-
I recently had a similar problem. I received an email that there were samba updates available and they showed up in software updater so I installed them and got the following showing the update was unsuccessful.
Software installer
SUCCESS
Operation status report
The system needs to be reconfigured after adding or removing software, or applying updates.
Please click on the Reconfigure button at the bottom of this page to start the reconfiguration process. An automatic reboot will be initiated as part of this reconfiguration process
Loading "installonlyn" plugin
Loading "fastestmirror" plugin
Loading "smeserver" plugin
Loading "protect-packages" plugin
Setting up Update Process
Setting up repositories
Loading mirror speeds from cached hostfile
Reading repository metadata in from local files
http://ftp.monash.edu.au/pub/linux/CentOS/4.8/updates/i386/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://mirror.internode.on.net/pub/centos/4.8/updates/i386/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://mirror.intrapower.net.au/pub/centos/4.8/updates/i386/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
http://ftp.stu.edu.tw/Linux/CentOS/4.8/updates/i386/repodata/primary.xml.gz: [Errno 4] Socket Error: timed out
Trying other mirror.
http://ftp.cs.pu.edu.tw/Linux/CentOS/4.8/updates/i386/repodata/primary.xml.gz: [Errno 14] HTTP Error 404: Not Found
Trying other mirror.
http://centos.mirror.cdnetworks.com/4.8/updates/i386/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
Excluding Packages from CentOS - os
Finished
Excluding Packages from CentOS - updates
Finished
Could not find update match for samba.i386
Could not find update match for samba-common.i386
Could not find update match for samba-client.i386
No Packages marked for Update/Obsoletion
The system needs to be reconfigured after adding or removing software, or applying updates.
Please click on the Reconfigure button at the bottom of this page to start the reconfiguration process. An automatic reboot will be initiated as part of this reconfiguration process
I clicked on the re-configure button, the server re-booted and then the software installer said it was up to date. Then I kept getting emails saying that there were samba updates available but the software installer was still saying the system was up to date.
In the end I logged in as root and did the following commands.
signal-event post-upgrade
signal-event reboot
After the reboot the software updater showed the updates as available and they installed ok.
I have no idea what caused the problem.
-
Sorry I am a relative newbie to SME but I too have started to have this happen. It has happened the last two update pushes.....and both times I have had to do the manual
signal-event post-upgrade
and
signal-event reboot
commands to get the new updates to be shown in the server-manager. How do I go about finding why this is continually happening as of late?
I have just this week gotten now my 3rd set of update notification emails (for bind updates) but they are not being listed in the software installer within the server-manager but I have verified that they are available for download from the mirrors.
-
I have just this week gotten now my 3rd set of update notification emails (for bind updates) but they are not being listed in the software installer within the server-manager but I have verified that they are available for download from the mirrors.
'bind' is not used in SME server, so you don't need to worry about those updates. However, you don't want to be getting notifications which don't make sense. You should report your problem in detail, via the bug tracker. Hopefully someone will help you to investigate carefully and work out what is going on.
-
Thanks Charlie....Thats what I thought from RTFM (lol) Will try to figure out the bug tracker system and get a ticket submitted ...
-
It's not bind that's trying to be updated, more specifically it's bind-utils and bind-libs, which SME Server does use.
-
thats what they were...I just remembered "bind"...
-
I'm seeing this on multiple machines now! Vanilla 7.5.1 system included!
-
http://bugs.contribs.org/show_bug.cgi?id=6159
Is this familiar?
-
I've got the same symptoms on a server. It last did an update itself on December 8th. I've posted it to the bug mentioned.
-
I am a certified Quality Engineer, and as such would point out that the software installer is a feature of SME server that at present is not working well on several machines. Thus we should be free to discuss that feature of SME server in the forum. Now we can discuss if the feature is working to specification, and if the email notifications are part of a different feature of SME Server, and if the emails are from several bugs, or are a virus, or our own user mods. BUT it is not within the power of the average user to determine if the unwanted behavior of the Software Updater and Update Notifier are the same bug as was reported many months ago, or even are bugs! Just because something is not working to my liking does not make it a bug!
Many times I've learned that a tiny change I made in one area has had unintended consequences in another! But they are NOT bugs, just unintended consequences! Like putting salt in your coffee instead of sugar. I don't ask my wife to make fresh coffee if I'm the one who put in the salt! Why lumber the bug team when users want to discuss a behavior?
Remember, our Microsoft machines freeze up at least twice a month running updates, and perhaps SME server is SUPPOSED to install those updates automatically! How would we know?
-
And on to the behavior!
After running the Control Panel reconfigure command, the problem persisted! But manually running the post upgrade commands one at a time made the updates visible!
So I'm even more confused than before!
-
Mike;
The standard that is called for many times in the forums is that," if something does not work as intended, raise a bug". So I did.
The more people who report a bug or unintended consequence, the more focus will be put on solving. It seems as though this bug is gathering some steam.
Since I posted the bug, I've been doing the yum clean all, yum update, signal-event post upgrade, signal-event reboot routine.
That being said, your wife sounds like a real keeper :-), I usually end up making the coffee.
-
Speaking from a QA basis, the bug that is of interest to the engineers is often of no interest to users! Users need work-arounds and alternative solutions!
I point this out because there are numerous YUM bugs reported. What we need is for someone to figure out the sequence that cause the issue, and it is the forum that creates the visibility! I'd assume a lot of people are now more sensitive to update issues, and someone may figure out the sequence that leads to the problem.
Of interest to me was that I did NOT yum clean all, yum update, just signal-event post upgrade and signal-event reboot at the command prompt. Yet reconfigure from control panel had not solved the issue!
SO what is the difference? Because after a software install, I use the reconfigure reboot on the software installer page, not the command prompt.
So we may have a bug on the software installer web page, not in YUM.
I'll add that to the bug report if I can find it!