Network printing Printer Pauses /usr/libexec/cups/backend/lpd failed

Question

Level 1

0 points

Network printing Printer Pauses /usr/libexec/cups/backend/lpd failed

Morning,

I wonder if anyone has encountered the following problem?

NETWORK SET UP
We have a network of 8 macs & a Fuji Xerox c2255 printer all connected to a gigabit switch.
The Fuji Xerox has an fixed ip address 192.168.1.122 All devices have fixed ip address.

PROBLEM
Only one mac (Mac Pro) can print direct to the Fuji Xerox Printer. This Mac Pro is on 10.5.8. and it is sharing its printer connection with the rest of the studio. Oddily enough, the Appletalk function is turned on. When the appletalk function is turned off on the ethernet port, it can not longer directly print nor share the Fuji Xerox with the rest of the network

The remainder of the Macs are all on 10.6.4 or 10.6.3. When the printer is first installed on the an iMac client, it can print from text files, offices docs, from safari or firefox with out any problem. But when it attempts to print a pdf file (preview) or Indesign files then it pauses the printer. Within the printer queue, if attempt to restart the printer, the printer pauses. It remains in this state indefinitely. When looking at the CUPS logs via the console, the error is printer-state-message="/usr/libexec/cups/backend/lpd failed". This is the message displayed on all the clients that attempt to print directly (via LPD) to the Fuji Xerox. Once this error message is logged, the iMac can no longer print out text files nor word documents.

The following console log is typically of what all the 10.6.x clients are reporting,

D [15/Jul/2010:18:38:07 +1000] [Job 4] STATE: +connecting-to-device
D [15/Jul/2010:18:38:07 +1000] [Job 4] Looking up "192.168.1.122"...
D [15/Jul/2010:18:38:07 +1000] [Job 4] Connecting to 192.168.1.122:515 for printer
D [15/Jul/2010:18:38:07 +1000] [Job 4] Connecting to printer...
D [15/Jul/2010:18:38:07 +1000] [Job 4] STATE: -connecting-to-device
D [15/Jul/2010:18:38:07 +1000] [Job 4] Connected to printer...
D [15/Jul/2010:18:38:07 +1000] [Job 4] Connected to 192.168.1.122:515 (IPv4) (local port 1008)...
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.1 = 7500
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.2 = 1170
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.3 = 400
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.4 = 585
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.5 = 25000
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.6 = 18400
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.7 = 19600
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.8 = 19200
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.9 = 19600
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.10 = 200000
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.11 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.12 = 200000
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.13 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.14 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.15 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.16 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.17 = 200000
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.18 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.19 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.20 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.21 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] prtMarkerSuppliesLevel.1.22 = -3
D [15/Jul/2010:18:38:07 +1000] [Job 4] ATTR: marker-levels=50,75,25,50,100,46,49,48,49,100,-1,100,-1,-1,-1,-1,100,-1,-1,-1,- 1,-1
D [15/Jul/2010:18:38:07 +1000] [Job 4] lpd_command 02
D [15/Jul/2010:18:38:07 +1000] [Job 4] Sending command string (2 bytes)...
D [15/Jul/2010:18:38:07 +1000] [Job 4] Reading command status...
D [15/Jul/2010:18:38:07 +1000] [Job 4] lpd_command returning 1
D [15/Jul/2010:18:38:07 +1000] [Job 4] Backend returned status 1 (failed)
D [15/Jul/2010:18:38:07 +1000] [Job 4] Printer stopped due to backend errors; please consult the error_log file for details.
D [15/Jul/2010:18:38:07 +1000] [Job 4] End of messages
D [15/Jul/2010:18:38:07 +1000] [Job 4] printer-state=5(stopped)
D [15/Jul/2010:18:38:07 +1000] [Job 4] printer-state-message="/usr/libexec/cups/backend/lpd failed"
D [15/Jul/2010:18:38:07 +1000] [Job 4] printer-state-reasons=media-low-report,toner-low-report,paused

APPROACHED USED TO DATE
1. I have reset the Printer subsystem for all clients
2. I have reinstalled the latest PS drivers for this model of Fuji Xerox c2255. I have been on the phone with Fuji Xerox Technical support, FX DocuPrint C2255 v3017.104PS , and confirmed that this is the latest (and only) availible drivers for 10.5-10.6
3. I have had the Studio manger arrange to have the Fuji Xerox printer fully serviced and had the firmware updated to latest version.
4. Via Fuji Xerox Technical support, they advise I use the following settings for LDP printing for FX c2255,

Latest driver for 10.6 : 3017.104.ps
Setting to check :
Queue name : PS
Enable EtherTalk
LPD port : from auto to PS

Software version :
Controller plus PS role 1.100.21

