Koozali.org: home of the SME Server

yum update 2013-01-17, samba conflict

Offline macwunder

  • *
  • 17
  • +0/-0
yum update 2013-01-17, samba conflict
« on: January 17, 2013, 04:04:13 PM »
Anyone else seeing this? This morning I saw a large update notification. When I try to update via shell, I see a lot of samba conflicts (and update will not run):

updates/filelists_db                                                                  |  94 kB     00:00     
--> Processing Dependency: /usr/bin/tdbbackup for package: e-smith-samba
--> Restarting Dependency Resolution with new changes.
--> Running transaction check
---> Package samba.i386 0:3.0.33-3.39.el5_8 set to be updated
--> Processing Dependency: samba-common = 3.0.33-3.39.el5_8 for package: samba
--> Running transaction check
---> Package samba-common.i386 0:3.0.33-3.39.el5_8 set to be updated
--> Processing Conflict: samba3x conflicts samba < 3.6.6-0.129.el5
--> Processing Conflict: samba3x conflicts samba-common < 3.6.6-0.129.el5
--> Processing Conflict: samba3x-common conflicts samba < 3.6.6-0.129.el5
--> Processing Conflict: samba3x-common conflicts samba-common < 3.6.6-0.129.el5
--> Processing Conflict: samba3x-client conflicts samba < 3.6.6-0.129.el5
--> Processing Conflict: samba3x-winbind conflicts samba-common < 3.6.6-0.129.el5
--> Finished Dependency Resolution
samba3x-winbind-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x-winbind conflicts with samba-common
samba3x-client-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x-client conflicts with samba
samba3x-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x conflicts with samba-common
samba3x-common-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x-common conflicts with samba
samba3x-common-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x-common conflicts with samba-common
samba3x-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x conflicts with samba
--> Running transaction check
---> Package kernel.i686 0:2.6.18-308.16.1.el5 set to be erased
--> Processing Conflict: samba3x conflicts samba < 3.6.6-0.129.el5
--> Processing Conflict: samba3x conflicts samba-common < 3.6.6-0.129.el5
--> Processing Conflict: samba3x-common conflicts samba < 3.6.6-0.129.el5
--> Processing Conflict: samba3x-common conflicts samba-common < 3.6.6-0.129.el5
--> Processing Conflict: samba3x-client conflicts samba < 3.6.6-0.129.el5
--> Processing Conflict: samba3x-winbind conflicts samba-common < 3.6.6-0.129.el5
--> Finished Dependency Resolution
samba3x-winbind-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x-winbind conflicts with samba-common
samba3x-client-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x-client conflicts with samba
samba3x-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x conflicts with samba-common
samba3x-common-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x-common conflicts with samba
samba3x-common-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x-common conflicts with samba-common
samba3x-3.6.6-0.129.el5.i386 from base has depsolving problems
  --> samba3x conflicts with samba
Error: samba3x-common conflicts with samba-common
Error: samba3x-client conflicts with samba
Error: samba3x-winbind conflicts with samba-common
Error: samba3x-common conflicts with samba
Error: samba3x conflicts with samba-common
Error: samba3x conflicts with samba

Wanting to make sure I didn't have some contrib messing things up, I ran newrpms:

Extra Packages
compat-libevent-11a.i386               3.2.1-1.el5.rf                  installed
device-mapper-multipath.i386           0.4.7-48.el5_8.2                installed
fping.i386                             2.4-1.b2.3.el4.rf               installed
gnustep-base.i386                      1.23.0-1                        installed
gnustep-make.i386                      2.6.1-1                         installed
hddtemp.i386                           0.3-0.beta15.1.el4.rf           installed
kernel.i686                            2.6.18-308.16.1.el5             installed
kernel.i686                            2.6.18-308.20.1.el5             installed
kpartx.i386                            0.4.7-48.el5_8.2                installed
libawl-php.noarch                      0.51-1                          installed
libffi.i386                            3.0.10-1                        installed
libmemcached.i386                      0.34-1                          installed
libobjc.i386                           4.1.2-52.el5_8.1                installed
lshw.i386                              2.15-1.el5.rf                   installed
memcached.i386                         1.4.2-1.el5                     installed
perl-rrdtool.i386                      1.2.30-1.el5.rf                 installed
phpmyadmin.noarch                      2.11.11.3-1.el4.rf              installed
rrdtool.i386                           1.2.30-1.el5.rf                 installed
sme-unjunkmgr.noarch                   1.1.3-1                         installed
smeserver-diskusage.noarch             0.0.1-13.el4.sme                installed
smeserver-hwinfo.noarch                1.0-15.el4.sme                  installed
smeserver-mailstats.noarch             0.0.3-14.el4.sme                installed
smeserver-mod_dav.noarch               0.1-18.el4.sme                  installed
smeserver-phpmyadmin.noarch            2.11.1.2-3.el4.sme              installed
smeserver-service_control.noarch       2.0-1                           installed
smeserver-sme8admin.noarch             1.3-3.el5.sme                   installed
smeserver-sogo.noarch                  0.5.6-1.el5.sme                 installed
smeserver-tw-logonscript.noarch        1.3-15.el4.sme                  installed
smeserver-wbl.noarch                   0.1.0-11.el4.sme                installed
sogo.i386                              1.3.14-1.el5                    installed
sogo-tool.i386                         1.3.14-1.el5                    installed
sope49-appserver.i386                  4.9-20120323_1664.el5.1         installed
sope49-cards.i386                      1.3.14-1.el5                    installed
sope49-core.i386                       4.9-20120323_1664.el5.1         installed
sope49-gdl1.i386                       4.9-20120323_1664.el5.1         installed
sope49-gdl1-contentstore.i386          1.3.14-1.el5                    installed
sope49-gdl1-mysql.i386                 4.9-20120323_1664.el5.1         installed
sope49-ldap.i386                       4.9-20120323_1664.el5.1         installed
sope49-mime.i386                       4.9-20120323_1664.el5.1         installed
sope49-sbjson.i386                     2.3.1-20120323_1664.el5.1       installed
sope49-xml.i386                        4.9-20120323_1664.el5.1         installed
sysstat.i386                           7.0.2-11.el5                    installed
webtatic-release.noarch                5-2                             installed

