(Follow-up posted to comp.unix.sco.misc as well)

On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:

>Everyone,
>
>I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
>giving me errors related to the printing process. I have included
>some of them below
>---------------------------------------------------
>Your request lpt2-509301 destined for lpt2
>encountered an error while printing on printer lpt2.
>
>Reason for failure:
>
>/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
>dumped
>---------------------------------------------------
>Other messages include the following:
>
>/usr/spool/lp/admins/lp/interfaces/lpt2: 13665 Memory fault - core
>dumped
>/usr/spool/lp/admins/lp/interfaces/lpt2: 12988 Memory fault - core
>dumped
>
>The output ``port'', a FIFO, was closed before all output was written.
>/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
>dumped
>/usr/spool/lp/admins/lp/interfaces/lpt5: 5347 Memory fault - core
>dumped
>
>Can any of you give me a start on this problem.
>
>Thank you,
>
>Greg Ennis

You have a problem in your interfaces files (lpt2, lpt5 from above) or
they've become corrupted. Those files are simple shell scripts
(usually), so looking through them should give you some idea.

There are SCO-specific NGs where this question may solicit more
responses, comp.unix.sco.misc being one.


Scott McMillan

Scott McMillan <smcm@usa.net> wrote in message news:<m3sd00l5qv931n23f98il0ccf2i9avih6a@4ax.com>. ..
> (Follow-up posted to comp.unix.sco.misc as well)
>
> On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:
>
> >Everyone,
> >
> >I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
> >giving me errors related to the printing process. I have included
> >some of them below
> >---------------------------------------------------
> >Your request lpt2-509301 destined for lpt2
> >encountered an error while printing on printer lpt2.
> >
> >Reason for failure:
> >
> >/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
> >dumped
> >---------------------------------------------------
> >Other messages include the following:
> >
> >/usr/spool/lp/admins/lp/interfaces/lpt2: 13665 Memory fault - core
> >dumped
> >/usr/spool/lp/admins/lp/interfaces/lpt2: 12988 Memory fault - core
> >dumped
> >
> >The output ``port'', a FIFO, was closed before all output was written.
> >/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
> >dumped
> >/usr/spool/lp/admins/lp/interfaces/lpt5: 5347 Memory fault - core
> >dumped
> >
> >Can any of you give me a start on this problem.
> >
> >Thank you,
> >
> >Greg Ennis
>
> You have a problem in your interfaces files (lpt2, lpt5 from above) or
> they've become corrupted. Those files are simple shell scripts
> (usually), so looking through them should give you some idea.
>
> There are SCO-specific NGs where this question may solicit more
> responses, comp.unix.sco.misc being one.
>
>
> Scott McMillan

Scott,

Thanks for the suggestion of a different newsgroup, and thanks again
for moving my inquiry to the new group.

Here is a copy of the lpt2 script that is causing the problem. the
lpt5 script is a copy of lpt2.

If anyone can give me a starting point I would appreciate it.

Thank you,

Greg Ennis

#!/bin/sh
#
# @(#) hpnp.model 62.2 97/03/03
#
# $Header: hpnp.model,v 1.9 91/11/14 10:44:35 pma Exp $
#
# Copyright (C) 1991-1997 The Santa Cruz Operation, Inc.
# All Rights Reserved.
# The information in this file is provided for the exclusive use of
# the licensees of The Santa Cruz Operation, Inc. Such users have the
# right to use, modify, and incorporate this code into other products
# for purposes authorized by the license agreement provided they
include
# this notice and the associated copyright notice with any such
product.
# The information in this file is provided "AS IS" without warranty.
#
# (c)Copyright Hewlett-Packard Company 1991. All Rights Reserved.
# (c)Copyright 1983 Regents of the University of California
# (c)Copyright 1988, 1989 by Carnegie Mellon University
#
# RESTRICTED RIGHTS LEGEND
# Use, duplication, or disclosure by the U.S. Government is subject to
# restrictions as set forth in sub-paragraph (c)(1)(ii) of the Rights
in
# Technical Data and Computer Software clause in DFARS 252.227-7013.
#
# Hewlett-Packard Company
# 3000 Hanover Street
# Palo Alto, CA 94304 U.S.A.
#
# HP-UX Network Peripheral Model Script
#
# This script invokes the original model script
# from the subdirectory model.orig and pipes its
# output to hpnpf.
#
# Hpnpf does not exit on signal 15. Thus, the
# original model script can catch the signal,
# echo a string and exit. Hpnpf will exit when
# its standard input is closed.
#

MODEL=`basename $0`
REALMODEL=`echo $0 | sed -e "s%$MODEL%model.orig/$MODEL%"`