5. I have (manually) deleted the all the FujiXerox drivers from /Library/Printers/ then repair permissions, then reinstalled the latest version of the Fuji Xerox driver from 10.6

WEIRDNESS

1. With the 10.6.x client, when the drivers are first installed, if I create a simply indesign file, I can print directly to the Fuji Xerox. If I then attempt to print out a previously created indesign document, it will pause the printer and the console (CUPS error_log) will display the above result. If I switch my printer to the Mac Pro 10.5.8 sharing the printer, the same document can print out via the hosted Fuji Xerox.
2. The Mac Pro 10.5.8 can print all documents directly to the Fuji Xerox regardless of the format of the document. It is also able to share the printer with the dept. This is the sole means of the dept being able to print out artwork.
3. Prior to the firmware upgrade I have tried an iMac printing/hosting the Fuji Xerox via direct USB cable. The same behaviour as above were experienced.
4. This model of Fuji Xerox only supports LDP or direct USB connection.
5. I have tried using the Bonjour address to configure the printer but the results are no better nor no worse. At one stage, all the iMacs were able to print sucessfully for a day but then 'stopped working' (as reported by the studio manager). They then switch back to the Mac Pro hosting the printer to continue working.
6. I discovered that if the drivers are installed and then a Permission repair carried out (via Disk Utility), it would change all the driver permissions for the files in the /Library/Printers/FujiXerox. When attempting to print (with the revised permissions), the 'print' button would not 'work'; the print dialog would present until Cancel was selected. It was almost like changing the permissions has lock out the functionality of being able to print. Manually moving the FujiXerox to Trash and reinstalling the drivers reverted the printer back to the above behaviour.
7. I discovered that when installing the printer, using LPD, it is better to allow the default settings. If I stuplated that the Fuji Xerox is a two bin set up, rather then a single bin set up, I can not print out from any application. If, I left settings as default, my assumption is that the apps can mange the printer features.

I've been working on this for a while now and this is driving me crazy. I would appreciate any suggestions. Has anyone come across this issue before ? Any ideas ?
Thank you,
Fred

Posted on Jul 15, 2010 8:45 PM

Reply

Answer 1

PAHU

Level 6

16,711 points

Jul 16, 2010 5:44 AM in response to Fred Mar

Hello Fred,

The issue certainly sounds interesting and not one that I've ever experienced but I would like to offer some help with determining the cause and possible solutions.

The inability of the SL Mac's to connect using LPD and the failing of the service is unusual for all Mac's to experience. There is a chance that the LPD service is not enabled on the printer, or an additional queue name is required, however I would not expect either of these to stop the LPD service. Still it would be worth checking the printer setup. According to Xerox support for the C2255, perform the following:

1. Press the [Menu] button on the control panel to display the menu screen.
2. Press the [Up] or [Down] button until 'Print Reports' is displayed.
3. Press the [Right] or [OK] button to select. 'Job History' is displayed.
4. Press the [Up] or [Down] button until 'Configuration' is displayed.
5. Press the [Right] or [OK] button to select. A print start confirmation screen appears.
6. Press the [OK] button to print.
7. Once the Configuration Page is printed, press the [Menu] button to return to the 'Ready to print' screen.

I am expecting that you would see a reference to the LPD service being enabled or disabled. You may also see in the report if the printer supports other IP protocols, such as RAW Port 9100. If it does, then you can try using this protocol, which is called HP Jetdirect-Socket on the Mac. (I know that you mentioned that the printer only supports LPD and USB, but I find it unusual that a device that supports IPv6 would not support this protocol)

Since the device supports Postscript you could also create a test queue using Generic Postscript. This may help to get past any filters or plugins that the Xerox driver uses and may be contributing to the symptom, especially since the printing seems to fail when a Postscript file or application is used. It would actually be good to see the cups error log immediately after this action is performed. Thinking more about this the LPD error could be a by-product of other Xerox files failing. Again, the Generic PS driver would help for testing purposes.

Well that is about all I can think of for now. Feel free to reply to discuss the matter further. In parting it is also interesting to read that Xerox support suggested to enable EtherTalk. They must not be aware that AppleTalk has been dropped from Mac OS X 10.6.

Pahu

Reply

Answer 2

Fred Mar Author

Level 1

0 points

Jul 16, 2010 4:47 PM in response to PAHU

Hi Pahu,

Thanks for your reply. I noticed that you have replied to a number of other postings as well - you're a good sort !! Your knowledge and contribution to this forum is much appreciated and very welcome.

Yes, this is a curly problem. I've actually been trying to resolve it for several months. Interesting the c2255 is not stated as being supported under Apple's Fuji drivers release for SN. The driver has to be downloaded directly from Fuji Xerox. The following is from the c2255 Config page,

Communication Settings
Ethernet Rated Speed
Connection Type Auto
MAC Address "08:00:37.8C:76.0C"