Didn't see a non-standard samba. What is to be done?

Thanks!

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: yum update 2013-01-17, samba conflict
« Reply #1 on: January 17, 2013, 04:31:52 PM »
please raise a bug and report here the reference for future readers, thank you

Offline macwunder

  • *
  • 17
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #2 on: January 17, 2013, 04:45:39 PM »

Offline macwunder

  • *
  • 17
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #3 on: January 17, 2013, 05:00:34 PM »

Offline geoff

  • ***
  • 61
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #4 on: January 17, 2013, 10:15:28 PM »
I'm seeing exactly the same as you have seen.

Offline pcowley

  • *
  • 14
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #5 on: January 18, 2013, 12:18:47 AM »
I'm also seeing the same issues too.  Glad to see a bug has been raised for it.

Cheers
Pete

Offline go_jesse

  • *
  • 2
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #6 on: January 18, 2013, 02:28:24 AM »
since the package is in updates testing you can work around the issue by doing (on command line)

$ sudo yum --enablerepo=smeupdates-testing install e-smith-samba

$ sudo yum upgrade
OR
upgrade via the web interface as normal.

then of course do (as suggested by e-smith)

$ sudo signal-event post-upgrade; sudo signal-event reboot


Offline geoff

  • ***
  • 61
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #7 on: January 18, 2013, 03:09:56 AM »
The web interface gives me the same result

Offline purvis

  • *****
  • 567
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #8 on: January 18, 2013, 05:06:36 AM »
If the Centos OS updates are not included in the update list from the server-manger panel under "Software Installer", the updates will not have a problem.
The updates from CentOS seem to be the problem.

Offline purvis

  • *****
  • 567
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #9 on: January 18, 2013, 07:38:01 AM »
For good or bad, i was able to overcome the yum update issues using go_jesse statements above.
Thanks Jesse

Here are my steps

From the server-manger panel, using a web browser to access  http://ipaddress/server-manager
Goto Software installer
Select Change software installer settings
Select all repositors except these two, CentOS-os and SME Server-updates testing
Click on the save button
Click on the Date and Time
Click on Software installer
Install any packages
If packages neeed to be installed then click on Reconfigure
The computer will reboot and reconfigure
Let the computer reboot and settle down
From a command prompt on the console or a console using a ssh program
Enter
top -l
If you do not see yum from the display after awhile, press ctrl-c to exit out of the top program

Enter
yum clean all
yum --enablerepo=smeupdates-testing install e-smith-samba

Now you should at this point get a Y to continue, enter the Y
After the updates enter
signal-event post-upgrade; sudo signal-event reboot

The computer will reboot and reconfigure.
Get back to the console of the server by whatever means you did before.
Enter
top -i

Wait to see no more yum processes running, then use ctrl-c to exit out of the top program
Enter
yum clean all
yum update

At this point you should no longer see any more updates to be installed.

Go back into the server-manager panel using a browser as you did before and into the Software installer.
Select select Change software installer settings
Select all repositors except SME Server-updates testing
Click on the save button
Click on the Date and Time
Click on Software installer
Install any packages
If packages neeed to be installed then click on Reconfigure
The computer will reboot and reconfigure
Let the computer reboot and settle down
At this point, the computer should have the updates installed

To check for more updates, get back to a console
Enter
yum clean all
yum update

You should see no more updates needed





