From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [samba-4.14.5_1] [armv6l] smbd failing to start
Date: Fri, 10 Jun 2022 04:13:31 +0200 [thread overview]
Message-ID: <20220610021331.XOhx2Bm0jZN3ZQhBF6hD2WkM4wOwYIsJUAL2GqYWbh0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32079@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]
Closed issue by hk0O7 on void-packages repository
https://github.com/void-linux/void-packages/issues/32079
Description:
### System
* xuname: Void 5.4.83_1 armv6l Unknown uptodate rFF
* package: samba-4.14.5_1
### Expected behavior
Being able to start `smbd` with the default configuration.
### Actual behavior
It immediately ends with:
```
exit_daemon: daemon failed to start: Samba cannot setup ep pipe, error code 13
```
### Steps to reproduce the behavior
```
# xbps-install -Suy samba
# smbd -FS -d 10 --no-process-group
...
regdb_open: registry db opened. refcount reset (1)
make_internal_ncacn_conn: Create pipe requested winreg
Created internal pipe winreg
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
```
After this, two (forked?) `smbd` processes for the given command will remain, and thus trying to start it from runit with `sv start smbd` will end up filling up the system with `smbd -F -S -d1` processes.
This looks like the same issue that was mentioned by [wangp][1] and [Anachron][2] in #27565 for samba-4.13.2_2.
[1]: https://github.com/void-linux/void-packages/issues/27565#issuecomment-753282396
[2]: https://github.com/void-linux/void-packages/issues/27565#issuecomment-753361331
prev parent reply other threads:[~2022-06-10 2:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 1:19 [ISSUE] " hk0O7
2021-07-21 18:17 ` Anachron
2021-07-21 19:26 ` hk0O7
2021-07-21 20:11 ` Anachron
2021-08-02 17:20 ` mvf
2021-08-02 17:38 ` ahesford
2021-08-02 18:27 ` mvf
2021-08-09 2:51 ` fosslinux
2021-08-09 2:52 ` fosslinux
2021-08-09 2:53 ` fosslinux
2021-08-13 16:25 ` KeepBotting
2022-05-27 2:12 ` github-actions
2022-06-10 2:13 ` github-actions [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=20220610021331.XOhx2Bm0jZN3ZQhBF6hD2WkM4wOwYIsJUAL2GqYWbh0@z \
--to=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).