TCP/IP
IP Mode IPv4 Mode

IPv4
IP Address Resolution STATIC
IP Address "192.168.1.122"
Subnet Mask "255.255.255.0"
Gateway Address "192.168.1.1"
IP Filter Disabled
Status Ready

WINS
DHCP Address Resolution Disabled
Primary WINS Server Address “”
Secondary WINS Server Address “”

DNS
Domain Name “”

IPv4
DHCP Address Resolution Disabled
Preferred DNS Server “”
Alternate DNS Server 1 “”
Alternate DNS Server 2 “”
Dynamic DNS Registration Disabled

SSL / TLS
HTTP - SSL 1 TLS Communication Disabled
LDAP - SSL ' TLS Communication Disabled

IPSec
IPSec Communication Disabled

IEEE 802. lx
]EEE802.lx Disabled

SNMP
Port Status Enabled
Transport Protocol UDP
SNMP Version v1 / v2c

Internet Services
Port Status Enabled
Port Number 80
Maximum Number of Sessions 5
Connection Time-Out 30 seconds

SOAP Enabled
Port Status Port Number 80
Maximum Number of Sessions 3
Connection Time-Out 30 seconds

USB-1 (2.0)
Port Status Enabled
Print Mode ‘Postscript 3’
PJL Enabled
Adobe Communication Protocol Standard
Auto Eject Time 30 seconds

USB-2 (2.0) Port Status Enabled
Print Mode Auto
PJL Enabled
Adobe Communication Protocol Standard
Auto Eject Time 30 seconds

NetWare Port Status Disabled

LPD
Port Status Enabled
Print Mode ‘Postscript 3’
PJL Enabled
TBCP Filter Disabled
Port Number 515
Maximum Number of Sessions 5
Connection Time-Out 16 Seconds

SMB
Port Status Enabled
Prim Mode Auto
PJL Enabled
Transport Protocol TCP/IP. NetBEUI
TBCP Filler Disabled
Workgroup "WORKGROUP"
Host Name "AP-8C760C"
Auto Master Mode Off
Password Encryption On
Maximum Number of Sessions 5
Unicode Support Disabled
Administrator Name "ADMIN"

EtherTalk
Port Status Enabled
Print Mode PostScript 3'
PJL Enabled
Printer Name "DocuPrint C2255”
Zone Name “*”

IPP
Port Slatus Disabled

Port 9100
Port Slatus Enabled
Print Mode Auto
PJL Enabled
Pon Number 9100
TBCP Filter Disabled
End of Job Timeout 60 Seconds

WSD
Port Number 80
Data Receive Time-Out 30 Seconds
Maximum TTL 1
Maximum Number of Subscribers 50
Notification Delivery Time-Out 8 Seconds
Print Service
Port Status Enabled
Print Mode Auto
PJL Enabled
TBCP Filter Disabled

UPnP
Discovery
Port Status Enabled
Port Number 80

SSDP
Valid Advertising Period 180 Minutes
Maximum TTL 1

Bonjour
Port Status Enabled
Printer Name "DocuPrint C2255

What is interesting is that this problem occurs with all the 10.6.x macs. There is a Mac Pro that has been upgrade to 10.6; an iMac that has had a complete rebuild with 10.6; two iMacs that have been upgraded from 10.5.x and two new iMacs that came preinstalled with 10.6.2. None of these Macs can direct connect to the Fuji Xerox c2255. Only the 10.5.8 Mac can direct connect to the FX c2255 and can host (or share) the FX c2255 printer to the rest of the network.

One of the bizarra aspects is that the all the Macs can print text files, offices docs, web pages, etc, etc directly to the Fuji Xerox c2255 without any problem. BUT try to print a pdf file from preview or from Indesign and it resorts back to the status described earlier. Oddily enough, if I create a simple pdf in Indesign (circle, squares, a paragraph of text), I can print out the file using Indesign, directly to the printer. If I import one of the previously created documents, the printer reverts to the status described earlier. HOWEVER, if I take the same document and print via the Mac Pro 10.5.8 hosting/sharing the printer, the document will print without any problem. What the... ??!?!?!
I thought it might be a firmware problem but following the onsite service of the printer, I think I can rule that out.

Can you see anything that I might be missing ???
Thank you,
Fred

Reply

Answer 3

PAHU

Level 6

16,711 points

Jul 17, 2010 4:56 PM in response to Fred Mar

Thank you for the additional information Fred. The config page shows that Port 9100 is enabled so as I said before I would be inclined to create another print queue, this time using IP > HP Jetdirect-Socket for the protocol and possible even using Generic Postscript for the printer model. It would be interesting to see then if the PDF or InDesign files encounter the same problem.