« Last Edit: January 18, 2013, 08:15:46 AM by purvis »

Offline gbentley

  • *****
  • 482
  • +0/-0
  • Forum Lurker
    • Earth
Re: yum update 2013-01-17, samba conflict
« Reply #10 on: January 18, 2013, 08:14:56 AM »
The updates from CentOS seem to be the problem.

Should I just wait a little longer in that case or follow the instructions here?
"If you don't know what you want, you end up with a lot you don't."

Offline janet

  • *****
  • 4,812
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #11 on: January 18, 2013, 09:22:41 AM »
gbentley

You should read & follow the advice in the bug report(s).
From here
http://bugs.contribs.org/show_bug.cgi?id=7210

Comment 23 says
"> You can also do:
>
> yum --enablerepo smeupdates-testing upgrade
>
> This will give you all the ready to be released packages (and solves the
> upgrade issue along with it).

I tested this, it works.  However, some un-verified packages may have been picked-up in the process, to be confirmed. It may be prudent just waiting for a little while, hence giving us some time to check this issue.
Thanks."
Please search before asking, an answer may already exist.
The Search & other links to useful information are at top of Forum.

Offline apmuthu

  • *
  • 244
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #12 on: January 18, 2013, 01:19:35 PM »
One of the testing repo updates breaks ftp - wait 24-36 hours before a normal update does it.

Offline geoff

  • ***
  • 61
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #13 on: January 19, 2013, 04:39:21 AM »
After running Chris Burnat's mod at the top of the SME8.0 forum my server just updated perfectly, and a lot faster than usual.

Thanks to all involved for great work!!

Offline macwunder

  • *
  • 17
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #14 on: January 19, 2013, 05:12:50 AM »
Just received notification that the fixes have been released to the yum repositories. Should be good now.

Offline pcowley

  • *
  • 14
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #15 on: January 19, 2013, 11:20:13 AM »
I reran the software updates this morning and they all went through fine!

Problem is indeed fixed now.

A big thank you to our diligent developers!

Cheers
Pete

Offline genisys

  • *
  • 46
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #16 on: February 23, 2013, 11:26:08 AM »
Hello all -
I have tried all suggestions on this topic, including updating my mirrors per Chris's forum post and I still cannot get around the samba3x issue.

The Bug report (7210) seems to state that this should be fixed with a normal yum update, but it is definitely not, at least in my case. The bug also states not to use the "smeupdates-testing upgrade" part, because it will possibly add packages that are not functioning. I'm missing something.  Can anyone advise what the actual steps to fixing this are?

Thanks,
Nick

Offline purvis

  • *****
  • 567
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #17 on: February 23, 2013, 12:15:52 PM »
genisys
did you follow what i suggested.

Offline genisys

  • *
  • 46
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #18 on: February 23, 2013, 01:31:37 PM »
Hello -
Yes, I've tried to do what you've suggested. When I shut off Centos-os updates, I was able to complete the other updates and the server manager says that the system is up to date. Then I turn Centos-os updates back on, refresh and it shows all of the OS updates that are available (lots). I try to apply them and get the same samba3x error.

Nick

Offline purvis

  • *****
  • 567
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #19 on: February 23, 2013, 01:44:44 PM »
Nick, did you disable both centos selections or just one?
I disabled both centos. Did the update thru the manager panel. Then turned the 2 centos selections back on.

Offline genisys

  • *
  • 46
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #20 on: February 25, 2013, 03:33:27 PM »
Yes, in server-manager, I unselected:

     CentOS - os
     CentOS - updates

And selected ONLY:

     SME Server - extras

When I do this, the server says it's up to date. Of course when I turn the above back on, there are updates available and I can't apply them due to samba3x issue.

Offline Stefano

  • *
  • 10,894
  • +3/-0
Re: yum update 2013-01-17, samba conflict
« Reply #21 on: February 25, 2013, 03:35:14 PM »
please use bugzilla, thank you

Offline genisys

  • *
  • 46
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #22 on: February 25, 2013, 04:04:01 PM »
Hi Stefano,

I went ahead and created a new bug. I didn't do this previously, because they were marked FIXED, however I see now, that I should have.

http://bugs.contribs.org/show_bug.cgi?id=7402

Thanks,
Nick

Offline genisys

  • *
  • 46
  • +0/-0
Re: yum update 2013-01-17, samba conflict
« Reply #23 on: February 26, 2013, 03:21:30 PM »
My problem was resolved, http://bugs.contribs.org/show_bug.cgi?id=7402

I had to reset my yum configuration:

     mv /home/e-smith/db/yum_repositories /tmp
     /etc/e-smith/events/actions/initialize-default-databases
     expand-template /etc/yum.smerepos.d/sme-base.repo

Then just update the server via yum as usual.

Thanks for all the responses!

Nick