Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

issues with CUPS - printers keep loosing jobs

44 views
Skip to first unread message

lukaszmail

unread,
Mar 28, 2009, 1:32:08 AM3/28/09
to
Hello

We recently switched to active directory and our print server on linux
print server (running CUPS) seems to struggle with keeping up with all
the connections to its printers. A windows machine is connecting to
all those printers (about 20) and if I restart it or its spool server
service, the printers' status changes between:

"Printer not found on server, unable to connect"
"Opening"
"Ready"

and the printers go from ready to ..unable to connect back and forth.
Eventually this stabilises on the ready status and it seems to go fine
for sometime but with an increased volume of printing, the issue
returns. This in itself is not a problem, but what is happening is
that the some print jobs are simply lost (about 50%) without a trace
when printing from any of the printers on this server.

I should also mention that the PDC is in a different geographical
location than the linux and windows servers which are at a remote
location. There's currently no BDC at the remote site.


There's some errors in the samba logs on the linux server:


/var/log/samba/log.__ffff_10.10.1.7 <--------------- This is the
windows server connecting to all the printers on this linux server
/var/log/samba/log.__ffff_10.10.15.251 <--------- Another server also
using some of the printers
/var/log/samba/log.smbd
and some other logs...

report:
:
:
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
[2009/03/27 17:16:28, 0] printing/print_cups.c:cups_connect(68)
Unable to connect to CUPS server localhost:631 - Cannot assign
requested address
:
:

check the times. This seems to flood the server.


/var/log/samba/log.octane.old
reports:

___
[2009/03/27 17:38:43, 0] rpc_client/cli_pipe.c:rpc_api_pipe(789)
rpc_api_pipe: Remote machine OCTANE pipe \spoolss fnum 0x4000
returned critical error. Error was Write error: Success
[2009/03/27 17:38:43, 0] rpc_server/
srv_spoolss_nt.c:srv_spoolss_replycloseprinter(174)
srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code
0x0000003b].
[2009/03/27 17:38:43, 0] rpc_client/cli_pipe.c:rpc_api_pipe(789)
rpc_api_pipe: Remote machine OCTANE pipe \spoolss fnum 0x4000
returned critical error. Error was Write error: Success
[2009/03/27 17:38:43, 0] rpc_server/
srv_spoolss_nt.c:srv_spoolss_replycloseprinter(174)
srv_spoolss_replycloseprinter: reply_close_printer failed [DOS code
0x0000003b].
___
OCTANE is the windows XP box with all the printers from this server


/var/log/samba/log.wb-NE-AM
reports:
:
:
[2009/03/27 18:05:57, 1] libsmb/clikrb5.c:ads_krb5_mk_req(680)
ads_krb5_mk_req: krb5_get_credentials failed for CANDC01$@NE-AM
(Cannot resolve network address for KDC in requested realm)
[2009/03/27 18:05:57, 1] libsmb/
cliconnect.c:cli_session_setup_kerberos(626)
cli_session_setup_kerberos: spnego_gen_negTokenTarg failed: Cannot
resolve network address for KDC in requested realm
[2009/03/27 18:10:37, 1] libsmb/clikrb5.c:ads_krb5_mk_req(680)
ads_krb5_mk_req: krb5_get_credentials failed for CANDC01$@NE-AM
(Cannot resolve network address for KDC in requested realm)
[2009/03/27 18:10:37, 1] libsmb/
cliconnect.c:cli_session_setup_kerberos(626)
cli_session_setup_kerberos: spnego_gen_negTokenTarg failed: Cannot
resolve network address for KDC in requested realm
[2009/03/27 18:15:39, 1] libsmb/clientgen.c:cli_rpc_pipe_close(545)
cli_rpc_pipe_close: cli_close failed on pipe \NETLOGON, fnum 0x6 to
machine CANDC01.NE-AM.NE.grp. Error was SUCCESS - 0
:
:

/var/log/samba/log.wb-BUILTIN
reports:
:
:
[2009/03/26 15:57:36, 0] winbindd/
winbindd_dual.c:async_request_timeout_handler(182)
async_request_timeout_handler: child pid 2349 is not responding.
Closing connection to it.
[2009/03/26 15:57:36, 1] winbindd/winbindd_util.c:trustdom_recv(260)
Could not receive trustdoms
[2009/03/27 18:15:39, 0] winbindd/
winbindd_dual.c:async_request_timeout_handler(182)
async_request_timeout_handler: child pid 2333 is not responding.
Closing connection to it.
[2009/03/27 18:15:39, 1] winbindd/winbindd_util.c:trustdom_recv(260)
Could not receive trustdoms
:
:


/var/log/samba/log.nmbd
reports:
:
:
[2009/03/27 15:15:47, 0] nmbd/nmbd_namequery.c:query_name_response
(108)
query_name_response: Multiple (2) responses received for a query on
subnet 10.10.1.5 for name NE-AM<1d>.
This response was from IP 10.10.15.236, reporting an IP address of
10.10.15.236.
[2009/03/27 15:56:06, 0] nmbd/nmbd_namequery.c:query_name_response
(108)
query_name_response: Multiple (2) responses received for a query on
subnet 10.10.1.5 for name NE-AM<1d>.
This response was from IP 10.10.15.236, reporting an IP address of
10.10.15.236.
[2009/03/27 16:26:31, 0] nmbd/nmbd_namequery.c:query_name_response
(108)
query_name_response: Multiple (2) responses received for a query on
subnet 10.10.1.5 for name NE-AM<1d>.
This response was from IP 10.10.15.236, reporting an IP address of
10.10.15.236.
[2009/03/27 17:17:20, 0] nmbd/nmbd_namequery.c:query_name_response
(108)
query_name_response: Multiple (2) responses received for a query on
subnet 10.10.1.5 for name NE-AM<1d>.
This response was from IP 10.10.15.236, reporting an IP address of
10.10.15.236.
:
//LLLLLLLLLLLLLLLLLnot part of
logLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL
10.10.15.236 is a windows which tried to be the domain Master Browser.
I disabled the browser service on it.
//LLLLLLLLLLLLLLLLLnot part of
logLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL

and finally /var/log/user.log reports the following everythime the
server restarts:

Mar 27 18:10:41 vortex cupsd[1982]: *** WARNING *** The program
'cupsd' uses the Apple Bonjour compatibility layer of Avahi.
Mar 27 18:10:41 vortex cupsd[1982]: *** WARNING *** Please fix your
application to use the native API of Avahi!
Mar 27 18:10:41 vortex cupsd[1982]: *** WARNING *** For more
information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=cupsd>

//
LLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLL

here's our smb.conf:
_________________
[global]

workgroup = NE-AM
realm = NE-AM.NE.GRP
server string = %h server

template shell = /bin/false
template homedir = /home/%D/%U
idmap uid = 10000-20000
idmap gid = 10000-20000
enhanced browsing = no
winbind use default domain = yes
security = ADS
password server = 10.7.0.100
encrypt passwords = true
unix password sync = yes
printing = cups
printcap name = cups
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
domain master = no
local master = no
prefered master = no
os level = 2

[homes]
comment = Home Directories
browseable = no
writable = no
create mask = 0700
directory mask = 0700
[printers]
comment = All Printers
browseable = yes
path = /var/spool/samba
printable = yes
public = yes
writable = no
create mode = 0700
use client driver = yes
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = yes
public = yes
valid users = %S

Any Ideas? More info?

0 new messages