samba - May 2006 - allocate_print_jobid: failed to allocate a print job for queue lbrmgt

We have recently migrated from a package called Totalnet to Samba to
replace our file and print services.  File services are working great.
>From time to time we get a call that printing stops working.
I have found a post stating that it may be a file space issue.  After
checking, our file systems have plenty of extra space in them and have
never filled up yet.

Our current fix for this is to erase the print queue's tdb file.
   tdbtool /var/locks/samba/printing/lbrmgt.tdb erase

Q1. What sort of side affect are we introducing by erasing the print
queue's tdb file?
Q2. What steps can I perform in order to diagnose or fix the issue
permanently?

Details:
Samba 3.0.20b
OS - AIX 5.1 ML7

Relivant smb.conf settings:
[global]
        printcap name = /etc/printcap
        printing = AIX
        printer admin = root
        load printers = Yes
        print command = lpr -r -h -P'%p' %s

[printers]
        comment = All Printers
        path = /var/spool/samba
        printable = Yes
        printer admin = root, staff
        browseable = Yes
        public = Yes
        writeable = Yes
        read only = Yes

[print$]
        comment = Printer Driver Download Area
        path = /etc/samba/Drivers
        browseable = Yes
        guest ok = Yes
        read only = Yes
        write list = root

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

Mineau, Kevin wrote:
>From time to time we get a call that printing stops working.
> 
> I have found a post stating that it may be a file space 
> issue.  After checking, our file systems have plenty of extra
> space in them and have never filled up yet.
> 
> Our current fix for this is to erase the print queue's tdb file.
>    tdbtool /var/locks/samba/printing/lbrmgt.tdb erase
> 
> Q1. What sort of side affect are we introducing by erasing the print
> queue's tdb file?
Not much unless you have jobs that take a really long
time to print.  This print queue tdb contains the Win32
attributes (document name, owner, etc...) for the unix
print job.
> Q2. What steps can I perform in order to diagnose or fix the issue
> permanently?
Just out of curiosity, how busy is your server ?  Active connections,
number of printers, etc...






cheers, jerry
====================================================================Samba       
------- http://www.samba.org
Centeris                         -----------  http://www.centeris.com
"What man is a man who does not make the world better?"      --Balian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFEW04BIR7qMdg1EfYRAnf7AKC6BKFzE8AGuv4BMgegseoNlR1aGACfUIzQ
ScJUyVdTC+Tpf1w60oUdKKQ=Kvld
-----END PGP SIGNATURE-----

Mineau, Kevin wrote:

 Over 100 locations, each has it's own local samba
 server with identical config. Each location has 5
 XP PC connections. Guess around 10 - 30 print
 requests from the PCs per day.  Some jobs could be from 
 Word or Excel.  Print jobs unlikely over 20 pages
 while most are less than 5.

Gerald (Jerry) Carter wrote:

What server OS and file systems ?

Mineau, Kevin wrote:

All locations are running AIX 5.1 Maintenance Level 7
All filesystems are jfs.

Update / resolution:

After additional investigation into our problem, we have occasionally
seen an entry like:

   wks069195 (<ipaddress>) connect to service lbrmgt initially as user
nobody (uid=-2, gid=-2) (pid 1015860)

We then opened up the permissions on /var/spool/samba/lbrmgt.  (chmod
777)
Since then this error condition has stopped.