The problem is due to some in-house code that is lowercasing the host name when it
sends the receive data file command. Explains why only machines with uppercase host
names are affected.
Sorry for the noise!
-----Original Message-----
From: Forrest Babcock
Sent: Tuesday, April 30, 2002 4:42 PM
To: '[EMAIL PROTECTED]'
Subject: RE: LPRng: missing data file errors
FYI - I have narrowed the problem down to a case lookup. Notice the lowercase d in
the machine name d6807 when the casekey_line is added. However, when the casekey is
searched for, the key contains and uppercase D in the machine name.
I will keep looking to try and determine where the values that are added and the keys
that are searched for are coming from. It may very well be something from our code.
Thx.
2002-04-30-16:09:48.502 ldap03 [23561] RECV lprngt5: Add_casekey_line_list:
'dfA701d6807 /local/spool/lpd/lp...', sep ' =#@', sort 1
...
2002-04-30-16:09:48.602 ldap03 [23561] RECV lprngt5: Find_str_value: key
'otransfername', value 'dfA701D6807'
2002-04-30-16:09:48.602 ldap03 [23561] RECV lprngt5: Find_first_casekey: enumerating
line_list
2002-04-30-16:09:48.602 ldap03 [23561] RECV lprngt5: Find_first_casekey: line_list[0]
== dfA701d6807=/local/spool/lpd/lprngt5
/temp00OnYRCp
2002-04-30-16:09:48.602 ldap03 [23561] RECV lprngt5: Find_first_casekey: count 1, key
'dfA701D6807', sep ' =#@'
2002-04-30-16:09:48.602 ldap03 [23561] RECV lprngt5: Find_first_casekey: cmp -1, top
-1, mid 0, bot 0
2002-04-30-16:09:48.602 ldap03 [23561] RECV lprngt5: Find_first_casekey: cmp -1, mid
0, key 'dfA701D6807', count 1
2002-04-30-16:09:48.602 ldap03 [23561] RECV lprngt5: Find_casekey_str_value: key
'dfA701D6807', value '<NULL>'
2002-04-30-16:09:48.602 ldap03 [23561] RECV lprngt5: setstatus: msg 'lprngt5:
Check_for_missing files: missing data file 'dfA
701D6807''
-----Original Message-----
From: Forrest Babcock
Sent: Tuesday, April 30, 2002 10:33 AM
To: '[EMAIL PROTECTED]'
Subject: LPRng: missing data file errors
Patrick / List,
Running LPRng 3.8.10 I am having some trouble with missing data file errors.
I see that this has been addressed in the past (3.8.8) and my symptoms are very
similar, only happens on some machines.
We have a very diverse setup here with jobs coming from mainframes, Unix, windows and
Linux. We also interface LPRng with our previous lpd server (we are looking to
replace it with LPRng) and some pre-existing tools. In the problem mentioned above we
are losing some jobs forwarded from one of our older lpd servers to LPRng, but this
only happens coming from our Mainframe and select Windows machines. So, I am not
positive that this is an LPRng problem but, since the symptoms are similar I would
like to get and idea of where in the code the problem was previously and/or what the
general scenario for loosing the data file was. This may help me isolate the cause of
the problem.
On another note, with the printing setup we have and the existence of tools that we
did not wish to replace, LPRng has been an excellent option for us to move to our
print servers to Linux. Very configurable / flexible, the ability to preprocess
control files, etc. all of this has made it possible and fairly easy for us to get new
servers integrated in a relatively short period of time. Thanks!
Thanks for any help / insight you can provide.
Forrest Babcock
-----------------------------------------------------------------------------
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.
-----------------------------------------------------------------------------
