Topic: Yum/rpm samba problem

[elmarconi]

Based on this thread/bug ID 3762 I installed samba-3.0.28-1.el4.sme.1. as per smeupdates-testing.

Though less frequent I still experience the read/write errors, especially with Jet-DB apps running on the shares...

I've noticed in the above mentioned bugreport that in the meantime 3.0.28-0.el4.9 was released to smeos/base.

Is there any elegant way of replacing the installed 3.0.28-1.el4.sme.1 with the 3.0.28-0.el4.9, or should I first yum remove it and the yum install it again?

rpm --force will break things I've heard.

[David Harper]

This was fixed in 7.4. If you upgrade to 7.4 you should be fine.

[elmarconi]

This was fixed in 7.4. If you upgrade to 7.4 you should be fine.

Code: [Select]

[root@smeserver ~]# rpm -q smeserver-release samba
smeserver-release-7.4-1.el4.sme
samba-3.0.28-1.el4.sme.1
I think it is by design.
samba-3.0.28-1.el4.sme.1. > 3.0.28-0.el4.9

Or am I missing something?

[cactus]

Based on this thread/bug ID 3762 I installed samba-3.0.28-1.el4.sme.1. as per smeupdates-testing.

Then please report in the bugtracker, please keep all relevant information in one channel in stead of scattering it here as well.

[elmarconi]

cactus, thanks for stepping in!

The reason I mentioned this here is that I am not sure whether this is a bug or behaviour by design. I believe it is by design that yum does not update application version u.v.x with application version u.v.w (x > w). If it is by design, I see no ground to raise a bug!

The bug is closed, and I want to apply the solution, install the samba version in repo smeos and/or base.

I could rephrase the question to:

I want to replace application u.v.x (from repo sme-testing) with application version u.v.w (x > w) repo smeos/base.
How to do this with yum? Should I first yum remove it and then yum install it again?

[cactus]

cactus, thanks for stepping in!

The reason I mentioned this here is that I am not sure whether this is a bug or behaviour by design. I believe it is by design that yum does not update application version u.v.x with application version u.v.w (x > w). If it is by design, I see no ground to raise a bug!

A failed to get your point... I do now.

I want to replace application u.v.x (from repo sme-testing) with application version u.v.w (x > w) repo smeos/base.
How to do this with yum? Should I first yum remove it and then yum install it again?

Downgrading, as that is what you are willing to do AFAIK, can be done but not with yum remove as this will remove a lot more packages. Your best bet is to see what was installed at the time you updates from smeupdates-testing (yum.log) and remove them with rpm -e, after that install them again with yum.

[elmarconi]

Code: [Select]

[root@smeserver7 ~]# grep "3.0.28-1.el4.sme.1" /var/log/yum/yum.log
Sep 12 21:51:45 Updated: samba-common.i386 3.0.28-1.el4.sme.1
Sep 12 21:51:48 Updated: samba-client.i386 3.0.28-1.el4.sme.1
Sep 12 21:51:57 Updated: samba.i386 3.0.28-1.el4.sme.1
I need this system not to go fubar today.
rpm -e will not go unless I add e-smith-samba to the list of packages.

Grmph, one more reason to convert to virtual machines with snapshot options...

[elmarconi]

Hold breath, jump in:

Code: [Select]

[root@smeserver7 ~]# service smb stop
[root@smeserver7 ~]# rpm -ev --nodeps samba samba-client samba-common
[root@smeserver7 ~]# yum install samba samba-client
[root@smeserver7 ~]# expand-template /etc/samba/smb.conf
[root@smeserver7 ~]# service smb start
[root@smeserver7 ~]# rpm -q samba samba-common samba-client
samba-3.0.28-0.el4.9
samba-common-3.0.28-0.el4.9
samba-client-3.0.28-0.el4.9

So far, so good...

[Stefano]

Code: [Select]

[root@smeserver7 ~]# cp /etc/samba/smb.conf.rpmsave /etc/samba/smb.conf
[root@smeserver7 ~]# cp /etc/pam.d/samba.rpmsave /etc/pam.d/samba


since smb.conf and pam.d/samba (IIRC) are expanded from templates , I think that these 2 lines are not necessary, but you should do instead

Code: [Select]

signal-event post-upgrade
signal-event reboot

my 2c

Stefano

[elmarconi]

Agree, fixed it ...

Edit: Actually I did not do the signal-event post-upgrade & signal-event reboot, as I only did the expand-template /etc/samba/smb.conf.

After service smb start load of errors:
ERROR: smbd is already running. File /var/run/smbd.pid exists and process id 21700 is running.

It seemed as some user left his machine on, incl. a connection to the server. Killed all remaining smbd processes, then service smb start went well...

[elmarconi]

I'm afraid this has not had the desired effect:

Code: [Select]

[size=1]
Mar 24 07:54:10 smeserver smbd[17122]:   read_data: read failure for 4 bytes to client 192.168.xx.185. Error = Connection reset by peer
Mar 24 08:45:45 smeserver smbd[24785]:   read_data: read failure for 4 bytes to client 192.168.xx.181. Error = Connection reset by peer
Mar 24 08:55:01 smeserver smbd[18418]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 08:55:01 smeserver smbd[18418]:   write_data: write failure in writing to client 192.168.xx.179. Error Broken pipe
Mar 24 09:14:33 smeserver smbd[24405]:   read_data: read failure for 4 bytes to client 192.168.xx.83. Error = No route to host
Mar 24 09:48:42 smeserver smbd[13340]:   read_data: read failure for 4 bytes to client 192.168.xx.174. Error = Connection reset by peer
Mar 24 09:48:42 smeserver smbd[13340]:   write_data: write failure in writing to client 192.168.xx.174. Error Broken pipe
Mar 24 09:48:42 smeserver smbd[1599]:   read_data: read failure for 4 bytes to client 192.168.xx.174. Error = Connection reset by peer
Mar 24 09:57:20 smeserver smbd[26147]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 09:57:20 smeserver smbd[26147]:   write_data: write failure in writing to client 192.168.xx.179. Error Broken pipe
Mar 24 11:04:46 smeserver smbd[2834]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:04:46 smeserver smbd[2834]:   write_data: write failure in writing to client 192.168.xx.179. Error Broken pipe
Mar 24 11:49:58 smeserver smbd[13129]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:49:58 smeserver smbd[13129]:   write_data: write failure in writing to client 192.168.xx.179. Error Broken pipe
Mar 24 11:50:00 smeserver smbd[19919]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:50:00 smeserver smbd[19919]:   write_data: write failure in writing to client 192.168.xx.179. Error Broken pipe
Mar 24 11:50:00 smeserver smbd[19926]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:50:01 smeserver smbd[19955]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:50:03 smeserver smbd[19958]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:50:03 smeserver smbd[19967]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:50:26 smeserver smbd[19970]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:56:33 smeserver smbd[20011]:   read_data: read failure for 4 bytes to client 192.168.xx.179. Error = Connection reset by peer
Mar 24 11:56:33 smeserver smbd[20011]:   write_data: write failure in writing to client 192.168.xx.179. Error Broken pipe
[/size]

I am now searching in another direction as this seems to affects most recently purchased desktops,
fitted with Marvell Yukon 88E8075 PCI-E Gb NIC's.

[elmarconi]

Follow-up: Well, after searching high and low I today started by systematicly disabling all advanced features on the settings tab of this Marvell Yukon 88E8075 PCI-E Gb NIC.

I have done some preliminairy testing and before i could easily reproduce the mentioned behavoir, now afterwards it seems that this has gone.

If time permits will try to switch back on all advanced options one by one and see where this goes.