Koozali.org: home of the SME Server

[SOLVED] Problem with accidental Samba upgrade to 4.1.18

Offline miroj

  • *
  • 26
  • +0/-0
[SOLVED] Problem with accidental Samba upgrade to 4.1.18
« on: August 23, 2015, 10:00:34 AM »
On SME 9 64bit I do have SOGo installation. During upgrade of SOGo, by my mistake, Samba was upgraded to 4.1.18 from SOGo repo. In every day usage there are no issues, but I have discovered that I can't join new Windows machines to SME Domain. SME is in a server-gateway mode, playing Windows domain controller.

The smbclient -L localhost returns Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED).

Before going with re-installation and returning content from backup, any idea or advice how to fix this situation?
« Last Edit: August 25, 2015, 07:20:25 PM by miroj »
---
"Open Source will apear on your machines anyway"
Paolo Malinverno
Vice President, Gartner Research

guest22

Re: Problem with accidental Samba upgrade to 4.1.18
« Reply #1 on: August 23, 2015, 12:21:47 PM »
See what packages were installed in the yum log. Yum downgrade these.

Offline miroj

  • *
  • 26
  • +0/-0
Re: Problem with accidental Samba upgrade to 4.1.18
« Reply #2 on: August 23, 2015, 01:05:34 PM »
I have tried that, but unfortunately it becomes a dependency hell, and yum can't handle the downgrade to original packages  :sad:.
---
"Open Source will apear on your machines anyway"
Paolo Malinverno
Vice President, Gartner Research

guest22

Re: Problem with accidental Samba upgrade to 4.1.18
« Reply #3 on: August 23, 2015, 01:09:42 PM »
Then I suggest you save yourself a lot of time and possible future issues, and re-install.

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: Problem with accidental Samba upgrade to 4.1.18
« Reply #4 on: August 23, 2015, 02:03:46 PM »
On SME 9 64bit I do have SOGo installation. During upgrade of SOGo, by my mistake, Samba was upgraded to 4.1.18 from SOGo repo.
I would be interested on how you upgraded samba from the sogo repository, just to avoid other mistakes. I tried to use --enablerepo=sogo and I can't upgrade samba.

concerning samba, first you have to do full backups, and after you can try

a) either reinstall
b) or try to remove samba (you are looking for samba samba-client samba-common samba-winbind samba-winbind-clients)
rpm -e --nodeps samba
rpm -e --nodeps samba-\*
yum install samba samba-client samba-common samba-winbind samba-winbind-clients

if you have other rpm which are blocking you, remove them and think to reinstall them after
« Last Edit: August 23, 2015, 02:05:47 PM by stephdl »
See http://wiki.contribs.org/Koozali_Foundation
irc : Freenode #sme_server #sme-fr

!!! Please write your knowledge to the Wiki !!!

Offline miroj

  • *
  • 26
  • +0/-0
Re: Problem with accidental Samba upgrade to 4.1.18
« Reply #5 on: August 25, 2015, 07:19:47 PM »
Thank you for the advices. I have opted for option a), the re-installation, due the problems with the removal of rpms. Just for the info, after successful restore, everything is fine and normal.

I'm not sure what command I have issued to upgrade the Samba packages, but I'm positive that the packages were from the SOGo repository. It was my mistake, since in the wiki the SOGo upgrade command is clearly stated. Might be that I have just enabled SOGo repo and just made yum upgrade, but I can't confirm it.

Thank you once again for the help and  the advice.
---
"Open Source will apear on your machines anyway"
Paolo Malinverno
Vice President, Gartner Research