thr3ads.net - samba - [Samba] cli_pipe: return critical error. Error was Call returned zero byte (EOF), hilfe! [May 2003]

If this information is useful, please help other people find it:
Share via:

Dragan Krnic

2003-May-12 16:01 UTC

[Samba] cli_pipe: return critical error. Error was Call returned zero byte (EOF), hilfe!

Hi Kurt,

I tried to explain my problem to you at Göttingen
but it looks like I'm the only one who gets this
error.

I've just reinstalled my box with SuSE 8.2, kernel
2.4.20-62, samba 2.2.8a, and cups 1.1.18, moved all 
config files, databases, scripts and jobs to it and
it looks like samba has become even better and faster. 
No one noticed anything wrong except I just can't come
to terms with cups. I hoped my problem would be gone
with the new installation but it wouldn't.

I've gone strictly according to the book, your
"Printing with CUPS (Samba 2.2.x and 3.0)", which
I picked up at Samba Experience, but I still get
the same buggy result NT_STATUS_UNSUCCESSFUL when
cupsaddsmb executes adddriver for "Windows NT x86"
and "Windows 4.0" as well as when it finally does
the set driver. Here is a slightly edited log:

p90:~ # lpstat -t
scheduler is running
system default destination: lp
device for lp: parallel:/dev/lp0
lp accepting requests since Jan 01 00:00
printer lp is idle.  enabled since Jan 01 00:00

p90:~ # cupsaddsmb -U root -v lp
Password for root required to \
access localhost via SAMBA: 
Running command: \
smbclient //localhost/print\$ -N -U'root%secret' \
-c 'mkdir W32X86;\
put /var/spool/cups/tmp/3ebfbbceacb75 W32X86/lp.ppd;\
put /usr/share/cups/drivers/cupsdrvr.dll\
    W32X86/cupsdrvr.dll;\
put /usr/share/cups/drivers/cupsui.dll\
    W32X86/cupsui.dll;\
put /usr/share/cups/drivers/cups.hlp W32X86/cups.hlp'

added interface ip=172.24.204.184 \
      bcast=172.24.207.255 nmask=255.255.248.0
added interface ip=192.168.0.1 \
      bcast=192.168.0.255 nmask=255.255.255.0
Domain=[DOM1] OS=[Unix] Server=[Samba 2.2.8a-SuSE]
NT_STATUS_OBJECT_NAME_COLLISION making remote \
directory \W32X86

putting file /var/spool/cups/tmp/3ebfbbceacb75 as\
      \W32X86/lp.ppd
putting file /usr/share/cups/drivers/cupsdrvr.dll as\
      \W32X86/cupsdrvr.dll
putting file /usr/share/cups/drivers/cupsui.dll as\
      \W32X86/cupsui.dll
putting file /usr/share/cups/drivers/cups.hlp as\
      \W32X86/cups.hlp

Running command:
rpcclient localhost -N -U'root%secret' -c '\
adddriver "Windows NT x86" \
"lp:cupsdrvr.dll:lp.ppd:cupsui.dll:cups.hlp:\
NULL:RAW:NULL"'

cmd = adddriver "Windows NT x86" \
"lp:cupsdrvr.dll:lp.ppd:cupsui.dll:cups.hlp:\
NULL:RAW:NULL"
cli_pipe: return critical error. Error was \
          Call returned zero bytes (EOF)

result was NT_STATUS_UNSUCCESSFUL

Running command:
smbclient //localhost/print\$ -N -U'root%secret' \
-c 'mkdir WIN40;\
put /var/spool/cups/tmp/3ebfbbceacb75 WIN40/lp.PPD;\
put /usr/share/cups/drivers/ADFONTS.MFM \
    WIN40/ADFONTS.MFM;\
put /usr/share/cups/drivers/ADOBEPS4.DRV \
    WIN40/ADOBEPS4.DRV;\
put /usr/share/cups/drivers/ADOBEPS4.HLP \
    WIN40/ADOBEPS4.HLP;\
put /usr/share/cups/drivers/DEFPRTR2.PPD \
    WIN40/DEFPRTR2.PPD;\
put /usr/share/cups/drivers/ICONLIB.DLL \
    WIN40/ICONLIB.DLL;\
put /usr/share/cups/drivers/PSMON.DLL \
    WIN40/PSMON.DLL;'

added interface ip=172.24.204.184 \
      bcast=172.24.207.255 nmask=255.255.248.0
added interface ip=192.168.0.1 \
      bcast=192.168.0.255 nmask=255.255.255.0
Domain=[DOM1] OS=[Unix] Server=[Samba 2.2.8a-SuSE]
NT_STATUS_OBJECT_NAME_COLLISION making remote 
directory \WIN40

putting file /var/spool/cups/tmp/3ebfbbceacb75 as \
     \WIN40/lp.PPD
