Problems downgrading package (Samba)

vic-t · 2018-12-26 12:04:35

I ran into some serious issues with a Samba AD setup after upgrading to the current version 4.9.4 so I wanted to try to downgrade the package back to the last version I had running which is 4.7.4. Luckily, the package is still there in /var/cache/pacman/pkg so I was able to run pacman -U without issues.

Unfortunately, this wasn't entirely successful. Samba can't be started anymore as it complains that required libraries aren't there. Here is an extract from journalctl -xe.

samba[10745]: /usr/bin/samba: /usr/lib/samba/libndr-samba4.so: version `SAMBA_4.7.4' not found (required by /usr/bin/samba)

I thought that, maybe, pacman didn't dare to overwrite existing libraries but after checking the contents of the package file, I'm a bit confused: These files aren't even part of the package. Neither of the new one (4.9.4), nor of my old one (4.7.4.). And yet, when querying the file using pacman -Qo, pacman confirms that these files are owned by Samba (4.9.4, in my case). Reviewing the package contents here on the site confirm that these files should be part of the package but they really aren't.

Can someone help me better understand this? What would be the correct steps to properly downgrade Samba, including all libraries, and other dependencies?

seth · 2018-12-26 14:42:50

pacman -Qo /usr/lib/samba/libndr-samba4.so
/usr/lib/samba/libndr-samba4.so is owned by smbclient 4.9.4-1

Please notice that partial upgrades (or downgrades) are unsupported and I'd strongly suggest to rather address "some serious issues" with the current version, because you'll not be able to stay this package for an infinite time.

Trilby · 2018-12-26 15:06:35

vic-t wrote:

when querying the file using pacman -Qo, pacman confirms that these files are owned by Samba (4.9.4, in my case). Reviewing the package contents here on the site confirm that these files should be part of the package

Can you show your pacman output and the web link that confirms this?

Did you see the first or third bullet point in the big red "warning" box at the very top of the wiki page on downgrading?
https://wiki.archlinux.org/index.php/Do … g_packages

Last edited by Trilby (2018-12-26 15:07:54)

vic-t · 2018-12-26 15:46:11

Trilby wrote:

vic-t wrote:
when querying the file using pacman -Qo, pacman confirms that these files are owned by Samba (4.9.4, in my case). Reviewing the package contents here on the site confirm that these files should be part of the package
Can you show your pacman output and the web link that confirms this?

I believe Seth covered the pacman output, the web link is the following: https://www.archlinux.org/packages/extra/x86_64/samba/

Did you see the first or third bullet point in the big red "warning" box at the very top of the wiki page on downgrading?
https://wiki.archlinux.org/index.php/Do … g_packages

Yes, I did. Quite frankly, I'm not sure what "If the downgrading involve a soname change" means. And I'm also not sure if it is relevant. In my understanding, this isn't about external dependencies but about the package Samba itself. If I downgrade a package and the package owns libraries, shouldn't these libraries be replaced as well?

vic-t · 2018-12-26 15:49:55

seth wrote:

pacman -Qo /usr/lib/samba/libndr-samba4.so
/usr/lib/samba/libndr-samba4.so is owned by smbclient 4.9.4-1
Please notice that partial upgrades (or downgrades) are unsupported and I'd strongly suggest to rather address "some serious issues" with the current version, because you'll not be able to stay this package for an infinite time.

I did that, of course but during the last 4 days, this didn't get me anywhere. I downgraded as a very last resort. I understand it can't stay like this infinitely but it still should be possible - or shouldn't it?

In the meantime, I've set up a VM where I will use the Arch archive to downgrade the whole system, not just the package. I'd still be curious to know the answers to my questions, though.

seth · 2018-12-26 15:53:17

The answer to your question is that smbclient isn't samba. It's a dependency package.
Since it's also a dep for smbnetfs (and a truckload of other packages), you might want to downgrade that package as well.

Where's the thread w/ your actual samba issues?

vic-t · 2018-12-26 16:03:33

seth wrote:

The answer to your question is that smbclient isn't samba. It's a dependency package.
Since it's also a dep for smbnetfs (and a truckload of other packages), you might want to downgrade that package as well.
Where's the thread w/ your actual samba issues?

I'm not sure I understand. My issue is with the Samba AD DC server, not with smbclient. And per my understanding of the wiki entry, downgrading should take care of the dependencies Samba has.

The actual Samba issue I'm trying to solve with the help of the Samba list, I thought that's the best way to go. Unfortunately, we didn't yield any meaningful result so far. In a nutshell: My (Arch) server ran into a memory issue a few days ago, a hard reset was the only thing left to do. After this hard reset, there were DNS issues with Samba though I didn't notice that in time before I proceeded with pacman -Syu, updating Samba from v4.7.4. to 4.9.4. Looks like this made everything worse. So, my last resort is to downgrade Samba, restore from backup, and then try to upgrade again.

If you believe it makes sense to post the issues separately here in this forum, I'd be happy to do so, of course.

Trilby · 2018-12-26 16:03:53

vic-t wrote:

I believe Seth covered the pacman output, the web link is the following: https://www.archlinux.org/packages/extra/x86_64/samba/

Except that Seth's output and the webpage you just linked to directly refute both of your claims. libndr-samba4.so does not belong to the samba package. I was curious to dig into why on your system pacman was saying it does.

vic-t wrote:

And per my understanding of the wiki entry, downgrading should take care of the dependencies Samba has.

No, this is precisely what the first bullet in the red warning box is all about.

Last edited by Trilby (2018-12-26 16:05:16)

vic-t · 2018-12-26 16:06:48

Sorry about that, now I understand why you both speak about smbclient.. I guess I'm already too tired. I saw "4.9.4" and immediately jumped to the conclusion this is referring to Samba. Clearly, I need to downgrade smbclient, too.

seth · 2018-12-26 16:45:26

You *can* bring up this issue here whenever you feel like (please elaborate on the issue AND link the mailing list), though afaiu it's not a regression by the update but you already had DNS issues w/ the 4.7 version? (And I'm also unsure about the downgrade/restore/update process)

vic-t · 2018-12-27 11:04:26

Just fyi: I was able to solve the problem. After properly downgrading Samba and its dependencies (smbclient, libwbclient), I was able to restore /var/lib/samba from backup and start Samba without issues. I can now plan to upgrade Samba properly after the holidays.

loqs · 2018-12-27 11:56:15

https://lists.samba.org/archive/samba/2 … 20103.html

seth · 2018-12-27 13:29:52

W/o issues means even DNS works?
Otherwise did you ensure that local resolution of samdom.example.ch works? (check ping, dig, drill & nslookup, none should fail)

vic-t · 2018-12-27 15:48:09

Yes, everything works. I can query the DNS server properly (host command, but ping and nslookup work too), AD-LDAP works again, Kerberos/authentication works.. just the way it did before the upgrade. Journalctl is finally clean too, no errors whatsoever.

Slithery · 2018-12-27 15:57:35

Just for future reference the way that I'd handle a situation like this is to use the archive to roll all packages back to a specific date/time. At least this way you can guarantee that all of your packages/db's are in a consistent state before you start troubleshooting.

vic-t · 2018-12-27 16:29:25

Yes, I read about this possibility in detail and even tried it in a virtual machine. Successfully only after changing SigLevel to Never, wouldn't budge otherwise (maybe something for the wiki?). But frankly, especially since I was doing all the troubleshooting through SSH, I was worried I could end up with new issues that would make me have to drive to the server location during the holidays.

Arch Linux

#1 2018-12-26 12:04:35

Problems downgrading package (Samba)

#2 2018-12-26 14:42:50

Re: Problems downgrading package (Samba)

#3 2018-12-26 15:06:35

Re: Problems downgrading package (Samba)

#4 2018-12-26 15:46:11

Re: Problems downgrading package (Samba)

#5 2018-12-26 15:49:55

Re: Problems downgrading package (Samba)

#6 2018-12-26 15:53:17

Re: Problems downgrading package (Samba)

#7 2018-12-26 16:03:33

Re: Problems downgrading package (Samba)

#8 2018-12-26 16:03:53

Re: Problems downgrading package (Samba)

#9 2018-12-26 16:06:48

Re: Problems downgrading package (Samba)

#10 2018-12-26 16:45:26

Re: Problems downgrading package (Samba)

#11 2018-12-27 11:04:26

Re: Problems downgrading package (Samba)

#12 2018-12-27 11:56:15

Re: Problems downgrading package (Samba)

#13 2018-12-27 13:29:52

Re: Problems downgrading package (Samba)

#14 2018-12-27 15:48:09

Re: Problems downgrading package (Samba)

#15 2018-12-27 15:57:35

Re: Problems downgrading package (Samba)

#16 2018-12-27 16:29:25

Re: Problems downgrading package (Samba)

Board footer