asked on

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

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.

Thanks,

Craig

ASKER CERTIFIED SOLUTION

wesly_chen

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Craig Sharp

ASKER

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.

wesly_chen

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...

Craig Sharp

ASKER

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.

Craig