putting file /usr/share/cups/drivers/ADFONTS.MFM as \
     \WIN40/ADFONTS.MFM
putting file /usr/share/cups/drivers/ADOBEPS4.DRV as \
     \WIN40/ADOBEPS4.DRV
putting file /usr/share/cups/drivers/ADOBEPS4.HLP as \
     \WIN40/ADOBEPS4.HLP
putting file /usr/share/cups/drivers/DEFPRTR2.PPD as \
     \WIN40/DEFPRTR2.PPD
putting file /usr/share/cups/drivers/ICONLIB.DLL as \
     \WIN40/ICONLIB.DLL
putting file /usr/share/cups/drivers/PSMON.DLL as \
     \WIN40/PSMON.DLL

Running command:\
rpcclient localhost -N -U'root%secret' \
-c 'adddriver \
"Windows 4.0" \
"lp:ADOBEPS4.DRV:lp.PPD:NULL:ADOBEPS4.HLP:\
    PSMON.DLL:RAW:ADOBEPS4.DRV,lp.PPD,ADOBEPS4.HLP,\
    PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'

cmd = adddriver \
"Windows 4.0" \
"lp:ADOBEPS4.DRV:lp.PPD:NULL:ADOBEPS4.HLP:\
    PSMON.DLL:RAW:ADOBEPS4.DRV,lp.PPD,ADOBEPS4.HLP,\
    PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"

cli_pipe: return critical error. Error was
          Call returned zero bytes (EOF)

result was NT_STATUS_UNSUCCESSFUL

Running command: rpcclient localhost -N -U'root%secret' -c
'setdriver lp lp'

cmd = setdriver lp lp
result was NT_STATUS_UNSUCCESSFUL

The samba log records the following error:
===================================================INTERNAL ERROR: Signal 11 in
pid 29670 (2.2.8a-SuSE)
Please read the file BUGS.txt in the distribution
===================================================
I've had the same problem with 2.2.6's and 2.2.7's
but apparently even though INTERNAL ERRORs are
reported, cups works with samba very well. If you
try connecting from a freshly installed W2K, it
dutifully downloads the drivers and does the
printing, but still it's a nagging feeling that
something is wrong, a little Murphy ticking in the
innards of my samba server just watching for the
least convenient moment to go off.

Can you help?

Cheers
Dragan

PS.: As a matter of fact the downloadable drivers are
a PITA, because they let you fully control all of the
features (lot of them on this color laser babe) but
they let you do it in a lack-lustre explorer-like 
applet instead of in the fancy multi-layered dialog
box that the people have grown so fond of on their 
Windoze boxes. So in order to have all the glitz
I give my users a step-by-step pictorial guidance
how to not let their box download the drivers from
samba automatically. It is counterintuitive, but
what shall I say? It would be ideal for samba to
just swallow everything that normally goes into a
printer installation and then dole it out on demand
to everyone else like any WinStation would do.


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005

Kurt Pfeifle

2003-May-12 16:18 UTC

head link

[Samba] cli_pipe: return critical error. Error was Call returned zero byte (EOF), hilfe!

Dragan Krnic wrote:> Hi Kurt,
> 
> I tried to explain my problem to you at G?ttingen
> but it looks like I'm the only one who gets this
> error.
> 
> I've just reinstalled my box with SuSE 8.2, kernel
> 2.4.20-62, samba 2.2.8a, and cups 1.1.18, moved all 
> config files, databases, scripts and jobs to it and
> it looks like samba has become even better and faster. 
> No one noticed anything wrong except I just can't come
> to terms with cups. I hoped my problem would be gone
> with the new installation but it wouldn't.
> 
> I've gone strictly according to the book, your
> "Printing with CUPS (Samba 2.2.x and 3.0)", which
> I picked up at Samba Experience,
Please get yourself the updated version from

   http://www.linuxprinting.org/kpfeifle/SambaPrintHOWTO/

It contains a lot more material on that question,
including how to do it all manually with rpcclient.
> but I still get
> the same buggy result NT_STATUS_UNSUCCESSFUL when
> cupsaddsmb executes adddriver for "Windows NT x86"
> and "Windows 4.0" as well as when it finally does
> the set driver. Here is a slightly edited log:
Sorry, I don't have time right now to look thru that log
in detail. But probably I will tonight, in which case you
will find s.th. in your mailbox tomorrow morning...

Cheers,
Kurt

Possibly Parallel Threads

Search for more reasonably related threads

samba - May 2003 - cli_pipe: return critical error. Error was Call returned zero byte (EOF), hilfe!

[Samba] cli_pipe: return critical error. Error was Call returned zero byte (EOF), hilfe!

[Samba] cli_pipe: return critical error. Error was Call returned zero byte (EOF), hilfe!

Possibly Parallel Threads