hi,
I had the same problem with 3.6.26 and got a patch from Patrick which solved the
problem:
regards
~Christoph
'patch max_open'
============
It was put into the code in order to track down problems with applications
that are closing all of the 'unused' file descriptors when they do
and execve( lpr ), or do not close file descriptors.
And it looks like we have a couple of culprits right here: ghostview and Acrobat
Reader.
This surfaced on a couple of systems when lpr got an 'out of file descriptor'
system level error... Needless to say, I was perturbed.
The 'Max_open()' code was put in to try and find out just how many file
descriptors were in use. I would use it to track the 'high water mark'
and the when I did an EXECVE I would close only the ones 'below'
the high water mark.
Here is the code:
void Max_open( int fd )
{
if( fd > 0 ){
if( fd > Max_fd+10 ){
FATAL(LOG_ERR) "Max_open: fd %d and old Max_fd %d", fd, Max_fd);
}
if( fd > Max_fd ) Max_fd = fd;
}
}
All you need to do is comment out the check...
void Max_open( int fd )
{
if( fd > 0 ){
#if 0
if( fd > Max_fd+10 ){
FATAL(LOG_ERR) "Max_open: fd %d and old Max_fd %d", fd, Max_fd);
}
#endif
if( fd > Max_fd ) Max_fd = fd;
}
}
But you might also send a flame to the ghostview and Acrobat folks...
Patrick Powell Astart Technologies,
[EMAIL PROTECTED] 9475 Chesapeake Drive, Suite D,
Network and System San Diego, CA 92123
Consulting 858-874-6543 FAX 858-279-8424
LPRng - Print Spooler (http://www.astart.com)
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
William Barnes schrieb:
> No, I wasn't getting those errors.
> Instead, I found this thanks to your suggestion what to look for:
> subserver pid 399 exit status 'JSUCC' at 2001-04-13-14:08:43.811 ## A=<NULL> num
> ber=0 process=393
> floor21: Max_open: fd 39 and old Max_fd 23 at 2001-04-13-14:09:03.851 ## A=<NULL
> > number=0 process=393
>
> It's working better, but when a super large job gets queued up or someone sends many
>jobs very quickly, it'll stall the queue every time...
> I appreciate any help.
>
> Thanks!
> --Bill
> *******************************************
> * Bill Barnes, CNA, MCP, A+
> * Library Network Administrator
> * Harvey A. Andruss Library
> * Bloomsburg University
> * AL 125
> * ph: 570-389-2813
> * fax: 570-389-3895
> * e-mail: [EMAIL PROTECTED]
> *******************************************
>
> >>> [EMAIL PROTECTED] 04/11/01 12:39PM >>>
>
> Check the logs to see if you have a gdbm error. If you do, the same happened
> to me. I was
> easy to fix... recompile without gdbm support.
>
> As Thomas Vogt pointed out...
>
> >Try reconfiguring and recompiling LPRng-3.7.4 with "configure
> --disable-gdbm ...".
>
> My error looked like this on the logs:
>
> In /var/spool/lpd/queue_name/status.queue_name
> >subserver pid 2245 exit status 'JSUCC' at 2001-03-30-14:42:42.314 ##
> A=<NULL> number=0 process=2047
>
> In /var/spool/lpd/queue_name/lpq.0
> >Status: consig1: Open_gdbm: cannot lock 'db.consig1' - Interrupted system
> call at 14:29:06.915
>
> Best Regards
>
> -----Original Message-----
> From: William Barnes [mailto:[EMAIL PROTECTED]]
> Sent: Miércoles, 11 de Abril de 2001 09:23 a.m.
> To: [EMAIL PROTECTED]
> Subject: LPRng: LPRng and Windows 2000
>
> Hello All,
> I've been using LPRng on a Red Hat 7.0 print server for about a year
> now, and it's worked fine. This was about 20 clients printing to 3
> printers.
>
> However, since it worked so good, I added more Windows 2000 machines to it,
> and I'm runing into something new:
> I have 50 workstations printing to two LPR queues on the LPRng printer,
> which forwards them to two HP 8000N laser printers. If one job comes into
> the queue, it processes it ok. If two come into the queue, it usually does
> ok. If someone sends in 5 jobs (because the clicked the print button 5
> times in a row), it prints the first one, says that it's "JSUCC" on that
> job, and stalls there. When it re-trys agin, it does the same thing: prints
> the first job in the queue, says that it's "JSUCC", and stalls on that one.
> If I go in and delete all the jobs, it works fine again.
>
> Some more information that may help us:
> Red Hat 7.0 with 2.2.16-22 Kernel
> LPRng-3.6.24 (the one RedHat put out with security fixes)
> I'm using the filter that came with RedHat 7.0, but I tried the latest IFHP
> from LPRng website and it does the same thing.
> Example of my Printcap file:
> floor21:\
> :sd=/var/spool/lpd/floor21:\
> :mx#0:\
> :sh:\
> :lpd_bounce=false:\
> :if=/var/spool/lpd/floor21/filter:\
> :af=/var/spool/lpd/floor21/acct:\
> :lp=/dev/null:
> #
> floor22:\
> :sd=/var/spool/lpd/floor22:\
> :mx#0:\
> :sh:\
> :lpd_bounce=false:\
> :if=/var/spool/lpd/floor22/filter:\
> :af=/var/spool/lpd/floor22/acct:\
> :lp=/dev/null:
>
> my .config from floor21 and floor22 directories are printing to port 9100 on
> the IP address.
>
> Thank you for any help you can give me.
>
> Thanks!
> --Bill
> *******************************************
> * Bill Barnes, CNA, MCP, A+
> * Library Network Administrator
> * Harvey A. Andruss Library
> * Bloomsburg University
> * AL 125
> * ph: 570-389-2813
> * fax: 570-389-3895
> * e-mail: [EMAIL PROTECTED]
> *******************************************
>
> ----------------------------------------------------------------------------
> -
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
>
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body. For the
> impatient,
> to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
> with: | example:
> subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems, send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> ----------------------------------------------------------------------------
> -
>
> -----------------------------------------------------------------------------
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
>
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body. For the impatient,
> to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
> with: | example:
> subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems, send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------
-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