With regards to the bizarre symptom, it is actual not unusual to encounter the symptom you have. With regards to InDesign, I have seen a similar crashing issue you mention with files that have been sent to us. The same application using files created locally are fine, but some files created elsewhere will not print. In one case the application was looking for a Helios server for a high resolution version of an image contained within the file. In another case a font conflict was causing the spooler to pause. In both cases we used Enfocus PitStop to learn more about the document creation, an expensive but invaluable tool for problem solving.

Without PitStop you could select to print and check the Graphics tab within the ID print dialog. Compare the Images and Fonts menus with a file that does print correctly. Also go to the OPI menu and ensure that image replacement is not being used. You should also check the Transparency Flattener menu and try a different preset. The last thing is the Summary menu in the print dialog. If you save this for the ID file that prints and then for one that causes problems, this can make things a lot easier to compare.

Reply

Answer 4

Jul 18, 2010 8:55 AM in response to Fred Mar

I too had this problem after the 10.6.4 update sharing a brother printer that worked flawlessly prior to the update - I solved it after trying many different combinations of types of printers and drivers by *+reseting the printing system on both machines+* on the client *choosing LPD printing, typing in the IP address of the host (print server) along with the full name of the Queue, selecting Generic Laser printer as the driver.*

*THE HOST MACHINE THINKS PRINTER SHARING IS OFF, +but it's NOT+* the client will print without the busy message!

Reply

Answer 5

Fred Mar Author

Level 1

0 points

Jul 20, 2010 6:40 PM in response to themachead

Hello,

Thank you for your ideas, Pahu and themachead.

Pahu, your comment 'With regards to the bizarre symptom, it is actual not unusual to encounter the symptom you have. ' was very helpful. It got me thinking that there may be more then one component affecting this situation. Via a process of elimination, I am thinking that it may be something to do with the way that the indesign documents are created, in particular how and where the eps images are located and how they are being access across the LAN. During my latest tests, the following error appeared, "This document may contain binary EPS files, which can cause the print job to fail.", which lead to this Adobe Tech Note, http://kb2.adobe.com/cps/401/kb401179.html. Note in particular the 'ADDITIONAL INFORMATION' of the the Tech Note.

With this in mind, I carried out some tests and can confirm that if I create a pdf file from an Indesign document, I can print the document via Acrobat or Preview direct to the Fuji Xerox printer. Yet if I try to print the same Indesign document direct from Indesign, then the printer pauses and resorts to the behaviour described earlier. The next time I am onsite, I will try to print the 'created pdf' file direct from Indesign and see what happens.

These test indicated two possible areas of contention - 1. Settings on the Fuji Xerox 2. Indesign document structure

For anyone else following this thread, have a look at this link from Adobe, http://kb2.adobe.com/cps/499/cpsid_49998.html

I will return to this thread once I have more results and will close the thread when we have a solution. For now, if anyone else has any other solutions, please feel free to contribute.
Thank you,
Fred

Reply

Answer 6

Fred Mar Author

Level 1

0 points

Aug 5, 2010 10:41 PM in response to Fred Mar

So, I have a solution to the problem; it is not a complete solution but it is a working solution which will allow the department to keep working for the interim.

I believe our problem relates to how Indesign handles or processes certain types or format of data within an Indesign document (or the format of the Indesign document itself). If, Indesign outputs the data as ASCII, or binary, or whatever and the printer is unable to interpreted the output properly then the print job will fail. This may due to one of many factors (the format of the Indesign document, the embedded data within the document or the capabilities of the printer itself) or a combination of factors. In our particular case, I believe it is to do with a combination of factors. I understand that Indesign (by default) will output data in a binary format. There is a very good document by Adobe that explains what happens with the processing of data by indesign at this link, http://kb2.adobe.com/cps/401/kb401179.html

In our particular case, I discovered that the Fuji Xerox c2255 did not appear to support binary printing in the Adobe Protocol via the LPD (ethernet) port. However, the printer DOES support binary printing in the Adobe Protocol via the USB ports. When tested - with the c2255 connected via USB cable rather then ethernet - it was very satisfying to be able to successful print directly to the c2255 printer from any pdf or postscript app (Adobe Indesign / Preview).

For now, the printer is connected to a mac mini via usb cable and the mac mini acting is acting as a print server. All the dept Macs can print to the Fuji Xerox from whatever application they choose (Mail, Safari, Firefox, Word, Excel, Entourage, Photoshop, etc) including Adobe Indesign CS4.

I suspect that we will need to carry out further investigation looking at the format of the depts' Indesign documents. I have been advised that mid last year, the Indesign documents were batch processed from an older format to a newer format. It is conceivable that during the conversion process something was missing or not prepared correctly. This will require further investigation.

Thank you, everyone, for your input, in particular PAHU and themachead.

Reply