Broken pipes reported by smbclient

I followed Orielly's online Samba troubleshooting guide until I reached section 9.2.5.2.

I get the following errors about broken pipes:

linuxbox:/# smbclient -L localhost -U%
Added interface ip=10.0.0.69 bcast=10.0.0.255 nmask=255.255.255.0
read_socket_with_timeout: timeout read. read error = Broken pipe.
session request to LOCALHOST failed
read_socket_with_timeout: timeout read. read error = Broken pipe.
session request to *SMBSERVER failed

The Orielly guide does NOT give this as one of the possible errors that this command can give, so I'm a bit stumped as to where to turn next.  Up until this test, the computer in question passes all the others perfectly.  Telnet and ftp to the computer work perfectly.

Any ideas on how to fix the pipes?
LVL 13
magarityAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
jlevieConnect With a Mentor Commented:
Well, there's what's wrong. Which Linux are you on and if you've compiled a new kernel does it have the System V IPC options enabled (in the General setup section of xconfig)?
0
 
jlevieCommented:
Have you configured Samba and is it running? You can check for the existance of the Samba daemons with "ps -ef | grep mbd | grep -v grep", which should return something like:

root      1380     1  0 Apr28 ?        00:00:02 bin/nmbd
root      1382     1  0 Apr28 ?        00:00:00 bin/smbd

if both daemons are running.
0
 
magarityAuthor Commented:
jlevie,
Yes, I get the following when trying that command:

root       104     1  0 22:34 ? 00:00:00 usr/sbin/smbd -D
root       106     1  0 22:34 ? 00:00:00 usr/sbin/nmbd -D              

also, 'netstat -a' lists the apropriate ports are ready to recieve.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
jlevieCommented:
Could I see what's in /etc/hosts?
0
 
magarityAuthor Commented:
jlevie,
sure, here is everthing that isn't a comment:

127.0.0.1       localhost
10.0.0.69               littleboy.house.net littleboy
10.0.0.1 jevex
10.0.0.4 zorac
10.0.0.10 sarah                    

where 'littleboy' is the linux computer in question.
0
 
jlevieCommented:
Well it's not going to be any of the simple things, your hosts file looks fine.

You should have testparm somewhere on the system. If you haven't already, it would be good to run it and see if it likes your smb.conf file. If there's nothing remarkable in the testparm output, try stopping and restarting Samba to make sure that it's using the current smb.conf data. If it still doesn't work, you can send me your smb.conf file (jlevie@bellsouth.net) and I'll see if I can spot what's wrong.
0
 
magarityAuthor Commented:
testparm says that the configuration is loaded correctly.

restarting the system, which I assume restarts samba with the current smb.conf file, does not help.

here's the very simple smb.conf file:

[global]
workgroup = colorado
security = user
browsable = yes
local master = yes
log level = 1
log file = /sambalog.log
[homes]
guest ok = no
browsable = no
[storage]
path = /usr/storage
public = yes

I even tried recompiling the kernel again just to make sure that the smb fs was properly inserted.
0
 
magarityAuthor Commented:
Here is the log file after deleting the one that was there and rebooting.  The first entry is before running "smbclient -L localhost -U%" and the others were added after that.

[2000/04/29 18:20:44, 1] smbd/files.c:file_init(216) file_init: Information only: requested 10000 open files, 1014 are available.

[2000/04/29 18:22:23, 0] locking/shmem_sysv.c:sysv_shm_open(563)
  Can't create or use semaphore [1]. Error was Function not implemented

[2000/04/29 18:22:23, 0] locking/locking.c:locking_init(174)
  ERROR: Failed to initialise share modes

[2000/04/29 18:22:24, 0] locking/shmem_sysv.c:sysv_shm_open(563)
  Can't create or use semaphore [1]. Error was Function not implemented

[2000/04/29 18:22:24, 0] locking/locking.c:locking_init(174)
  ERROR: Failed to initialise share modes
0
 
magarityAuthor Commented:
slackware 7

no, i have not put in the system v ipc since the help on that says its particularly for dosemu, which i don't want.

i take it i should have that in there, so i'm running a recompile now and will report back later.  (its a 3 hour job on the machine in question, hah hah)

what tipped you off that i needed it?
0
 
jlevieCommented:
Because the log file had:

2000/04/29 18:22:23, 0] locking/shmem_sysv.c:sysv_shm_open(563)
                         Can't create or use semaphore [1]. Error was Function not implemented

and semaphores and shared memory are a part of the SysV IPC.

The kernel notes can only tell you about things that the kernel know it needs for something else. There's no way that it could know that you intend to load some application (like Samba, MySQL, or Postgres, etc) that also requires that option. Hopefully it will only be the SysV IPC that's missing and Samba will work when the new kernel is in place.
0
 
magarityAuthor Commented:
Hurrah, I never would have guessed that this was the cause of my troubles but not compiling in system v ipc was what was missing.
0
 
jlevieCommented:
Great, I'm glad its working now.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.