#499 Samba 'errors' with 0.69.1 4292 (samba 3.0.34)

v0.69x
closed
Volker
5
2014-08-27
2009-01-23
templemeads
No

I am not certain if these are 'real' problems; but after updating to 0.69.1 4292 (embedded) I see the following logs (Samba appeared to be working OK - if slow!)

Jan 23 13:52:41 smbd[1565]: [2009/01/23 13:52:41, 0] passdb/pdb_smbpasswd.c:startsmbfilepwent(241)
Jan 23 13:52:41 smbd[1565]: startsmbfilepwent_internal: file /var/etc/private/smbpasswd did not exist. File successfully created.
Jan 23 13:52:44 lighttpd[1764]: (log.c.97) server started
Jan 23 13:52:45 login: login on ttyv0 as root
Jan 23 13:53:32 smbd[1905]: [2009/01/23 13:53:32, 0] lib/util_sock.c:set_socket_options(261)
Jan 23 13:53:32 smbd[1905]: Failed to set socket option IPTOS_LOWDELAY (Error Connection reset by peer)
Jan 23 13:53:32 smbd[1905]: [2009/01/23 13:53:32, 0] lib/util_sock.c:set_socket_options(261)
Jan 23 13:53:32 smbd[1905]: Failed to set socket option TCP_NODELAY (Error Connection reset by peer)
Jan 23 13:53:32 smbd[1905]: [2009/01/23 13:53:32, 0] lib/util_sock.c:get_peer_addr(1224)
Jan 23 13:53:32 smbd[1905]: getpeername failed. Error was Socket is not connected
Jan 23 13:53:32 smbd[1905]: [2009/01/23 13:53:32, 0] lib/util_sock.c:write_data(562)
Jan 23 13:53:32 smbd[1905]: write_data: write failure in writing to client 192.168.0.2. Error Broken pipe
Jan 23 13:53:32 smbd[1905]: [2009/01/23 13:53:32, 0] lib/util_sock.c:send_smb(761)
Jan 23 13:53:32 smbd[1905]: Error writing 4 bytes to client. -1. (Broken pipe)
Jan 23 13:58:31 nmbd[1561]: [2009/01/23 13:58:31, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
Jan 23 13:58:31 nmbd[1561]: **
Jan 23 13:58:31 nmbd[1561]:
Jan 23 13:58:31 nmbd[1561]: Samba name server FREENAS1 is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.10
Jan 23 13:58:31 nmbd[1561]:
Jan 23 13:58:31 nmbd[1561]:
**
Jan 23 15:00:41 smbd[12164]: [2009/01/23 15:00:41, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463)
Jan 23 15:00:41 smbd[12164]: call_nt_transact_ioctl(0x9009c): Currently not implemented.

Regards

Andy

Discussion

  • Volker
    Volker
    2009-01-26

    Hmmm, i did not get these errors nor slow speed. Anyone else having these problems?

    Regards
    Volker

     
  • Volker
    Volker
    2009-01-27

    Hi again,
    can you increase the log level to debug to get as much informations as possible?

    Thanks
    Volker

     
  • templemeads
    templemeads
    2009-01-27

    ...no problem. I have enabled SMB 'debug' logging (now performance is much slower!)
    So far, I have not seen a repeat of this 'error'.

    Is there a method to display more debug data via the webGUI (only last 50 entries using diag_logs.php which does not capture much traffic with SMB reporting in Debug mode)?

    If I see the error again, I'll post an update.

    Regards

    Andy

     
  • Volker
    Volker
    2009-02-02

    You can try to increase the number of displayed rows on the 'Diag|Logs|Settings' tab page.

     
  • Volker
    Volker
    2009-02-03

    Yesterday i realized that message on my test system too. I did not find any solution for this so i switch back to the previous working version.

    Regards
    Volker

     
  • templemeads
    templemeads
    2009-02-03

    Hi Volker

    Whilst it is not good you see the error message too, if it is a problem that needs fixing, then you will be in a better position.

    Some Internet searches reveal many Samba users experience this error.

    The following link is an on-line calculator to decode IOCTL codes (I dont know of it helps!)
    http://www.osronline.com/article.cfm?article=229

    IOCTL VALUE (hex) 0x9009c
    Device: FILE_SYSTEM (0x9)
    Function: 0x27
    Access: FILE_ANY_ACCESS
    Method: METHOD_BUFFERED

    The following user experienced the error using OpenBSD and Samba 3.0.31. As with the error I experienced, it follows (common) Broken_Pipe error. I read on the FreeNAS forum where users set additional Samba parameters which in some cases remove this error.
    http://www.usenet-forums.com/samba/410389-samba-microsoft-access-mdb-database-samba-share.html

    This link suggests the error is caused when Samba client requests FSCTL_GET_OBJECT_ID and it fails(?)
    http://markmail.org/message/isi44cc3sl7bknen

    Also, from the FreeNAS forum, I found a log with this error in 0.69B3, so I guess this must exist with older Samba versions:
    http://apps.sourceforge.net/phpbb/freenas/viewtopic.php?f=46&t=276#p1040

    I see Samba 3.3.0 is available - I cannot see mention of this (long running) error being addressed (I assume it is a Samba issue).

    Good Luck!

    Sorry I cannot provide much help.

    Andy