From: wangp <wangp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Samba aborts on Raspberry Pi 3B
Date: Thu, 31 Dec 2020 01:01:47 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27565@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2613 bytes --]
New issue by wangp on void-packages repository
https://github.com/void-linux/void-packages/issues/27565
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.4.68_1 armv7l Unknown notuptodate rdFFF
(Raspberry Pi 3B)
* package:
samba-4.13.2_3
### Expected behavior
smbd starts normally.
### Actual behavior
smbd aborts at startup, saying it could not open secrets db. Has anybody else seen something similar on Raspberry Pi or ARM?
Log output:
```
2020-12-30T23:36:05.51797 daemon.notice: Dec 31 10:36:05 smbd: smbd version 4.13.2 started.
2020-12-30T23:36:05.51825 daemon.notice: Dec 31 10:36:05 smbd: Copyright Andrew Tridgell and the Samba Team 1992-2020
2020-12-30T23:36:05.58031 daemon.notice: Dec 31 10:36:05 smbd: ===============================================================
2020-12-30T23:36:05.58073 daemon.notice: Dec 31 10:36:05 smbd: INTERNAL ERROR: could not open secrets db in pid 22239 (4.13.2)
2020-12-30T23:36:05.58092 daemon.notice: Dec 31 10:36:05 smbd: If you are running a recent Samba version, and if you think this problem is not yet fixed in the latest versions, please consider reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
2020-12-30T23:36:05.58118 daemon.notice: Dec 31 10:36:05 smbd: ===============================================================
2020-12-30T23:36:05.58130 daemon.notice: Dec 31 10:36:05 smbd: PANIC (pid 22239): could not open secrets db in 4.13.2
2020-12-30T23:36:05.58146 daemon.notice: Dec 31 10:36:05 smbd: BACKTRACE: 0 stack frames:
```
testparm output:
```
# testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
bind interfaces only = Yes
disable spoolss = Yes
dns proxy = No
interfaces = eth0
load printers = No
log file = /var/log/samba/%m.log
logging = syslog
map to guest = Bad Password
max log size = 50
printcap name = /dev/null
server role = standalone server
server string = Samba Server
show add printer wizard = No
idmap config * : backend = tdb
hosts allow = 192.168.1. 127.
printing = bsd
...share definitions...
```
Downgrading back to samba-3.6.25_14.armv7l.xbps works okay.
### Steps to reproduce the behavior
1. install samba package
2. set up /etc/samba/smb.conf
3. start the smbd service
next reply other threads:[~2020-12-31 0:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 0:01 wangp [this message]
2020-12-31 3:56 ` ahesford
2020-12-31 5:39 ` ericonr
2020-12-31 14:10 ` Anachron
2020-12-31 14:11 ` Anachron
2020-12-31 15:56 ` ahesford
2020-12-31 17:18 ` hortimech
2020-12-31 17:44 ` ahesford
2021-01-01 7:54 ` wangp
2021-01-01 7:57 ` wangp
2021-01-01 13:53 ` Anachron
2021-01-01 13:58 ` ahesford
2021-01-01 14:03 ` hortimech
2021-01-01 14:15 ` Anachron
2021-01-01 14:27 ` ahesford
2021-01-01 18:30 ` Anachron
2021-01-01 18:40 ` hortimech
2021-01-02 0:28 ` wangp
2021-01-02 0:41 ` ericonr
2021-01-02 0:42 ` ericonr
2021-01-02 11:12 ` andry-dev
2021-01-02 13:12 ` wangp
2021-01-02 19:06 ` ahesford
2021-01-05 3:42 ` [ISSUE] [CLOSED] " ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27565@inbox.vuxu.org \
--to=wangp@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).