Your message dated Tue, 19 Jun 2018 10:34:48 +0200
with message-id 
<CAFX5sbx1sumA+Sd9RG=gvo8kit7fbs6e_23bqwz8cqofnke...@mail.gmail.com>
and subject line netbios name checked
has caused the Debian Bug report #816301,
regarding samba 2:4.3.3 refuses to start when security = share (or another 
config error)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
816301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816301
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:4.3.3+dfsg-2+b1
Severity: important

Today, when upgrading from 2:4.1.17+dfsg-4 to 2:4.3.3+dfsg-2+b1, I found
that samba, winbind and libpam-winbind were not configured.  It looked
like a circular dependency, so I tried to force configuration:

|tucano:~# dpkg --force-depends --configure --pending
|Setting up samba (2:4.3.3+dfsg-2+b1) ...
|Job for smbd.service failed because the control process exited with error 
code. See "systemctl status smbd.service" and "journalctl -xe" for details.
|invoke-rc.d: initscript smbd, action "start" failed.
|dpkg: error processing package samba (--configure):
| subprocess installed post-installation script returned error exit status 1
|dpkg: winbind: dependency problems, but configuring anyway as you requested:
| winbind depends on samba (= 2:4.3.3+dfsg-2+b1); however:
|  Package samba is not configured yet.
|
|Setting up winbind (2:4.3.3+dfsg-2+b1) ...
|Job for winbind.service failed because the control process exited with error 
code. See "systemctl status winbind.service" and "journalctl -xe" for details.
|invoke-rc.d: initscript winbind, action "start" failed.
|dpkg: error processing package winbind (--configure):
| subprocess installed post-installation script returned error exit status 1
|dpkg: libpam-winbind:amd64: dependency problems, but configuring anyway as you 
requested:
| libpam-winbind:amd64 depends on winbind (= 2:4.3.3+dfsg-2+b1); however:
|  Package winbind is not configured yet.
|
|Setting up libpam-winbind:amd64 (2:4.3.3+dfsg-2+b1) ...
|debconf: unable to initialize frontend: Dialog
|debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell 
buffer, or without a controlling terminal.)
|debconf: falling back to frontend: Readline
|Processing triggers for libc-bin (2.21-9) ...
|Errors were encountered while processing:
| samba
| winbind

As you sse, it worked for libpam-winbind, but not for winbind and samba.  Here 
is some more info:

|tucano:~# systemctl status winbind.service
|● winbind.service - LSB: start Winbind daemon
|   Loaded: loaded (/etc/init.d/winbind; bad; vendor preset: enabled)
|   Active: failed (Result: exit-code) since Mon 2016-02-29 13:52:22 CET; 19min 
ago
|     Docs: man:systemd-sysv-generator(8)
|
|Feb 29 13:52:22 tucano.isti.cnr.it systemd[1]: Starting LSB: start Winbind 
daemon...
|Feb 29 13:52:22 tucano.isti.cnr.it winbind[13309]: Starting the Winbind 
daemon: winbind failed!
|Feb 29 13:52:22 tucano.isti.cnr.it systemd[1]: winbind.service: Control 
process exited, code=exited status=1
|Feb 29 13:52:22 tucano.isti.cnr.it systemd[1]: Failed to start LSB: start 
Winbind daemon.
|Feb 29 13:52:22 tucano.isti.cnr.it systemd[1]: winbind.service: Unit entered 
failed state.
|Feb 29 13:52:22 tucano.isti.cnr.it systemd[1]: winbind.service: Failed with 
result 'exit-code'.

