Very Computer

by **Phil Schum** » Thu, 20 Aug 1998 04:00:00

all of a sudden -
our laser print Qs are down, and will not come back up -
these have been running fine for months ??
they have HP jetdirect or IBM cards.
we start them - and they go down with these msgs -
I tried it on all 4 of them -
the other external print servers are running fine -
any ideas - ?
Phil -
---

Printer Queue - dsp5si - Restarted

Message from root on dsprs6000 (UNKNOWN) [Wed Aug 19 15:50:03 CDT 1998] ...
Message from queueing system:

Backend: /usr/lib/lpd/pio/etc/piojetd dsplp48 9100 /home/phil/.profile
Backend Exit Value: EXITFATAL (0100)
Job Submit Time: Aug 19 15:03:33 1998, Current Time: Aug 19 15:50:03 1998
Use local problem reporting procedures.
<EOT>

by **Dennis Matze** » Fri, 21 Aug 1998 04:00:00

Did someone bring up a BOOTP server and change the ip addresses of the
JetDirects?

> all of a sudden -
> our laser print Qs are down, and will not come back up -
> these have been running fine for months ??
> they have HP jetdirect or IBM cards.
> we start them - and they go down with these msgs -
> I tried it on all 4 of them -
> the other external print servers are running fine -
> any ideas - ?
> Phil -
> ---

> Printer Queue - dsp5si - Restarted

> Message from root on dsprs6000 (UNKNOWN) [Wed Aug 19 15:50:03 CDT 1998] ...
> Message from queueing system:

> Backend: /usr/lib/lpd/pio/etc/piojetd dsplp48 9100 /home/phil/.profile
> Backend Exit Value: EXITFATAL (0100)
> Job Submit Time: Aug 19 15:03:33 1998, Current Time: Aug 19 15:50:03 1998
> Use local problem reporting procedures.
> <EOT>

--
"Every day is a good one - some are just better than others"

Dennis Matzen, CAD Systems Manager
City of Medford, Fire Department
Ph (541) 774-2323 Fax (514) 774-2514

Web: http://www.ci.medford.or.us/fire/fire.html

by **Phil Schum** » Fri, 21 Aug 1998 04:00:00

I can ping and telnet into the devices -
all with their static/assigned addresses -
but good point :)
also....
another bit of info -
I put the protocol analyzer online and watched it -
I could see the ping and telnet -
but NOTHING during the LP attempt -

in other words -
it's not a touch and printer barf situation,
nothing at all comes out of the 6000 -
it must be failing due to some type of corruption
in one of the printer/jetdirect files on the 6000.
Phil -

says...

>Did someone bring up a BOOTP server and change the ip addresses of the
>JetDirects?

>> all of a sudden -
>> our laser print Qs are down, and will not come back up -
>> these have been running fine for months ??
>> they have HP jetdirect or IBM cards.
>> we start them - and they go down with these msgs -
>> I tried it on all 4 of them -
>> the other external print servers are running fine -
>> any ideas - ?
>> Phil -
>> ---

>> Printer Queue - dsp5si - Restarted

>> Message from root on dsprs6000 (UNKNOWN) [Wed Aug 19 15:50:03 CDT 1998] ...
>> Message from queueing system:

>> Backend: /usr/lib/lpd/pio/etc/piojetd dsplp48 9100 /home/phil/.profile
>> Backend Exit Value: EXITFATAL (0100)
>> Job Submit Time: Aug 19 15:03:33 1998, Current Time: Aug 19 15:50:03 1998
>> Use local problem reporting procedures.
>> <EOT>

>--
>"Every day is a good one - some are just better than others"

>Dennis Matzen, CAD Systems Manager
>City of Medford, Fire Department
>Ph (541) 774-2323 Fax (514) 774-2514

>Web: http://www.ci.medford.or.us/fire/fire.html

by **Phil Schum** » Fri, 21 Aug 1998 04:00:00

the addresses are still as I assigned them -
but -
if someone did bring up a BOOTP server -
how could I find it on our network?
Phil
--

says...

Quote:
>Did someone bring up a BOOTP server and change the ip addresses of the
>JetDirects?

by **Dennis Matze** » Fri, 21 Aug 1998 04:00:00

You said you have a network analyzer. Set it you to capture only BOOTP
traffic and restart one of your JetDirects. See if it sends a BOOTP request
and then if someone answers it. I think you can also print out networks stats
from the jetdirect amd it will show how the address was set (control panel or
bootp) and if it was bootp the address of the server.

> the addresses are still as I assigned them -
> but -
> if someone did bring up a BOOTP server -
> how could I find it on our network?
> Phil
> --

> says...

> >Did someone bring up a BOOTP server and change the ip addresses of the
> >JetDirects?

