Samba Config Help? - SCO

This is a discussion on Samba Config Help? - SCO ; Hi Guys, I'm hoping you can help me. Sorry for such a long post. I think Samba is causing my server troubles. I used samba on 5.0.7 with no trouble at all. but on Openserver 6 I'm starting to get ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Samba Config Help?

  1. Samba Config Help?

    Hi Guys,

    I'm hoping you can help me. Sorry for such a long post.

    I think Samba is causing my server troubles. I used samba on 5.0.7
    with no trouble at all. but on Openserver 6 I'm starting to get some
    trouble.

    Here's my network setup, we do not have a Domain, do not really want a
    domain at this time. We operate everything off of a Workgroup.
    Basically all my users just telnet to the SCO machine to operate
    programs off of SCO.

    I'm thinking about changing my Samba config to set local master,
    preferred master & domain master all to "NO" to see if that stops the
    errors. I just can't figure it out.

    any help at all will be greatly appreciated.

    I'm receiving alot of Samba error messages, repeated over and over
    every day:
    -----------
    Jul 12 08:35:13 smbd[4985]: [2007/07/12 08:35:13, 0] lib/util_sock.c:
    (258)
    Jul 12 08:35:13 smbd[4985]: Failed to set socket option SO_KEEPALIVE
    (Error Invalid argument)
    Jul 12 08:35:13 smbd[4985]: [2007/07/12 08:35:13, 0] lib/util_sock.c:
    (258)
    Jul 12 08:35:13 smbd[4985]: Failed to set socket option TCP_NODELAY
    (Error Invalid argument)
    Jul 12 08:35:13 smbd[4985]: [2007/07/12 08:35:13, 0] lib/util_sock.c:
    (1222)
    Jul 12 08:35:13 smbd[4985]: getpeername failed. Error was Invalid
    argument
    Jul 12 08:35:13 smbd[4985]: [2007/07/12 08:35:13, 0] lib/util_sock.c:
    (526)
    Jul 12 08:35:13 smbd[4985]: read_data: read failure for 4 bytes to
    client 192.168.11.67. Error = Connection reset by peer
    Jul 12 08:54:34 smbd[5458]: [2007/07/12 08:54:34, 0] lib/util_sock.c:
    (526)
    Jul 12 08:54:34 smbd[5458]: read_data: read failure for 4 bytes to
    client 192.168.11.64. Error = Connection reset by peer
    Jul 12 09:03:27 smbd[5700]: [2007/07/12 09:03:27, 0] smbd/posix_acls.c:
    (2447)
    Jul 12 09:03:27 smbd[5700]: set_canon_ace_list: ACL type (file) is
    invalid for set (Invalid argument).
    Jul 12 09:03:27 smbd[5700]: [2007/07/12 09:03:27, 0] smbd/posix_acls.c:
    (2447)
    Jul 12 09:03:27 smbd[5700]: set_canon_ace_list: ACL type (file) is
    invalid for set (Invalid argument).
    Jul 12 09:04:07 smbd[5775]: [2007/07/12 09:04:07, 0] lib/util_sock.c:
    (258)
    Jul 12 09:04:07 smbd[5775]: Failed to set socket option SO_KEEPALIVE
    (Error Invalid argument)
    Jul 12 09:04:07 smbd[5775]: [2007/07/12 09:04:07, 0] lib/util_sock.c:
    (258)
    Jul 12 09:04:07 smbd[5775]: Failed to set socket option TCP_NODELAY
    (Error Invalid argument)
    Jul 12 09:04:07 smbd[5775]: [2007/07/12 09:04:07, 0] lib/util_sock.c:
    (1222)
    Jul 12 09:04:07 smbd[5775]: getpeername failed. Error was Invalid
    argument
    Jul 12 09:04:07 smbd[5775]: [2007/07/12 09:04:07, 0] lib/util_sock.c:
    (526)
    Jul 12 09:04:07 smbd[5775]: read_data: read failure for 4 bytes to
    client 192.168.11.65. Error = Connection reset by peer
    Jul 12 09:04:20 nmbd[1871]: [2007/07/12 09:04:20, 0] nmbd/
    nmbd_become_lmb.c396)
    Jul 12 09:04:20 nmbd[1871]: *****
    Jul 12 09:04:20 nmbd[1871]:
    Jul 12 09:04:20 nmbd[1871]: Samba name server HOLIDAY is now a local
    master browser for workgroup DOMAIN on subnet 192.168.11.11
    Jul 12 09:04:20 nmbd[1871]:
    Jul 12 09:04:20 nmbd[1871]: *****
    Jul 12 09:07:35 nmbd[1871]: [2007/07/12 09:07:35, 0] nmbd/
    nmbd_incomingdgrams.c311)
    Jul 12 09:07:35 nmbd[1871]: process_local_master_announce: Server
    PIII-866X2 at IP 192.168.11.24 is announcing itself as a local master
    browser for workgroup DOMAIN and we think we are master. Forcing
    election.
    Jul 12 09:07:35 nmbd[1871]: [2007/07/12 09:07:35, 0] nmbd/
    nmbd_become_lmb.c149)
    Jul 12 09:07:35 nmbd[1871]: *****
    Jul 12 09:07:35 nmbd[1871]:
    Jul 12 09:07:35 nmbd[1871]: Samba name server HOLIDAY has stopped
    being a local master browser for workgroup DOMAIN on subnet
    192.168.11.11
    Jul 12 09:07:35 nmbd[1871]:
    Jul 12 09:07:35 nmbd[1871]: *****
    Jul 12 09:07:54 nmbd[1871]: [2007/07/12 09:07:54, 0] nmbd/
    nmbd_become_lmb.c396)
    Jul 12 09:07:54 nmbd[1871]: *****
    Jul 12 09:07:54 nmbd[1871]:
    Jul 12 09:07:54 nmbd[1871]: Samba name server HOLIDAY is now a local
    master browser for workgroup DOMAIN on subnet 192.168.11.11
    Jul 12 09:07:54 nmbd[1871]:
    Jul 12 09:07:54 nmbd[1871]: *****
    Jul 12 09:14:28 smbd[1888]: [2007/07/12 09:14:28, 0] smbd/server.c:
    (389)
    Jul 12 09:14:28 smbd[1888]: open_sockets_smbd: accept: Protocol
    error
    Jul 12 09:48:33 smbd[5700]: [2007/07/12 09:48:33, 0] smbd/posix_acls.c:
    (2447)
    Jul 12 09:48:33 smbd[5700]: set_canon_ace_list: ACL type (file) is
    invalid for set (Invalid argument).
    Jul 12 09:48:33 smbd[5700]: [2007/07/12 09:48:33, 0] smbd/posix_acls.c:
    (2447)
    Jul 12 09:48:33 smbd[5700]: set_canon_ace_list: ACL type (file) is
    invalid for set (Invalid argument).
    Jul 12 10:00:51 smbd[5700]: [2007/07/12 10:00:51, 0] smbd/posix_acls.c:
    (2447)
    Jul 12 10:00:51 smbd[5700]: set_canon_ace_list: ACL type (file) is
    invalid for set (Invalid argument).
    Jul 12 10:00:51 smbd[5700]: [2007/07/12 10:00:51, 0] smbd/posix_acls.c:
    (2447)
    Jul 12 10:00:51 smbd[5700]: set_canon_ace_list: ACL type (file) is
    invalid for set (Invalid argument).
    Jul 12 10:05:37 nmbd[1871]: [2007/07/12 10:05:37, 0] nmbd/
    nmbd_incomingrequests.c118)
    Jul 12 10:05:37 nmbd[1871]: process_name_release_request: Attempt to
    release name DOMAIN<1d> from IP 192.168.11.72 on subnet 192.168.11.11
    being rejected as it is one of our names.


    -----------end error messages---------


    Here's the important part of my Samba config... also note, I've always
    used SWAT for configuration:

    # Samba config file created using SWAT
    # from 192.168.11.71 (192.168.11.71)
    # Date: 2007/07/06 17:22:18

    [global]
    workgroup = DOMAIN
    server string = Samba Server
    password server =
    log file = /var/log/samba/log.%m
    max log size = 250
    dns proxy = No

    [homes]
    comment = Home Directories
    read only = No
    browseable = No

    [printers]
    comment = All Printers
    path = /usr/spool/samba
    printable = Yes
    browseable = No
    ----------------------------------End samba config--------------------


    Again Thanks for any help provided!
    -David


  2. Re: Samba Config Help?

    On Jul 12, 9:01 am, "David C. Moody" wrote:
    > Hi Guys,
    >
    > I'm hoping you can help me. Sorry for such a long post.
    >
    > I think Samba is causing my server troubles. I used samba on 5.0.7
    > with no trouble at all. but on Openserver 6 I'm starting to get some
    > trouble.
    >
    > Here's my network setup, we do not have a Domain, do not really want a
    > domain at this time. We operate everything off of a Workgroup.
    > Basically all my users just telnet to the SCO machine to operate
    > programs off of SCO.
    >
    > I'm thinking about changing my Samba config to set local master,
    > preferred master & domain master all to "NO" to see if that stops the
    > errors. I just can't figure it out.
    >
    > any help at all will be greatly appreciated.
    >
    > I'm receiving alot of Samba error messages, repeated over and over
    > every day:
    > -----------
    > Jul 12 08:35:13 smbd[4985]: [2007/07/12 08:35:13, 0] lib/util_sock.c:
    > (258)
    > Jul 12 08:35:13 smbd[4985]: Failed to set socket option SO_KEEPALIVE
    > (Error Invalid argument)
    > Jul 12 08:35:13 smbd[4985]: [2007/07/12 08:35:13, 0] lib/util_sock.c:
    > (258)
    > Jul 12 08:35:13 smbd[4985]: Failed to set socket option TCP_NODELAY
    > (Error Invalid argument)
    > Jul 12 08:35:13 smbd[4985]: [2007/07/12 08:35:13, 0] lib/util_sock.c:
    > (1222)
    > Jul 12 08:35:13 smbd[4985]: getpeername failed. Error was Invalid
    > argument
    > Jul 12 08:35:13 smbd[4985]: [2007/07/12 08:35:13, 0] lib/util_sock.c:
    > (526)
    > Jul 12 08:35:13 smbd[4985]: read_data: read failure for 4 bytes to
    > client 192.168.11.67. Error = Connection reset by peer
    > Jul 12 08:54:34 smbd[5458]: [2007/07/12 08:54:34, 0] lib/util_sock.c:
    > (526)
    > Jul 12 08:54:34 smbd[5458]: read_data: read failure for 4 bytes to
    > client 192.168.11.64. Error = Connection reset by peer
    > Jul 12 09:03:27 smbd[5700]: [2007/07/12 09:03:27, 0] smbd/posix_acls.c:
    > (2447)
    > Jul 12 09:03:27 smbd[5700]: set_canon_ace_list: ACL type (file) is
    > invalid for set (Invalid argument).
    > Jul 12 09:03:27 smbd[5700]: [2007/07/12 09:03:27, 0] smbd/posix_acls.c:
    > (2447)
    > Jul 12 09:03:27 smbd[5700]: set_canon_ace_list: ACL type (file) is
    > invalid for set (Invalid argument).
    > Jul 12 09:04:07 smbd[5775]: [2007/07/12 09:04:07, 0] lib/util_sock.c:
    > (258)
    > Jul 12 09:04:07 smbd[5775]: Failed to set socket option SO_KEEPALIVE
    > (Error Invalid argument)
    > Jul 12 09:04:07 smbd[5775]: [2007/07/12 09:04:07, 0] lib/util_sock.c:
    > (258)
    > Jul 12 09:04:07 smbd[5775]: Failed to set socket option TCP_NODELAY
    > (Error Invalid argument)
    > Jul 12 09:04:07 smbd[5775]: [2007/07/12 09:04:07, 0] lib/util_sock.c:
    > (1222)
    > Jul 12 09:04:07 smbd[5775]: getpeername failed. Error was Invalid
    > argument
    > Jul 12 09:04:07 smbd[5775]: [2007/07/12 09:04:07, 0] lib/util_sock.c:
    > (526)
    > Jul 12 09:04:07 smbd[5775]: read_data: read failure for 4 bytes to
    > client 192.168.11.65. Error = Connection reset by peer
    > Jul 12 09:04:20 nmbd[1871]: [2007/07/12 09:04:20, 0] nmbd/
    > nmbd_become_lmb.c396)
    > Jul 12 09:04:20 nmbd[1871]: *****
    > Jul 12 09:04:20 nmbd[1871]:
    > Jul 12 09:04:20 nmbd[1871]: Samba name server HOLIDAY is now a local
    > master browser for workgroup DOMAIN on subnet 192.168.11.11
    > Jul 12 09:04:20 nmbd[1871]:
    > Jul 12 09:04:20 nmbd[1871]: *****
    > Jul 12 09:07:35 nmbd[1871]: [2007/07/12 09:07:35, 0] nmbd/
    > nmbd_incomingdgrams.c311)
    > Jul 12 09:07:35 nmbd[1871]: process_local_master_announce: Server
    > PIII-866X2 at IP 192.168.11.24 is announcing itself as a local master
    > browser for workgroup DOMAIN and we think we are master. Forcing
    > election.
    > Jul 12 09:07:35 nmbd[1871]: [2007/07/12 09:07:35, 0] nmbd/
    > nmbd_become_lmb.c149)
    > Jul 12 09:07:35 nmbd[1871]: *****
    > Jul 12 09:07:35 nmbd[1871]:
    > Jul 12 09:07:35 nmbd[1871]: Samba name server HOLIDAY has stopped
    > being a local master browser for workgroup DOMAIN on subnet
    > 192.168.11.11
    > Jul 12 09:07:35 nmbd[1871]:
    > Jul 12 09:07:35 nmbd[1871]: *****
    > Jul 12 09:07:54 nmbd[1871]: [2007/07/12 09:07:54, 0] nmbd/
    > nmbd_become_lmb.c396)
    > Jul 12 09:07:54 nmbd[1871]: *****
    > Jul 12 09:07:54 nmbd[1871]:
    > Jul 12 09:07:54 nmbd[1871]: Samba name server HOLIDAY is now a local
    > master browser for workgroup DOMAIN on subnet 192.168.11.11
    > Jul 12 09:07:54 nmbd[1871]:
    > Jul 12 09:07:54 nmbd[1871]: *****
    > Jul 12 09:14:28 smbd[1888]: [2007/07/12 09:14:28, 0] smbd/server.c:
    > (389)
    > Jul 12 09:14:28 smbd[1888]: open_sockets_smbd: accept: Protocol
    > error
    > Jul 12 09:48:33 smbd[5700]: [2007/07/12 09:48:33, 0] smbd/posix_acls.c:
    > (2447)
    > Jul 12 09:48:33 smbd[5700]: set_canon_ace_list: ACL type (file) is
    > invalid for set (Invalid argument).
    > Jul 12 09:48:33 smbd[5700]: [2007/07/12 09:48:33, 0] smbd/posix_acls.c:
    > (2447)
    > Jul 12 09:48:33 smbd[5700]: set_canon_ace_list: ACL type (file) is
    > invalid for set (Invalid argument).
    > Jul 12 10:00:51 smbd[5700]: [2007/07/12 10:00:51, 0] smbd/posix_acls.c:
    > (2447)
    > Jul 12 10:00:51 smbd[5700]: set_canon_ace_list: ACL type (file) is
    > invalid for set (Invalid argument).
    > Jul 12 10:00:51 smbd[5700]: [2007/07/12 10:00:51, 0] smbd/posix_acls.c:
    > (2447)
    > Jul 12 10:00:51 smbd[5700]: set_canon_ace_list: ACL type (file) is
    > invalid for set (Invalid argument).
    > Jul 12 10:05:37 nmbd[1871]: [2007/07/12 10:05:37, 0] nmbd/
    > nmbd_incomingrequests.c118)
    > Jul 12 10:05:37 nmbd[1871]: process_name_release_request: Attempt to
    > release name DOMAIN<1d> from IP 192.168.11.72 on subnet 192.168.11.11
    > being rejected as it is one of our names.
    >
    > -----------end error messages---------
    >
    > Here's the important part of my Samba config... also note, I've always
    > used SWAT for configuration:
    >
    > # Samba config file created using SWAT
    > # from 192.168.11.71 (192.168.11.71)
    > # Date: 2007/07/06 17:22:18
    >
    > [global]
    > workgroup = DOMAIN
    > server string = Samba Server
    > password server =
    > log file = /var/log/samba/log.%m
    > max log size = 250
    > dns proxy = No
    >
    > [homes]
    > comment = Home Directories
    > read only = No
    > browseable = No
    >
    > [printers]
    > comment = All Printers
    > path = /usr/spool/samba
    > printable = Yes
    > browseable = No
    > ----------------------------------End samba config--------------------
    >
    > Again Thanks for any help provided!
    > -David


    I guess my attempted reply got Google-Grouped. I'll try again.

    One thing you left off is the symptom that prompted the post. I take
    it some or all users are having trouble reaching some or all Samba
    printers?

    The "socket option failure" messages happen with an out-of-the-box
    install on OpenServer 6. I suspect that the global Socket Options
    should be something like "TCP_NODELAY=0 SO_KEEPALIVE=1 SO_SNDBUF=8192
    SO_RCVBUF=8192". It's not been convenient for me to try that, but in
    any event that's not causing your problem.

    What appears to be going on is a simple Samba configuration issue.
    Did you by chance drop the OpenServer 6 instance of Samba into the
    same network that formerly had the 5.0.7 instance using the latter's
    old Netbios name? That's what the process_name_release_request error
    suggests.

    Your redacted config settings are too abbreviated for more detailed
    diagnosis. For more help from this group or a Samba group, include
    all the settings under the SWAT Base Options, Security Options, and
    Browse Options (Basic View).

    --RLR


  3. Re: Samba Config Help?

    On Jul 13, 3:24 pm, ThreeStar wrote:
    >
    > I guess my attempted reply got Google-Grouped. I'll try again.
    >
    > One thing you left off is the symptom that prompted the post. I take
    > it some or all users are having trouble reaching some or all Samba
    > printers?
    >
    > The "socket option failure" messages happen with an out-of-the-box
    > install on OpenServer 6. I suspect that the global Socket Options
    > should be something like "TCP_NODELAY=0 SO_KEEPALIVE=1 SO_SNDBUF=8192
    > SO_RCVBUF=8192". It's not been convenient for me to try that, but in
    > any event that's not causing your problem.
    >
    > What appears to be going on is a simple Samba configuration issue.
    > Did you by chance drop the OpenServer 6 instance of Samba into the
    > same network that formerly had the 5.0.7 instance using the latter's
    > old Netbios name? That's what the process_name_release_request error
    > suggests.
    >
    > Your redacted config settings are too abbreviated for more detailed
    > diagnosis. For more help from this group or a Samba group, include
    > all the settings under the SWAT Base Options, Security Options, and
    > Browse Options (Basic View).
    >
    > --RLR- Hide quoted text -
    >
    > - Show quoted text -


    Thanks for your response. I appreciate you trying to help me as well.

    What prompted me posting, is that my server locks up every few weeks
    (about every 2 weeks). The only error messages I am getting are these
    Samba error messages. And by server locks up, I mean it is like the
    network card freezes and doesn't let anything in or out. Noone has
    complained about not being able to access resources, and all of our
    printers are IP printers so we print directly to them not through
    Samba.

    Yes this server did replace a Openserver5.0.7 setup with the same
    workgroup & name. But the 5.0.7 server is offline, and actually has
    now been converted to another 6.0 server with a different name. I
    haven't really config'd anything on the server, the only thing was it
    originally had interfaces as i01 or something like that and nothing
    would work, after removing that everything worked.

    my socket options is : TCP_NODELAY

    Here are my config options:
    Base Options
    workgroup: DOMAIN
    netbios name: HOLIDAY
    netbios aliases:
    server string: Samba Server
    interfaces:

    Security Options:
    security: USER
    auth methods:
    encrypt pw: Yes
    Client schannel: auto
    server schannel: auto
    password server:
    passdb backend: smbpasswd
    guest account: nouser
    invalid users:
    valid users:
    admin users:
    read list:
    write list:
    printer admin:
    hosts allow:
    hosts deny:
    preload modules:

    Browse Options:
    os level: 20
    preferred master: Auto
    local master: Yes
    domain master: Auto

    Thanks for any help!


  4. Re: Samba Config Help?

    On Jul 13, 2:23 pm, "David C. Moody" wrote:
    > On Jul 13, 3:24 pm, ThreeStar wrote:
    >
    >
    >
    >
    >
    > > I guess my attempted reply got Google-Grouped. I'll try again.

    >
    > > One thing you left off is the symptom that prompted the post. I take
    > > it some or all users are having trouble reaching some or all Samba
    > > printers?

    >
    > > The "socket option failure" messages happen with an out-of-the-box
    > > install on OpenServer 6. I suspect that the global Socket Options
    > > should be something like "TCP_NODELAY=0 SO_KEEPALIVE=1 SO_SNDBUF=8192
    > > SO_RCVBUF=8192". It's not been convenient for me to try that, but in
    > > any event that's not causing your problem.

    >
    > > What appears to be going on is a simple Samba configuration issue.
    > > Did you by chance drop the OpenServer 6 instance of Samba into the
    > > same network that formerly had the 5.0.7 instance using the latter's
    > > old Netbios name? That's what the process_name_release_request error
    > > suggests.

    >
    > > Your redacted config settings are too abbreviated for more detailed
    > > diagnosis. For more help from this group or a Samba group, include
    > > all the settings under the SWAT Base Options, Security Options, and
    > > Browse Options (Basic View).

    >
    > > --RLR- Hide quoted text -

    >
    > > - Show quoted text -

    >
    > Thanks for your response. I appreciate you trying to help me as well.
    >
    > What prompted me posting, is that my server locks up every few weeks
    > (about every 2 weeks). The only error messages I am getting are these
    > Samba error messages. And by server locks up, I mean it is like the
    > network card freezes and doesn't let anything in or out. Noone has
    > complained about not being able to access resources, and all of our
    > printers are IP printers so we print directly to them not through
    > Samba.
    >
    > Yes this server did replace a Openserver5.0.7 setup with the same
    > workgroup & name. But the 5.0.7 server is offline, and actually has
    > now been converted to another 6.0 server with a different name. I
    > haven't really config'd anything on the server, the only thing was it
    > originally had interfaces as i01 or something like that and nothing
    > would work, after removing that everything worked.
    >
    > my socket options is : TCP_NODELAY
    >
    > Here are my config options:
    > Base Options
    > workgroup: DOMAIN
    > netbios name: HOLIDAY
    > netbios aliases:
    > server string: Samba Server
    > interfaces:
    >
    > Security Options:
    > security: USER
    > auth methods:
    > encrypt pw: Yes
    > Client schannel: auto
    > server schannel: auto
    > password server:
    > passdb backend: smbpasswd
    > guest account: nouser
    > invalid users:
    > valid users:
    > admin users:
    > read list:
    > write list:
    > printer admin:
    > hosts allow:
    > hosts deny:
    > preload modules:
    >
    > Browse Options:
    > os level: 20
    > preferred master: Auto
    > local master: Yes
    > domain master: Auto
    >
    > Thanks for any help!


    Ah, well, in that case none of this matters. Sounds like a network
    card failure. Make sure you're using an up-to-date driver or try
    another NIC.

    I'm glad it's not causing problems but you should make sure that the
    "Holiday" entry associated with your prior server is unregistered from
    your workgroup/domain. See Samba or M$ documentation.

    Good luck!

    --RLR


+ Reply to Thread