|tucano:~# journalctl -xe
|-- The start-up result is done.
|Feb 29 14:12:06 tucano.isti.cnr.it systemd[1]: Starting LSB: start Samba 
SMB/CIFS daemon (smbd)...
|-- Subject: Unit smbd.service has begun start-up
|-- Defined-By: systemd
|-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
|--
|-- Unit smbd.service has begun starting up.
|Feb 29 14:12:06 tucano.isti.cnr.it smbd[20294]: Starting SMB/CIFS daemon: smbd 
failed!
|Feb 29 14:12:06 tucano.isti.cnr.it systemd[1]: smbd.service: Control process 
exited, code=exited status=1
|Feb 29 14:12:06 tucano.isti.cnr.it systemd[1]: Failed to start LSB: start 
Samba SMB/CIFS daemon (smbd).
|-- Subject: Unit smbd.service has failed
|-- Defined-By: systemd
|-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
|--
|-- Unit smbd.service has failed.
|--
|-- The result is failed.
|Feb 29 14:12:06 tucano.isti.cnr.it systemd[1]: smbd.service: Unit entered 
failed state.
|Feb 29 14:12:06 tucano.isti.cnr.it systemd[1]: smbd.service: Failed with 
result 'exit-code'.
|Feb 29 14:12:06 tucano.isti.cnr.it polkitd(authority=local)[2419]: 
Unregistered Authentication Agent for unix-process:20288:1lines 1799-1821/1821 
(END)q

Now I am stuck...


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (101, 
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages samba depends on:
ii  adduser           3.113+nmu3
ii  dpkg              1.18.4
ii  libbsd0           0.8.2-1
ii  libc6             2.21-9
ii  libcap2           1:2.24-12
ii  libldb1           2:1.1.26-1
ii  libpam-modules    1.1.8-3.2
ii  libpam-runtime    1.1.8-3.2
ii  libpopt0          1.16-10
ii  libpython2.7      2.7.11-4
ii  libtalloc2        2.1.5-1
ii  libtdb1           1.3.8-1
ii  libtevent0        0.9.26-3
ii  libwbclient0      2:4.3.3+dfsg-2+b1
ii  lsb-base          9.20160110
ii  procps            2:3.3.11-3
ii  python            2.7.11-1
ii  python-dnspython  1.12.0-1
ii  python-samba      2:4.3.3+dfsg-2+b1
pn  python2.7:any     <none>
ii  samba-common      2:4.3.3+dfsg-2
ii  samba-common-bin  2:4.3.3+dfsg-2+b1
ii  samba-libs        2:4.3.3+dfsg-2+b1
ii  tdb-tools         1.3.8-1
ii  update-inetd      4.43

Versions of packages samba recommends:
ii  attr                1:2.4.47-2
ii  logrotate           3.8.7-2
ii  samba-dsdb-modules  2:4.3.3+dfsg-2+b1
ii  samba-vfs-modules   2:4.3.3+dfsg-2+b1

Versions of packages samba suggests:
pn  bind9          <none>
pn  bind9utils     <none>
pn  ctdb           <none>
pn  ldb-tools      <none>
ii  ntp            1:4.2.8p4+dfsg-3+b1
pn  smbldap-tools  <none>
ih  winbind        2:4.3.3+dfsg-2+b1

-- Configuration Files:
/etc/logrotate.d/samba changed:
/var/log/samba/log.smbd {
        weekly
        missingok
        rotate 7
        postrotate
                /etc/init.d/smbd reload > /dev/null
        endscript
        compress
        notifempty
}
/var/log/samba/log.nmbd {
        weekly
        missingok
        rotate 7
        postrotate
                [ ! -f /var/run/samba/nmbd.pid ] || kill -HUP `cat 
/var/run/samba/nmbd.pid`
                find /var/log/samba -mtime +50 -delete
        endscript
        compress
        notifempty
}


-- debconf information:
  samba-common/title:
  samba/generate_smbpasswd: false
  samba/run_mode: daemons

--- End Message ---
--- Begin Message ---
Version: 2:4.8.1+dfsg-1

This was fixed with #816301 which introduced regressions fixed in
2:4.8.2+dfsg-2 (#900908)

Regards
-- 
Mathieu

--- End Message ---

Reply via email to