--
"Every day is a good one - some are just better than others"

Dennis Matzen, CAD Systems Manager
City of Medford, Fire Department
Ph (541) 774-2323 Fax (514) 774-2514

Web: http://www.ci.medford.or.us/fire/fire.html

by **Phil Schum** » Fri, 21 Aug 1998 04:00:00

this was a good one -
the problem was the /etc/hosts file - the PERMISSIONS -
the FTP'd copy created them with just RW-R--
and it really needed RW-RW-R--

it would work fine under root, but not from a user -
that was our clue -

before we FTP'd the file over to the 6000, we renamed the old -

since it did not have a file to 'replace',
the new file had some default permissions vs the 'old' ones inherited.
when we changed the permissions, everything was then ok.
wow - what a detective story :))

Phil -

>I can ping and telnet into the devices -
>all with their static/assigned addresses -
> but good point :)
>also....
>another bit of info -
>I put the protocol analyzer online and watched it -
>I could see the ping and telnet -
>but NOTHING during the LP attempt -

>in other words -
>it's not a touch and printer barf situation,
>nothing at all comes out of the 6000 -
>it must be failing due to some type of corruption
>in one of the printer/jetdirect files on the 6000.
>Phil -

>says...

>>Did someone bring up a BOOTP server and change the ip addresses of the
>>JetDirects?

>>> all of a sudden -
>>> our laser print Qs are down, and will not come back up -
>>> these have been running fine for months ??
>>> they have HP jetdirect or IBM cards.
>>> we start them - and they go down with these msgs -
>>> I tried it on all 4 of them -
>>> the other external print servers are running fine -
>>> any ideas - ?
>>> Phil -
>>> ---

>>> Printer Queue - dsp5si - Restarted

>>> Message from root on dsprs6000 (UNKNOWN) [Wed Aug 19 15:50:03 CDT 1998] ...
>>> Message from queueing system:

>>> Backend: /usr/lib/lpd/pio/etc/piojetd dsplp48 9100 /home/phil/.profile
>>> Backend Exit Value: EXITFATAL (0100)
>>> Job Submit Time: Aug 19 15:03:33 1998, Current Time: Aug 19 15:50:03
1998
>>> Use local problem reporting procedures.
>>> <EOT>

>>--
>>"Every day is a good one - some are just better than others"

>>Dennis Matzen, CAD Systems Manager
>>City of Medford, Fire Department
>>Ph (541) 774-2323 Fax (514) 774-2514

>>Web: http://www.ci.medford.or.us/fire/fire.html

by **LAIX Software Consultin** » Fri, 21 Aug 1998 04:00:00

Try this:

cat file | /usr/lib/lpd/pio/etc/piohpnpf -x PRINTERHOSTNAME

Or, you can examine the print queue backend script piojetd and perhaps put
some stuff at the top to see if its being invoked at all, like:

#!/bin/ksh
set -x
exec 2> /tmp/error_log
....rest of script...

So you can capture any errors coming from things called by piojetd. If I had to
hazard a guess if nothing ever goes across the network, either piojetd or piohpnpf
isn't there, or it's name resolution.

You could also try our TCPrint backend program: http://www.flash.net/~laixsoft
as it has some helpful diagnostic logging abilities.

Best regards,
Paul Laymon

> I can ping and telnet into the devices -
> all with their static/assigned addresses -
> but good point :)
> also....
> another bit of info -
> I put the protocol analyzer online and watched it -
> I could see the ping and telnet -
> but NOTHING during the LP attempt -

> in other words -
> it's not a touch and printer barf situation,
> nothing at all comes out of the 6000 -
> it must be failing due to some type of corruption
> in one of the printer/jetdirect files on the 6000.
> Phil -

> says...

> >Did someone bring up a BOOTP server and change the ip addresses of the
> >JetDirects?

> >> all of a sudden -
> >> our laser print Qs are down, and will not come back up -
> >> these have been running fine for months ??
> >> they have HP jetdirect or IBM cards.
> >> we start them - and they go down with these msgs -
> >> I tried it on all 4 of them -
> >> the other external print servers are running fine -
> >> any ideas - ?
> >> Phil -
> >> ---

> >> Printer Queue - dsp5si - Restarted

> >> Message from root on dsprs6000 (UNKNOWN) [Wed Aug 19 15:50:03 CDT 1998] ...
> >> Message from queueing system:

> >> Backend: /usr/lib/lpd/pio/etc/piojetd dsplp48 9100 /home/phil/.profile
> >> Backend Exit Value: EXITFATAL (0100)
> >> Job Submit Time: Aug 19 15:03:33 1998, Current Time: Aug 19 15:50:03 1998
> >> Use local problem reporting procedures.
> >> <EOT>

> >--
> >"Every day is a good one - some are just better than others"

