Mystery error from Send_job

Forum: Printers
Topic: Mystery error from Send_job
started by: rja

Posted by rja on Jan. 22 2007,00:25

I'\m trying to print to a remote printer using apsfilter with DSL-3.2.

Somehow, apsfilter can send a test page, but lp or lpr never sends anything.

I tried:

dsl@keyhole:~$ lp /opt/printcap
request id is dsl@keyhole+461
dsl@keyhole:~$ lpq
Printer: bro@keyhole 'PS;r=1200x1200;q=medium;c=mono;p=letter;m=auto' (dest raw@192.168.0.7)
Queue: no printable jobs in queue
Server: no server active
Status: job 'dsl@keyhole+461' error 'Mystery error from Send_job' at 18:14:17.958
Rank Owner/ID Class Job Files Size Time
error dsl@keyhole+461 A 461 ERROR: Mystery error from Send_job
no entries

The printer is a Brother HL5170DN.

[/home/dsl]# cat /opt/printcap
# APS1_BEGIN:printer1
# - don't delete start label for apsfilter printer1
# - no other printer defines between BEGIN and END LABEL
bro|PS;r=1200x1200;q=medium;c=mono;p=letter;m=auto:\
:lp=:\
:rm=192.168.0.7:\
:rp=raw:\
:if=/usr/etc/apsfilter/basedir/bin/apsfilter:\
:sd=/var/spool/lpd/bro:\
:lf=/var/spool/lpd/bro/log:\
:af=/var/spool/lpd/bro/acct:\
:mx#0:\
:sh:
# APS1_END - don't delete this

If I run "Printer Setup" again and use the "T" option, apsfilter sends a perfect
test page to the printer.

Stopping and starting "Printing/Lpd" from the control panel, or System>Printing/lpd>restart do not help

Posted by rja on Jan. 22 2007,01:10

My bad!

I had tried to setup dsl-3.2 using a samba printer first, and that failed, so I tried a remote lpd which also failed with the same "Mystery error from Send_job".

After rebooting with both dsl-3.0 and dsl-3.2, apsfilter worked fine with remote printing as long as I didn't try to use samba.

I probably have samba setup wrong on my Fedora Core 6 host, so I should not have reported this as a dsl 3.2 problem.

Sorry to bother everyone.

Posted by rja on Jan. 22 2007,01:49

Samba printing with apsfilter on dsl-3.2 was not the problem.

My fc6 host was using the wrong spool directory for samba.

Maybe this will help anyone else who see's this error message.