topic Re: Samba errors in Operating System - HP-UX

Samba errors

dictum9 — Tue, 06 Dec 2005 13:54:34 GMT

I am getting the following error, over and over again.

tail -f /usr/local/samba/var/logs/machine_name.log

write_socket_data: write failure. Error = Broken pipe
[2005/12/02 08:51:42, 0] lib/util_sock.c:(499)
write_socket_data: write failure. Error = Broken pipe
[2005/12/06 12:33:01, 0] lib/util_sock.c:(499)
write_socket_data: write failure. Error = Broken pipe

Re: Samba errors

dictum9 — Tue, 06 Dec 2005 13:57:04 GMT

P.S. Some accounts are having problems writing files, some work sometimes. What does this all mean?

This is on HP-UX 11.0.

Re: Samba errors

Geoff Wild — Tue, 06 Dec 2005 14:14:59 GMT

Try stop/start samba...

What version are you running?

what /opt/samba/bin/smbd

Rgds...Geoff

Re: Samba errors

dictum9 — Tue, 06 Dec 2005 14:21:27 GMT

HP CIFS Server: Version: A.01.11.04 based on Samba version: 2.2.12

Re: Samba errors

Geoff Wild — Tue, 06 Dec 2005 14:27:58 GMT

I have had that before - it may just be a setting...

In smb.conf, try:

keepalive = 0
client schannel = No

and if running wins:

winbind enum users = No
winbind enum groups = No

Rgds...Geoff

Re: Samba errors

Sameer_Nirmal — Tue, 06 Dec 2005 14:38:17 GMT

Hi,

These errors are socket errors showing "write failure" occured while writing socket data at client side.

I guess you have Windows 2K clients for which you are getting these errors. If these clients shutdown or reboots, such errors are logged in.

You need to put a parameter

keepalive = 0 in the /etc/opt/samba/smb.conf

To get rid of those messages.

Re: Samba errors

Sameer_Nirmal — Tue, 06 Dec 2005 15:14:53 GMT

Hi again,

Need to mention...

After adding/changing the parameter in the smb.conf file , you need to re start the samba using

# /sbin/init.d/samba stop
# /sbin/init.d/samba start