Print queue disables itself when the first job is submitted

[Karen Birkelbach]

I have created a printer using the lpadmin command for a remote printer without any problems, but when I send the first print job to the spooler, the queue automatically disables itself. The command I used to create the queue is:

# lpadmin -pPR0688 -v/dev/null -mrmodel -ocmrcmodel -osmrsmodel -ob3 -ormdepc1 -orpPR0688 -v/dev/null

# lpstat -pPR0688
printer PR0688 is idle. enabled since Jan 19 13:31
fence priority : 0

(the scheduler is stopped before and started after the command)

I then submit a job with:

# lp -dPR0688 /etc/motd
request id is PR0688-0 (1 file)

When I check the queue:

# lpstat -pPR0688
printer PR0688 disabled since Jan 19 13:32 -
error 1 returned
fence priority : 0

Any suggestions as to where to look next would be very helpful.

[A. Clay Stephenson]

When an interface file (model script) returns a non-zero exit code, as does yours, the normal behavior for the local lp susbsystem is to disable the print queue. The most common reasons for a remote printer to fail are: 1) incorrect hostname of the remote host 2) incorrect queue (printer) name on the remote host 3) bad hostname resolution on either end 4) no lpd listener running on the remote host. None of these are really checked when you setup a remote print queue.