Koozali.org: home of the SME Server

Obsolete Releases => SME 8.x Contribs => Topic started by: newburns on September 19, 2013, 01:05:19 AM

Title: [SOLVED]Wrong SOGo Version needs Removal
Post by: newburns on September 19, 2013, 01:05:19 AM
I have SME 8 x64. I accidentally installed from the standard SOGo repository which is x86. The x64 instructions were the last thing on the page.
How can I completely remove sogo and all dependencies?
I have done
Code: [Select]
yum remove smeserver-sogo sogo
This allowed me to reinstall according to the x64 instructions in the wiki, however, I cannot start the service.
Returns error
Code: [Select]
Starting SOGo:
/usr/sbin/sogod: error while loading shared libraries: libGDLContentStore.so.4.9: wrong ELF class: ELFCLASS32
  sogo                                                     [FAILED]

I know this is 100% user error, I just want to remove all traces of sogo, and reinstall the proper way. Thanks
Title: Re: Wrong SOGo Version needs Removal
Post by: newburns on September 19, 2013, 01:21:41 AM
It seems this did the trick
Code: [Select]
rpm -e sogo smeserver-sogo
I even took a text file of the rpm-ql list for sogo and smeserver-sogo for comparison.
Only 3 files remained. Which were in the GNUsteps folder.
But It's great now.
Title: Re: Wrong SOGo Version needs Removal
Post by: newburns on September 21, 2013, 03:15:14 AM
Spoke too soon.

Not fixed. Again, I know this is user error. I installed sogo according to the x86 repository from the instructions.
I tried to remove the installation with rpm -e
I updated the repository to the one listed on the bottom of the wiki page.
I did a yum clean all

I am still left with this error:
Code: [Select]
Starting SOGo:
/usr/sbin/sogod: error while loading shared libraries: libGDLContentStore.so.4.9: cannot open shared object file: No such file or directory

I think there's a conf file somewhere instructing sogo to use the wrong lib folder.
Title: Re: Wrong SOGo Version needs Removal
Post by: janet on September 21, 2013, 04:14:59 AM
newburns

I googled this
sogod wrong ELF class

It gives a few clues based on other reported similar issues
Read the first few posts/threads.

My guess is you have wrong architecture versions of other dependency packages.
You removed the main sogo packages for a certain arch but not the dependencies.
As you were switching between x86 install on x64 & vice versa, maybe my guess is appropriate.

Here is a list of packages that want to be installed on a relatively clean sme8, 32 bit so using these install steps
http://wiki.contribs.org/Sogo#Install

I suggest you go through the list & remove them one by one using
rpm -e packagename
You should get a warning if there are other rpms dependent on the package you are trying to uninstall, so remove the other package first, provided of course they are not needed by the base install of sme server or other known apps you have installed.

When you have removed them do a
signal-event post-upgrade
signal-event reboot

then you could run a standard
yum update
to replace any packages that the sme system requires.
I assume none will be required.

Then you can proceed to do your x64 install, correctly this time.

Here is what I did on sme8 32 bit
yum install --enablerepo=sogo --enablerepo=nethsme --enablerepo=epel smeserver-sogo memcached

Installing:
 memcached                     i386        1.4.5-1.el5                     epel          71 k
 smeserver-sogo                noarch      0.6-1.el5.nh                    nethsme       29 k
Installing for dependencies:
 gnustep-base                  i386        1.23.0-1                        sogo         1.7 M
 gnustep-make                  i386        2.6.1-1                         sogo         202 k
 libevent                      i386        1.4.13-1                        base         112 k
 libffi                        i386        3.0.10-1                        sogo          15 k
 libmemcached                  i386        0.34-1                          sogo         113 k
 libobjc                       i386        4.1.2-54.el5                    base         106 k
 sogo                          i386        2.0.7-1.el5                     sogo         3.2 M
 sogo-tool                     i386        2.0.7-1.el5                     sogo          39 k
 sope49-appserver              i386        4.9-20130722_1664.el5.1         sogo         889 k
 sope49-cards                  i386        2.0.7-1.el5                     sogo         159 k
 sope49-core                   i386        4.9-20130722_1664.el5.1         sogo         328 k
 sope49-gdl1                   i386        4.9-20130722_1664.el5.1         sogo         158 k
 sope49-gdl1-contentstore      i386        2.0.7-1.el5                     sogo          56 k
 sope49-gdl1-mysql             i386        4.9-20130722_1664.el5.1         sogo          32 k
 sope49-ldap                   i386        4.9-20130722_1664.el5.1         sogo          47 k
 sope49-mime                   i386        4.9-20130722_1664.el5.1         sogo         275 k
 sope49-sbjson                 i386        2.3.1-20130722_1664.el5.1       sogo          16 k
 sope49-xml                    i386        4.9-20130722_1664.el5.1         sogo         210 k


Before doing the above it might be useful to run
/sbin/e-smith/audittools/newrpms
to show you what versions of what packages you have installed.
Keep a record of this & compare it to "after the changes suggested above", & compare with a clean install of sme8 if you can.
Title: Re: Wrong SOGo Version needs Removal
Post by: newburns on September 21, 2013, 03:14:44 PM
As always, Thanks so much.

That fixed it. Removing each rpm independently, and reinstallation was perfect.
Is there anyway to get that list of installed rpm's without someone with a different machine having to do it for me?
Title: Re: Wrong SOGo Version needs Removal
Post by: janet on September 21, 2013, 04:28:50 PM
newburns

Keep a clean sme 8 install for doing test installs of contribs etc.
Do a yum install to see all the rpms that are going to be installed & say no (n) at the end.
Use the newrpms audit tool to keep this machine clean.
It sounds like you have plenty of VM's so set one aside for this purpose.