samba - Feb 2004 - printjob stays in windows queue after transfer failure

Hi Jerry et al,

I'm using the 3.0.1 release in 'ADS' mode with ~450 print queues and
~150
users (getting migrated right now, will be ~3.000 in the end). In general
everything works fine apart from some smaller driver configuration
problems, the usual stuff. Though I see a lot of errors in the log files
and it seems that sometimes the print job transfer fails (get 'zero
nothing to print' messages in '/var/adm/messages'). Now in these
cases the
job naturally never shows up in the UNIX queue but it stays in the windows
queue window forever. As far as I understand it doesn't get wiped out in
'../var/locks/printing/<printer>.tdb'. Of course I could write a
small
wrapper for the lpr command to check that circumstance and delete the
<printer>.tdb file ;-)

Hope this makes any sense to you, I think the job transfer problem is
related to this messages in log.smbd:

[2004/02/03 09:39:46, 0] lib/util.c:smb_panic(1400)
  PANIC: internal error
[2004/02/03 09:39:53, 0] smbd/connection.c:register_message_flags(220)
  register_message_flags: tdb_fetch failed
[2004/02/03 09:40:32, 0] rpc_client/cli_pipe.c:rpc_api_pipe(424)
  cli_pipe: return critical error. Error was Write error: Resource
temporarily unavailable
[2004/02/03 09:41:15, 0] lib/fault.c:fault_report(36)
  ==============================================================[2004/02/03
09:41:15, 0] lib/fault.c:fault_report(37)
  INTERNAL ERROR: Signal 11 in pid 9213 (3.0.1)
  Please read the appendix Bugs of the Samba HOWTO collection
[2004/02/03 09:41:15, 0] lib/fault.c:fault_report(39)
  ==============================================================[2004/02/03
09:41:16, 0] lib/util.c:smb_panic(1400)
  PANIC: internal error
[2004/02/03 09:41:23, 0] smbd/connection.c:register_message_flags(220)
  register_message_flags: tdb_fetch failed


best regards & thanks for any help
	~christoph


-- 
/*   Christoph Beyer     |   Office: Building 2b / 23     *\
 *   DESY                |    Phone: 040-8998-2317        *
 *   - IT -              |      Fax: 040-8998-4060        *
\*   22603 Hamburg       |     http://www.desy.de         */

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

christoph.beyer@desy.de wrote:
| Hi Jerry et al,
|
| I'm using the 3.0.1 release in 'ADS' mode with ~450 print queues
and ~150
| users (getting migrated right now, will be ~3.000 in the end). In general
| everything works fine apart from some smaller driver configuration
| problems, the usual stuff. Though I see a lot of errors in the log files
| and it seems that sometimes the print job transfer fails (get 'zero
| nothing to print' messages in '/var/adm/messages'). Now in these
cases the
| job naturally never shows up in the UNIX queue but it stays in the windows
| queue window forever. As far as I understand it doesn't get wiped out in
| '../var/locks/printing/<printer>.tdb'. Of course I could write a
small
| wrapper for the lpr command to check that circumstance and delete the
| <printer>.tdb file ;-)

Its more than that probably.  My guess is that a change
notify is not getting sent back to the client with the correct
jobid.  (which could be explained by one of the buig fixes
in 3.0.2 or by the fact that the smbd crash and the change
notify handle has become invalid).

|   ==============================================================| [2004/02/03
09:41:15, 0] lib/fault.c:fault_report(37)
|   INTERNAL ERROR: Signal 11 in pid 9213 (3.0.1)
|   Please read the appendix Bugs of the Samba HOWTO collection
| [2004/02/03 09:41:15, 0] lib/fault.c:fault_report(39)
|   ==============================================================
This could be bug #660 (which was fixed post 3.0.1.



- --
cheers, jerry
- ----------------------------------------------------------------------
Hewlett-Packard            ------------------------- http://www.hp.com
SAMBA Team                 ---------------------- http://www.samba.org
GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
"If we're adding to the noise, turn off this song" --Switchfoot
(2003)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAH64GIR7qMdg1EfYRArUoAKC3MFokWrLC9OY9A71NTBydsUHOmQCdExCx
l81jMeQZaCHPPnLugFF4qkY=En9K
-----END PGP SIGNATURE-----