Solaris 10 /etc/lp/filter.table corruption following lpsched hang

Posted on 2011-04-20
Medium Priority
Last Modified: 2012-05-11
I ran into an issue today where lpsched hung due to a DNS issue with printer names.  When I corrected the DNS issue, restarted the scheduler and tried to print to a local queue (remote printer), I received the following error:

dist431ptr: failed to commit job (32125-0): No filter available to convert job

The root cause was that the /etc/lp/filter.table file had become corrupt.  I copied the file from a sister server, restarted lpsched and the problem was resolved.

This is the second time this issue has occurred.  The first time was not due to DNS issues, but another issue.  The end result of the issue was that lpsched hung.  When the filter.table file was replaced, the issue was resolved.

I am looking for suggestions as to what might be the cause.

5.10 Generic_138888-03 sun4u sparc SUNW,Sun-Fire-V890.


Question by:Craig Sharp
  • 2
  • 2
LVL 38

Accepted Solution

wesly_chen earned 2000 total points
ID: 35451199
Check your system log at that time frame of DNS issue and looking for lp.

Based on the URL
----- quote --------
Solaris Print Manager automatically adds these filters to a print server.

Author Comment

by:Craig Sharp
ID: 35451228
Nothing was in the syslog.  The only thing we had to go on was that the printers were throwing the filter error shown above and we could not communicate.  The DNS was easy as these were all remote printers.  The filter.table issue was more elusive.
LVL 38

Expert Comment

ID: 35451281
As the quote from the URL:
Solaris Print Manager automatically adds these filters to a print server.

Does this give you some hints like "Solaris Print Manager" doing something automatically and it could mess up your filter table..... You  might want to check the print manager to see if you can disable automatically update or some sort of...

Author Comment

by:Craig Sharp
ID: 35452650
I see where you are going with this, but this is a system that remains static for months. We have other systems with identical print settle that do not exhibit this issue. This leads me to believe that there is something else happening. I will have a look at the print manager though and see if that may be doing something funny that was triggered by the dns issue. Thanks for you replies.


Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Attention: This article will no longer be maintained. If you have any questions, please feel free to mail me. jgh@FreeBSD.org Please see http://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-update-server/ for the updated article. It is avail…
FreeBSD on EC2 FreeBSD (https://www.freebsd.org) is a robust Unix-like operating system that has been around for many years. FreeBSD is available on Amazon EC2 through Amazon Machine Images (AMIs) provided by FreeBSD developer and security office…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
Suggested Courses

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question