#
# This name may be initialized when the script is
# installed in the spooler. If not, use the name
# of this script ($MODEL) as the peripheral to contact.
#
PERIPH=
if [ "$PERIPH" = "" ]
then
PERIPH=$MODEL
fi
LOG=/tmp/$PERIPH.$$
HPNPF=/usr/lib/hpnp/hpnpf
LPLOG=/tmp/hpnpf.$$
LOGTRIES=5

# set -xv
echo "$1\t$REALMODEL | $HPNPF -raw -x $PERIPH" >> $LPLOG

#
# Remove the log file if job is cancelled
# or the scheduler is shutdown.
#
trap "rm -f $LOG $LPLOG; trap 15;kill -15 0;exit 0" 15

ERRORLOGS=0
while :
do
#
# Save the stderr messages in a temporary log file
# and discard stdout which is the peripheral output.
#
rm -f $LOG
if $REALMODEL "$@" | $HPNPF -x $PERIPH 2> $LOG > /dev/null
then
#
# If the transfer is successful, remove
# the log file and exit.
#
rm -f $LOG $LPLOG
exit 0
else
#
# Added the request ID to the stderr message
# and store it in the lp log file.
#
# Only record the first $LOGTRIES errors. If
# the spooler gets in a loop retrying a job, the
# disk won't fill up with spooler log error messages.
#
if test -s $LOG -a $ERRORLOGS -lt $LOGTRIES
then
echo "$1\t`cat $LOG`" >> $LPLOG
ERRORLOGS=`expr $ERRORLOGS + 1`
fi
if test $ERRORLOGS -eq $LOGTRIES
then
echo "$1\t$LOGTRIES errors logged for $1; errors no longer
logged" >> $LPLOG
ERRORLOGS=`expr $ERRORLOGS + 1`
fi
fi
if [ ! -s $LPLOG ]
then
rm -f $LPLOG
fi
sleep 10
done

In article <6c2fdba7.0401170806.70722bb8@posting.google.com >,
Greg Ennis <PoMec@PoMec.Net> wrote:
>Scott McMillan <smcm@usa.net> wrote in message news:<m3sd00l5qv931n23f98il0ccf2i9avih6a@4ax.com>. ..
>> (Follow-up posted to comp.unix.sco.misc as well)
>>
>> On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:
>>
>> >Everyone,
>> >
>> >I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
>> >giving me errors related to the printing process. I have included
>> >some of them below
>> >---------------------------------------------------
>> >Your request lpt2-509301 destined for lpt2
>> >encountered an error while printing on printer lpt2.
>> >
>> >Reason for failure:
>> >
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
>> >dumped
>> >---------------------------------------------------
>> >Other messages include the following:
>> >
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 13665 Memory fault - core
>> >dumped
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 12988 Memory fault - core
>> >dumped
>> >
>> >The output ``port'', a FIFO, was closed before all output was written.
>> >/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
>> >dumped
>> >/usr/spool/lp/admins/lp/interfaces/lpt5: 5347 Memory fault - core
>> >dumped
>> >
>> >Can any of you give me a start on this problem.
>> >
>> >Thank you,
>> >
>> >Greg Ennis
>>
>> You have a problem in your interfaces files (lpt2, lpt5 from above) or
>> they've become corrupted. Those files are simple shell scripts
>> (usually), so looking through them should give you some idea.
>>
>> There are SCO-specific NGs where this question may solicit more
>> responses, comp.unix.sco.misc being one.
>>
>>
>> Scott McMillan
>
>Scott,
>
>Thanks for the suggestion of a different newsgroup, and thanks again
>for moving my inquiry to the new group.
>
>Here is a copy of the lpt2 script that is causing the problem. the
>lpt5 script is a copy of lpt2.
>
>If anyone can give me a starting point I would appreciate it.

[standard script deleted].

Are you calling the prints jobs with lp and no flags other than
-d printername.

If so you might try -c to make a copy of the file first.

See Tony's site http://www.aplawrence.com and search for
the articles on printing.

Didn't I mention this in comp.unix.admin?

Bill

--
Bill Vermillion - bv @ wjv . com

Bill Vermillion enscribed:
| In article <6c2fdba7.0401170806.70722bb8@posting.google.com >,
| Greg Ennis <PoMec@PoMec.Net> wrote:
| >Scott McMillan <smcm@usa.net> wrote in message news:<m3sd00l5qv931n23f98il0ccf2i9avih6a@4ax.com>. ..
| >> (Follow-up posted to comp.unix.sco.misc as well)
| >>
| >> On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:
| >>
| >> >Everyone,
| >> >
| >> >I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
| >> >giving me errors related to the printing process. I have included
| >> >some of them below
| >> >---------------------------------------------------
| >> >Your request lpt2-509301 destined for lpt2
| >> >encountered an error while printing on printer lpt2.
| >> >
| >> >Reason for failure:
| >> >
| >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
| >> >dumped
| >> >---------------------------------------------------
| >> >Other messages include the following:
| >> >
| >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 13665 Memory fault - core
| >> >dumped
| >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 12988 Memory fault - core
| >> >dumped
| >> >
| >> >The output ``port'', a FIFO, was closed before all output was written.
| >> >/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
| >> >dumped
| >> >/usr/spool/lp/admins/lp/interfaces/lpt5: 5347 Memory fault - core
| >> >dumped
| >> >
| >> >Can any of you give me a start on this problem.
| >> >
| >> >Thank you,
| >> >
| >> >Greg Ennis
| >>
| >> You have a problem in your interfaces files (lpt2, lpt5 from above) or
| >> they've become corrupted. Those files are simple shell scripts
| >> (usually), so looking through them should give you some idea.
| >>
| >> There are SCO-specific NGs where this question may solicit more
| >> responses, comp.unix.sco.misc being one.
| >>
| >>
| >> Scott McMillan
| >
| >Scott,
| >
| >Thanks for the suggestion of a different newsgroup, and thanks again
| >for moving my inquiry to the new group.
| >
| >Here is a copy of the lpt2 script that is causing the problem. the
| >lpt5 script is a copy of lpt2.
| >
| >If anyone can give me a starting point I would appreciate it.
|
| [standard script deleted].
|
| Are you calling the prints jobs with lp and no flags other than
| -d printername.
|
| If so you might try -c to make a copy of the file first.
|
| See Tony's site http://www.aplawrence.com and search for
| the articles on printing.
|
| Didn't I mention this in comp.unix.admin?

Actually this sounds more like someone kludged a printer into the system
without using the printer manager. Hand editing the printer files (other
than the interface script) has been known to cause problems.

The first step would be to remove the printer and reinstall it with
scoadmin printer.
--
================================================== ========================
Tom Parsons tom@tegan.com
================================================== ========================

In comp.unix.sco.misc Greg Ennis <PoMec@pomec.net> wrote:
>Scott McMillan <smcm@usa.net> wrote in message news:<m3sd00l5qv931n23f98il0ccf2i9avih6a@4ax.com>. ..
>> (Follow-up posted to comp.unix.sco.misc as well)
>>
>> On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:
>>
>> >Everyone,
>> >
>> >I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
>> >giving me errors related to the printing process. I have included
>> >some of them below
>> >---------------------------------------------------
>> >Your request lpt2-509301 destined for lpt2
>> >encountered an error while printing on printer lpt2.
>> >
>> >Reason for failure:
>> >
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
>> >dumped
>> >---------------------------------------------------
>> >Other messages include the following:
>> >
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 13665 Memory fault - core
>> >dumped
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 12988 Memory fault - core
>> >dumped
>> >
>> >The output ``port'', a FIFO, was closed before all output was written.
>> >/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
>> >dumped
>> >/usr/spool/lp/admins/lp/interfaces/lpt5: 5347 Memory fault - core
>> >dumped
>> >
>> >Can any of you give me a start on this problem.


Well, if you just copied lpt2 to lpt5, that's your problem:
you have no lpt5 in /usr/spool/lp/admins/lp/interfaces/model.orig

See http://aplawrence.com/SCOFAQ/scotec7.html to understand this.

Better idea: dump the hp.model junk and use netcat:
http://aplawrence.com/SCOFAQ/scotec7.html#getnetcat


--
tony@aplawrence.com Unix/Linux/Mac OS X resources: http://aplawrence.com
Get paid for writing about tech: http://aplawrence.com/publish.html

On 17 Jan 2004 08:06:43 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:

>Scott McMillan <smcm@usa.net> wrote in message news:<m3sd00l5qv931n23f98il0ccf2i9avih6a@4ax.com>. ..
>> (Follow-up posted to comp.unix.sco.misc as well)
>>
>> On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:
>>
>> >Everyone,
>> >
>> >I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
>> >giving me errors related to the printing process. I have included
>> >some of them below
>> >---------------------------------------------------
>> >Your request lpt2-509301 destined for lpt2
>> >encountered an error while printing on printer lpt2.
>> >
>> >Reason for failure:
>> >
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
>> >dumped
>> >---------------------------------------------------
>> >Other messages include the following:
>> >
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 13665 Memory fault - core
>> >dumped
>> >/usr/spool/lp/admins/lp/interfaces/lpt2: 12988 Memory fault - core
>> >dumped
>> >
>> >The output ``port'', a FIFO, was closed before all output was written.
>> >/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
>> >dumped
>> >/usr/spool/lp/admins/lp/interfaces/lpt5: 5347 Memory fault - core
>> >dumped
>> >
>> >Can any of you give me a start on this problem.
>> >
>> >Thank you,
>> >
>> >Greg Ennis
>>
>> You have a problem in your interfaces files (lpt2, lpt5 from above) or
>> they've become corrupted. Those files are simple shell scripts
>> (usually), so looking through them should give you some idea.
>>
>> There are SCO-specific NGs where this question may solicit more
>> responses, comp.unix.sco.misc being one.
>>
>>
>> Scott McMillan
>
>Scott,
>
>Thanks for the suggestion of a different newsgroup, and thanks again
>for moving my inquiry to the new group.
>
>Here is a copy of the lpt2 script that is causing the problem. the
>lpt5 script is a copy of lpt2.
>
>If anyone can give me a starting point I would appreciate it.
>
>Thank you,
>
>Greg Ennis
>

<snipped hpnp.model>

I see there is no definition for PERIPH - Have you defined lpt[2,5] in
/etc/hosts? Also, as Tom Parsons mentioned, try removing and
recreating the printers, although I usually use scoadmin -> Printers
-> HP Network Printer Manager.


Scott McMillan

bv@wjv.comREMOVE (Bill Vermillion) wrote in message news:<Hrn94F.rAr@wjv.com>...
> In article <6c2fdba7.0401170806.70722bb8@posting.google.com >,
> Greg Ennis <PoMec@PoMec.Net> wrote:
> >Scott McMillan <smcm@usa.net> wrote in message news:<m3sd00l5qv931n23f98il0ccf2i9avih6a@4ax.com>. ..
> >> (Follow-up posted to comp.unix.sco.misc as well)
> >>
> >> On 15 Jan 2004 10:27:25 -0800, PoMec@PoMec.Net (Greg Ennis) wrote:
> >>
> >> >Everyone,
> >> >
> >> >I have a SCO OpenServer(TM) Release 3.2v5.0.5 machine that keeps
> >> >giving me errors related to the printing process. I have included
> >> >some of them below
> >> >---------------------------------------------------
> >> >Your request lpt2-509301 destined for lpt2
> >> >encountered an error while printing on printer lpt2.
> >> >
> >> >Reason for failure:
> >> >
> >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 4614 Memory fault - core
> >> >dumped
> >> >---------------------------------------------------
> >> >Other messages include the following:
> >> >
> >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 13665 Memory fault - core
> >> >dumped
> >> >/usr/spool/lp/admins/lp/interfaces/lpt2: 12988 Memory fault - core
> >> >dumped
> >> >
> >> >The output ``port'', a FIFO, was closed before all output was written.
> >> >/usr/spool/lp/admins/lp/interfaces/lpt5: 12820 Memory fault - core
> >> >dumped
> >> >/usr/spool/lp/admins/lp/interfaces/lpt5: 5347 Memory fault - core
> >> >dumped
> >> >
> >> >Can any of you give me a start on this problem.
> >> >
> >> >Thank you,
> >> >
> >> >Greg Ennis
> >>
> >> You have a problem in your interfaces files (lpt2, lpt5 from above) or
> >> they've become corrupted. Those files are simple shell scripts
> >> (usually), so looking through them should give you some idea.
> >>
> >> There are SCO-specific NGs where this question may solicit more
> >> responses, comp.unix.sco.misc being one.
> >>
> >>
> >> Scott McMillan
> >
> >Scott,
> >
> >Thanks for the suggestion of a different newsgroup, and thanks again
> >for moving my inquiry to the new group.
> >
> >Here is a copy of the lpt2 script that is causing the problem. the
> >lpt5 script is a copy of lpt2.
> >
> >If anyone can give me a starting point I would appreciate it.
>
> [standard script deleted].
>
> Are you calling the prints jobs with lp and no flags other than
> -d printername.
>
> If so you might try -c to make a copy of the file first.
>
> See Tony's site http://www.aplawrence.com and search for
> the articles on printing.
>
> Didn't I mention this in comp.unix.admin?
>
> Bill

------------------------------------------------------------

Bill,

Thanks for your response. The command line syntax that the system is
using is:

lpr -oraw -d $PTR

Where $PTR is the name of the printer i.e. lpt2 or lpt5 etc

Most of the time the scripts work perfectly and there is no problem.
In fact the users have not ever reported any lost print jobs. I am
only getting e-mail notices of the problem, and it only seems to
occurr when the system is busy.

Also, I have not stipulated before that these printers are network
printers that are used by Windows Desktops as well as 2 Linux boxes.
The other systems have not been reporting any errros.

I'll modify the above command to lpr -c -oraw -d $PTR to see if the
problem resolves.

Thanks again,

Greg Ennis