Your message dated Tue, 22 Oct 2013 16:38:42 -0500
with message-id <[email protected]>
and subject line Perhaps a separate command?
has caused the Debian Bug report #385254,
regarding samba start should test tdb integrity
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.)
--
385254: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=385254
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 3.0.23b-2
Severity: important
After a power failure, printing failed, then worked after some fiddling
then failed again until I found the following posting by Jeremy
Allison:
http://lists.samba.org/archive/samba/2005-November/113292.html
Samba in Debian needs a better way to handle corrupt .tdb files - after
deleting the file, printing worked again, but I'd tried several other
things first and wasted a lot of time in the process. Could the startup
process check the integrity of the .tdb files and quarantine corrupt
files?
Just about anything would be better than something that leaves printing
in an inconsistent state.
Arthur.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Versions of packages samba depends on:
ii debconf [debconf-2.0] 1.5.3 Debian configuration management sy
ii libacl1 2.2.41-1 Access control list shared library
ii libattr1 2.4.32-1 Extended attribute shared library
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libcomerr2 1.39-1 common error description library
ii libcupsys2 1.2.2-2 Common UNIX Printing System(tm) -
ii libgnutls13 1.4.2-1 the GNU TLS library - runtime libr
ii libkrb53 1.4.4~beta1-1 MIT Kerberos runtime libraries
ii libldap2 2.1.30-13+b1 OpenLDAP libraries
ii libpam-modules 0.79-3.2 Pluggable Authentication Modules f
ii libpam-runtime 0.79-3.2 Runtime support for the PAM librar
ii libpam0g 0.79-3.2 Pluggable Authentication Modules l
ii libpopt0 1.10-3 lib for parsing cmdline parameters
ii logrotate 3.7.1-3 Log rotation utility
ii lsb-base 3.1-15 Linux Standard Base 3.1 init scrip
ii netbase 4.26 Basic TCP/IP networking system
ii procps 1:3.2.7-2 /proc file system utilities
ii samba-common 3.0.23b-2 Samba common files used by both th
ii zlib1g 1:1.2.3-13 compression library - runtime
Versions of packages samba recommends:
pn smbldap-tools <none> (no description available)
-- debconf information:
samba/nmbd_from_inetd:
samba/log_files_moved:
samba/tdbsam: false
* samba/generate_smbpasswd: false
* samba/run_mode: daemons
--- End Message ---
--- Begin Message ---
It makes sense to have a command (upstream?) that can verify the
databases and print out any errors or try to resolve them.
'samba-tool dbcheck' already does some of this, but just for the AD side
of things.
Doing this kind of thing during startup can add a fair amount of
slowdown. It's akin to always running 'fsck' during boot.
And even if tdb itself is happy, some of the contents may
still have been corrupted. You'd have to do deeper inspection to find
those.
signature.asc
Description: Digital signature
--- End Message ---
