From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: samba: update to 4.13.4
Date: Wed, 10 Feb 2021 03:44:12 +0100 [thread overview]
Message-ID: <20210210024412.h4r9RIxJXUTgDZiF7THOWYPDrGzak14ZAoGGzYFuQbU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28527@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2018 bytes --]
There's a closed pull request on the void-packages repository
samba: update to 4.13.4
https://github.com/void-linux/void-packages/pull/28527
Description:
Relatively minor update, but I'd appreciate a bit of testing, especially from @Anachron and @wangp who had some issues on `armv7l` or `aarch64`.
There is a caveat: I tried building this update while running the `smbd` and `nmbd` services from the current `samba-4.13.3_1` package. The resulting 4.13.4_1 package produced a broken `smbd` which died on startup with the error
```
svcctl_init_winreg: Could not open SYSTEM\CurrentControlSet\Services - NT_STATUS_INVALID_HANDLE
regdb_close: decrementing refcount (1->0)
dcesrv_init_ep_server: Failed to init endpoint server 'svcctl': NT_STATUS_UNSUCCESSFUL
dcesrv_init: Failed to init DCE/RPC endpoint servers: NT_STATUS_UNSUCCESSFUL
main: Failed to setup RPC server: NT_STATUS_UNSUCCESSFUL
exit_daemon: daemon failed to start: Samba cannot setup ep pipe, error code 13
```
Code 13 looks like `EACCES`, but this is a [hard-coded number](https://gitlab.com/samba-team/samba/-/blob/master/source3/smbd/server.c#L2104) that is independent of the actual reason for failure.
After removing `samba`, `smbclient` and `samba-libs` (which also required removing `cifs-utils` and `vlc` on my system) and rebuilding the package, `smbd` worked as expected. I tried a third rebuild with `samba`, `smbclient` and `samba-libs` installed but the services not active. This also seemed to produce a working package.
It seems that the build process allows the host configuration to leak through some how, and when the old services are running, something causes `smbd` to break. If you have similar troubles, I recommend first stopping any `nmbd` and `smbd` and rebuilding; if that still fails, try removing `samba-libs` and any dependants.
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
prev parent reply other threads:[~2021-02-10 2:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 17:06 [PR PATCH] Samba ahesford
2021-02-05 18:48 ` [PR PATCH] [Updated] samba: update to 4.13.4 ahesford
2021-02-05 21:02 ` Anachron
2021-02-10 2:44 ` ahesford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210210024412.h4r9RIxJXUTgDZiF7THOWYPDrGzak14ZAoGGzYFuQbU@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).