From owner-freebsd-questions@freebsd.org Tue Sep 19 10:35:10 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86F9BE0B68D for ; Tue, 19 Sep 2017 10:35:10 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay15.qsc.de (mailrelay15.qsc.de [212.99.187.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C4277658F for ; Tue, 19 Sep 2017 10:35:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay15.qsc.de; Tue, 19 Sep 2017 12:35:01 +0200 Received: from r56.edvax.de (port-92-195-1-252.dynamic.qsc.de [92.195.1.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 527803CC3F; Tue, 19 Sep 2017 12:34:59 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v8JAYxUA004301; Tue, 19 Sep 2017 12:34:59 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Tue, 19 Sep 2017 12:34:59 +0200 From: Polytropon To: Trond =?ISO-8859-1?Q?Endrest=F8l?= Cc: "freebsd-questions@freebsd.org" Subject: Re: how to fix " unable to print , broken pipe ! " when passing through CUPS protocol after successfully adding printers in vmware. Message-Id: <20170919123459.a05afeb9.freebsd@edvax.de> In-Reply-To: References: <20170919112258.cf2362cf.freebsd@edvax.de> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay15.qsc.de with C549B68365F X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1447 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Sep 2017 10:35:10 -0000 On Tue, 19 Sep 2017 11:47:19 +0200 (CEST), Trond Endrest=F8l wrote: > On Tue, 19 Sep 2017 11:22+0200, Polytropon wrote: >=20 > > On Tue, 19 Sep 2017 14:10:37 +0530, manash pal wrote: > > > I am very new to FreeBSD, after stuyding at google and youtube, I hav= e =20 > > > started to wipe out some embarrassment to go through this unix like o= s. =20 > > > however, after succussfully adding my printer through cups , I tried = to =20 > > > proceed printing of a pdf document. but , got a repeated reply " UNAB= LE TO =20 > > > PRINT DOCUMENT, BROKEN PIPE ! " what does it mean ? > >=20 > > Depends. The error "broken pipe" indicates a problem with data > > transmission between programs, usually the kind of "output of > > program A is input of program B". In CUPS, this piping concept > > creates a "data flow" through the different parts of the whole > > printing mechanism (technically not fully correct, but think of > > it like entry queue -> printer spooler -> printer filter -> out- > > out channel to printer). On that way, something happened. > >=20 > > Open your web browser and go to http://localhost:631/ where > > you find the CUPS web interface. In the printer listing, you > > can see the full error. > >=20 > > More information can be obtained from the CUPS log files, > > for example /var/log/cups/error_log. See if you find additional > > details there. > >=20 > > Sidenote: When you say "I print a PDF document", please specify > > _how_ you print it, as there are several ways to do so, and > > this could also be part of the problem you're experiencing. > > For example, > >=20 > > % lpr somefile.pdf > >=20 > > is one way to print a PDF document, but so is opening it in > > a PDF viewer (which there are at least 5 availabe on FreeBSD) > > and hitting the "Print" button. Printing PDFs from Gimp is > > possible, too. > >=20 > > The same (!) applies for the error message: Where did you read > > it? Which program provided the error message? CUPS? The PDF > > viewer you printed from? Was it a console message? If possible, > > provide the full text of the error message. In many cases, the > > error message text contains 50 % of the solution of the problem > > it is informing you about. > >=20 > > The fewer guesswork is involved, the easier is it to get the > > desired diagnostic result. :-) > >=20 > >=20 > >=20 > > > and how to solve this =20 > > > problem ? > >=20 > > Without proper diagnostics, there is nothing that I can say... >=20 > Watch your PATH. I've seen plenty of CUPS and lpd(8) problems due to=20 > /usr/bin/l* being used instead of /usr/local/bin/l*, and vice versa. Yes. And I have invented many ugly hacks to deal with this situation. :-) CUPS's default installation path for the binaries is /usr/local/bin, as intended. But due to the order in $PATH, the wrong utility could be called (the lpd one instead of the CUPS one). There is a port option to install the binaries into the OS location /usr/sbin and overwrite the OS tools, but that can cause problems during updates. There is lots of potential for confusion. :-) --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...