lp problem on Solaris 10

  • Follow


The system is an Ultra 10 running Solaris 10.
Occasionally the print system will start producing the message:

UX:lp: ERROR: No space to allocate temp files.
       TO FIX: Clean up disk, or try again later.

when attempt to print a file. lpsched appears to go into a loop, 
repeatedly adding the message "Failed to open a print service file (No 
such file or directory)." to /var/lp/logs/lpsched.

The root file system (which includes /var ) has 3 Gig free space and
/tmp has 2 Meg free space. The files to be printed are a few kb.

Running lpshut and lpsched fixes the problem temporarily.
lpsched writes " build info: 01/21/05:15:38:16" to
/var/lp/logs/lpsched when it starts.

Does anyone have any info on this problem ?
0
Reply Hugh 7/20/2005 5:45:52 PM

Hugh Coomes wrote:
> The system is an Ultra 10 running Solaris 10.
> Occasionally the print system will start producing the message:
> 
> UX:lp: ERROR: No space to allocate temp files.
>       TO FIX: Clean up disk, or try again later.
> 
> when attempt to print a file. lpsched appears to go into a loop, 
> repeatedly adding the message "Failed to open a print service file (No 
> such file or directory)." to /var/lp/logs/lpsched.
> 
> The root file system (which includes /var ) has 3 Gig free space and
> /tmp has 2 Meg free space. The files to be printed are a few kb.
> 
> Running lpshut and lpsched fixes the problem temporarily.
> lpsched writes " build info: 01/21/05:15:38:16" to
> /var/lp/logs/lpsched when it starts.
> 
> Does anyone have any info on this problem ?

I have no info but have suffered the same problem on a SB2500 with Sol 10. I wondered if it 
was the HP LP drivers I installed looks like it was not and is something else in Sol 10.

I also have a problem with the LP socket intermittently disconnecting (JetDirect) which 
means that it duplicates jobs as the server thinks it has failed.

John.
0
Reply John 7/21/2005 10:30:48 PM


1 Replies
499 Views

(page loaded in 0.035 seconds)

Similiar Articles:













7/23/2012 12:28:04 AM


Reply: