Topic: accidental upgrade to beta version - clamav stopping incomming emails

[janet]

Allan Pritchard

This is the error I got below. Took ages to type.

You should install the remote access ssh program called putty.exe on your windows workstation. Search Internet for free download.
Then access the sme server using that (in server manager first enable ssh access via passwords or key for local access as appropriate/required).

When you have a (DOS looking) window open in Putty, you can right click on the little logo/icon in the top left corner and simply copy the contents of the screen output (ie the error message & previous commands etc) into the Windows clipboard.
Then transfer to your Windows based email client, browser or whatever and paste the contents.

Saves typing it all manually, at the risk of making an error while transcribing it too.

[Allan Pritchard]

Thanks Mary

I've heard of people talking about putty on forums, I'll install it asap. I have found there seems is a gap between novices like me and people who know quite a bit about general linux. I'm learning heaps but sometimes simple things take hours trying to find out commands and syntax. And of course embarrasing moments like having to have employees read out error messages from the server to type them in.  I'm always nervous about wasting peoples time with dumb questions. So far I have found people to be really helpful on this forum and don't mind explaining things. It is really appreciated.

take care
Allan

[janet]

Allan Pritchard

Most of us came from the same place you are coming from.

[CharlieBrady]

I've gained a little more knowledge - its much easier designing houses  .

Not for me

[Allan Pritchard]

Hello All

I am tacking this on to my old post as it follows on from the help all ready received.

My SME 7.4beta2 has been running smoothly however every day I get a list of updates available, even if I update the list never changes. Having searched through the forums I have found using /sbin/e-smith/audittools/newrpms that I have 3 pages worth of installed packages. Two of which are


smeserver-release.noarch                 26:7.4-0.beta2.el4.sme installed
smeserver-release.noarch                 26:7.3-1.el4.sme       installed

doing a yum list I find that I have all of the updates installed, one of which is below but it still keeps saying I need to install updates

smeserver-release.noarch                 26:7.4-1.el4.sme       smeos


As this is our production server I don't want to go and do something dumb which may bring everything to a crashing halt. I am guessing that the installed packages were created when I accidently upgraded to a beta release and also that packages in "newrpms" take president over the other ones in the yum list.

My question is am I on the right track and will deleting the installed packages from the "newrpms" revert my server back to a vanilla SME 7.4 system.


Your advice would be much appreciated.

Regards
Allan Pritchard

[janet]

Allan Pritchard

Have you done what was advised in reply #3 of this thread ie set repos to the correct sme defaults only
see
http://wiki.contribs.org/SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled

Also Charlies post in this thread here
http://forums.contribs.org/index.php/topic,42410.msg199685.html#msg199685

suggests you have had interrupted installs, so you may need to apply the same concepts to uninstall these
smeserver-release.noarch                 26:7.4-0.beta2.el4.sme installed
smeserver-release.noarch                 26:7.3-1.el4.sme       installed


You should then do

yum clean all
then do
yum update
signal-event post-upgrade
signal-event reboot

see
http://wiki.contribs.org/SME_Server:Documentation:FAQ#General

Hopefully that will upgrade your beta release to the final 7.4 release, otherwise just download the sme 7.4 iso, burn a CD and do an upgrade install from CD.

As you are already running a beta release on your production server, then I wouldn't be too worried about what version you now update to, as it can only be an improvement.
As always, do a backup first to be safe.

[Allan Pritchard]

Thanks Mary

Yes I did what was advised in post #3

I will try the same approach to upgrade the various components starting with smeserver-release.noarch

I have set up a clean test server with SME 7.4 and have compiled a list of the default yum packages. I'll see where mine differs.

Thanks again
Allan

[cactus]

I have set up a clean test server with SME 7.4 and have compiled a list of the default yum packages. I'll see where mine differs.

I do not think that would have been neccesarry as you could have used the audittools:

Code: [Select]

/sbin/e-smith/audittools/newrpmsAbove should give you a list of all packages that are not available in the repositories that should be enabled by default as listed here: http://wiki.contribs.org/SME_Server:Documentation:FAQ#Which_repositories_should_be_enabled .

[Allan Pritchard]

Sorry you miss understood me I set up a server so I could get the following list (only part list as an example)
 

DCC.i386                                 1.3.90-22.el4          installed
FuzzyOcr.noarch                          3.5.1-3.el4.sme        installed
LPRng.i386                               3.8.32-2.el4.sme       installed
MAKEDEV.i386                             3.15.2-3               installed
SysVinit.i386                            2.85-34.4              installed
acpid.i386                               1.0.3-2                installed
anacron.i386                             2.3-32                 installed
apmd.i386                                1:3.0.2-24             installed
apr.i386                                 0.9.4-24.9             installed
apr-util.i386                            0.9.4-22.el4           installed
aspell.i386                              12:0.60.3-7.1.el4.sme  installed
aspell-bg.i386                           50:0.50-11.2.2.el4.sme installed
aspell-da.i386                           50:0.50-12.2.2.el4.sme installed
aspell-de.i386                           50:0.50-11.2.2.el4.sme installed
aspell-el.i386                           50:0.50-4.2.2.el4.sme  installed
aspell-en.i386                           50:6.0-2.1.el4.sme     installed
aspell-es.i386                           50:0.50-13.2.2.el4.sme installed
 
My production server seems to have a mixture of versions of the above "packages" I'm not sure of the correct term. Some have updated but others refuse to update and every day I get the same email saying there are updates for my server.

Below is the fist few off my production server

DCC.i386                                 1.3.90-22.el4          installed
DCC.i386                                 1.3.66-21.el4          installed
FuzzyOcr.noarch                          3.5.1-3.el4.sme        installed
LPRng.i386                               3.8.32-2.el4.sme       installed
MAKEDEV.i386                             3.15.2-3               installed
SysVinit.i386                            2.85-34.4              installed
acpid.i386                               1.0.3-2                installed
anacron.i386                             2.3-32                 installed
apmd.i386                                1:3.0.2-24             installed
apr.i386                                 0.9.4-24.9             installed
apr-util.i386                            0.9.4-22.el4           installed
aspell.i386                              12:0.60.3-7.1.el4.sme  installed
aspell-bg.i386                           50:0.50-11.2.2.el4.sme installed
aspell-da.i386                           50:0.50-12.2.2.el4.sme installed
 
For example I have two versions of DCC.i386  on my production server, there are quite a few like this scattered through the list. Being a newbie I am unsure what should and shouldn't be there and what the consequences are of removing it.

I did notice that using /sbin/e-smith/audittools/newrpms on the new server there appares to be none listed but in pruduction server there is over 100 "newrpms" is that correct?

Confirming I have

CentOS-os
CentOS-updates
SME Server - addons
SME Server - os
SME Server - Updates

all enabled.
 
I'll use Charlies post to try and remove and update things manually. I'm hoping that one is causing the conflict and once removed the update process will work smoothly doing the rest.

[cactus]

Sorry you miss understood me I set up a server so I could get the following list (only part list as an example)

No, I did not. You misunderstood me. You did not need to setup a copy to diagnose what additional packages are installed as the script I pointed you to compares what RPMs are on your system to what is current in the repositories (the latest released status of the version your repositories are pointing to). So if you have installed and configured the advised repositories only it should report you what files are newer/unknown.

[Allan Pritchard]

Sorry I didn't quite understand, I thought you were pointing me to the page showing what repositories should be enabled. Reading further down the page I understand now and think can follow that.

Thanks for your help

Cheers
Allan