> >Dennis Matzen, CAD Systems Manager
> >City of Medford, Fire Department
> >Ph (541) 774-2323 Fax (514) 774-2514

> >Web: http://www.ci.medford.or.us/fire/fire.html

by **LAIX Software Consultin** » Fri, 21 Aug 1998 04:00:00

Phil,

Actually, the sticky (setuid) bit on a shell script doesn't work except in OLD
AIX releases.

Regards,
Paul

> I just dialed in and checked the dir of the files -
> the other part of the problem was the permissions
> of the backend programs - along with Ping and Telnet -
> I covered this in another msg about 'sticky bits'

> anyway - if the permissions are 'r-x' you get your own permissions,
> if they are 'r-s' then you have a 'sticky bit'
> and get the permissions of the 'owner' -
> with our /etc/hosts file not granted open 'read' access (in error)
> then only 'root' users could print to the laser - BUT WHY ??
> well - the 'rembak' backend has 'sticky bit' and 'root'
> so the dot matrix printers all worked ok - as root users -
> however - the 'piojetd' backend has 'x' bit
> therefore you are on your own permissions - and it would fail -
> had the 'piojetd' had the sticky bit,
> or the 'rembak' NOT had the sticky bit,
> it would have been even more interesting...none or all would have worked -
> Phil -

> >this was a good one -
> >the problem was the /etc/hosts file - the PERMISSIONS -
> >the FTP'd copy created them with just RW-R--
> >and it really needed RW-RW-R--

> >it would work fine under root, but not from a user -
> >that was our clue -

> >before we FTP'd the file over to the 6000, we renamed the old -

> >since it did not have a file to 'replace',
> >the new file had some default permissions vs the 'old' ones inherited.
> >when we changed the permissions, everything was then ok.
> >wow - what a detective story :))

> >Phil -

> >...

> >>I can ping and telnet into the devices -
> >>all with their static/assigned addresses -
> >> but good point :)
> >>also....
> >>another bit of info -
> >>I put the protocol analyzer online and watched it -
> >>I could see the ping and telnet -
> >>but NOTHING during the LP attempt -

> >>in other words -
> >>it's not a touch and printer barf situation,
> >>nothing at all comes out of the 6000 -
> >>it must be failing due to some type of corruption
> >>in one of the printer/jetdirect files on the 6000.
> >>Phil -

by **Phil W. Schum** » Sat, 22 Aug 1998 04:00:00

I just dialed in and checked the dir of the files -
the other part of the problem was the permissions
of the backend programs - along with Ping and Telnet -
I covered this in another msg about 'sticky bits'

anyway - if the permissions are 'r-x' you get your own permissions,
if they are 'r-s' then you have a 'sticky bit'
and get the permissions of the 'owner' -
with our /etc/hosts file not granted open 'read' access (in error)
then only 'root' users could print to the laser - BUT WHY ??
well - the 'rembak' backend has 'sticky bit' and 'root'
so the dot matrix printers all worked ok - as root users -
however - the 'piojetd' backend has 'x' bit
therefore you are on your own permissions - and it would fail -
had the 'piojetd' had the sticky bit,
or the 'rembak' NOT had the sticky bit,
it would have been even more interesting...none or all would have worked -
Phil -

>this was a good one -
>the problem was the /etc/hosts file - the PERMISSIONS -
>the FTP'd copy created them with just RW-R--
>and it really needed RW-RW-R--

>it would work fine under root, but not from a user -
>that was our clue -

>before we FTP'd the file over to the 6000, we renamed the old -

>since it did not have a file to 'replace',
>the new file had some default permissions vs the 'old' ones inherited.
>when we changed the permissions, everything was then ok.
>wow - what a detective story :))

>Phil -

>...

>>I can ping and telnet into the devices -
>>all with their static/assigned addresses -
>> but good point :)
>>also....
>>another bit of info -
>>I put the protocol analyzer online and watched it -
>>I could see the ping and telnet -
>>but NOTHING during the LP attempt -

>>in other words -
>>it's not a touch and printer barf situation,
>>nothing at all comes out of the 6000 -
>>it must be failing due to some type of corruption
>>in one of the printer/jetdirect files on the 6000.
>>Phil -

by **Phil W. Schum** » Sat, 22 Aug 1998 04:00:00

hmm - we are AIX 4.2.1 -
well I have no other explanation
for why the dot matrix printers worked,
and the lasers did not

REMBAK = sticky 's' + root ==> worked
PIOJETD = 'x' bit ==> failed
Phil -

Quote:
>Phil,

>Actually, the sticky (setuid) bit on a shell script doesn't work except in
>OLD
>AIX releases.

>Regards,
>Paul

Very Computer

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start

Laser print Qs down - won't start