• Bug#265577: Acknowledgement (samba: nmbd shuts down frequently)

    From David Clymer@1:229/2 to All on Tue Aug 17 17:50:08 2004
    From: [email protected]

    Below is my config, if it's of any use.

    /etc/samba/smb.conf:

    [global]
    panic action = /usr/share/samba/panic-action %d
    log level = 4
    workgroup = SERVERS
    netbios name = JEKYL
    server string = "CSB Router, Name, & Proxy Server"
    hosts allow = 192.168. 10.0.1.2 EXCEPT 192.168.10.2 192.168.2.
    log file = /var/log/samba/%m.log
    max log size = 1000
    syslog = 0
    security = user
    encrypt passwords = true
    passdb backend = tdbsam guest
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    interfaces = 192.168.10.0/24 127.0.0.1
    bind interfaces only = yes
    local master = no
    preferred master = no
    domain master = no
    wins support = yes
    dns proxy = yes
    name resolve order = wins host lmhosts bcast

    I am only running nmbd on this box, not smbd. This was not a clean
    install of sarge; I upgraded from woody.

    The shutdowns happen on intervals < 15 minutes. I had a cron job running
    to restart it every 15 minutes, but it was still failing within that
    time period. I now run a cron job that checks for the nmbd process every
    5 minutes and starts it if it is not running. I have not seen any
    failures within that interval, yet.

    -davidc


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Steve Langasek@1:229/2 to David Clymer on Wed Aug 18 10:00:15 2004
    From: [email protected]

    On Tue, Aug 17, 2004 at 11:19:55AM -0400, David Clymer wrote:
    Below is my config, if it's of any use.

    /etc/samba/smb.conf:

    [global]
    panic action = /usr/share/samba/panic-action %d
    log level = 4
    workgroup = SERVERS
    netbios name = JEKYL
    server string = "CSB Router, Name, & Proxy Server"
    hosts allow = 192.168. 10.0.1.2 EXCEPT 192.168.10.2 192.168.2.
    log file = /var/log/samba/%m.log
    max log size = 1000
    syslog = 0
    security = user
    encrypt passwords = true
    passdb backend = tdbsam guest
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    interfaces = 192.168.10.0/24 127.0.0.1
    ^^^^^^^^^^^^^^^

    This is not a valid interface line. Please change this to one of the
    accepted values as documented in smb.conf, and let us know whether the
    problem goes away.

    Thanks,
    --
    Steve Langasek
    postmodern programmer

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.4 (GNU/Linux)

    iD8DBQFBIwblKN6ufymYLloRAp8TAJsF93j2tbJ2G8txZAh0Ws5iiVLfTgCgspg5 xFG4IuYwuRifSFm6gv6woOo=
    =vk4k
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From David Clymer@1:229/2 to All on Wed Aug 18 15:30:10 2004
    From: [email protected]

    Thus quoth Steve Langasek:
    To: David Clymer <[email protected]>, [email protected]
    From: Steve Langasek <[email protected]>
    Subject: Re: Bug#265577: Acknowledgement (samba: nmbd shuts down frequently)

    On Tue, Aug 17, 2004 at 11:19:55AM -0400, David Clymer wrote:
    Below is my config, if it's of any use.

    /etc/samba/smb.conf:

    [global]
    panic action = /usr/share/samba/panic-action %d
    log level = 4
    workgroup = SERVERS
    netbios name = JEKYL
    server string = "CSB Router, Name, & Proxy Server"
    hosts allow = 192.168. 10.0.1.2 EXCEPT 192.168.10.2 192.168.2.
    log file = /var/log/samba/%m.log
    max log size = 1000
    syslog = 0
    security = user
    encrypt passwords = true
    passdb backend = tdbsam guest
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    interfaces = 192.168.10.0/24 127.0.0.1
    ^^^^^^^^^^^^^^^

    This is not a valid interface line. Please change this to one of the accepted values as documented in smb.conf, and let us know whether the problem goes away.


    Man smb.conf indicates (if I read it correctly) that it is indeed a valid interface specification. Perhaps the docs need updating? Anyway, I've
    changed the line in question to:

    interfaces = 192.168.10.1 127.0.0.1

    I'll let you know if problems persist. Thanks for the suggestion.

    -davidc


    man smb.conf (exerpt):

    --------------8<--------------

    interfaces (G)
    This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NBT
    traffic. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127.0.0.1 that are
    broadcast capable.

    The option takes a list of interface strings. Each string can be in any of the following forms:

    o a network interface name (such as eth0). This may include shell-like wildcards so eth* will match any interface starting with the sub-
    string "eth"

    o an IP address. In this case the netmask is determined from the list of interfaces obtained from the kernel

    o an IP/mask pair.

    o a broadcast/mask pair.

    The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decimal form.

    The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS's normal hostname reso-
    lution mechanisms.

    Default: interfaces = # all active interfaces except 127.0.0.1 that are broadcast capable

    Example: interfaces = # This would configure three network interfaces corresponding to the eth0 device and IP addresses 192.168.2.10 and
    192.168.3.10. The netmasks of the latter two interfaces would be set to 255.255.255.0. eth0 192.168.2.10/24 192.168.3.10/255.255.255.0

    -------------->8--------------



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Steve Langasek@1:229/2 to David Clymer on Wed Aug 18 22:50:09 2004
    From: [email protected]

    On Wed, Aug 18, 2004 at 09:13:00AM -0400, David Clymer wrote:
    Thus quoth Steve Langasek:
    To: David Clymer <[email protected]>, [email protected]
    From: Steve Langasek <[email protected]>
    Subject: Re: Bug#265577: Acknowledgement (samba: nmbd shuts down frequently)

    On Tue, Aug 17, 2004 at 11:19:55AM -0400, David Clymer wrote:
    Below is my config, if it's of any use.

    /etc/samba/smb.conf:

    [global]
    panic action = /usr/share/samba/panic-action %d
    log level = 4
    workgroup = SERVERS
    netbios name = JEKYL
    server string = "CSB Router, Name, & Proxy Server"
    hosts allow = 192.168. 10.0.1.2 EXCEPT 192.168.10.2 192.168.2.
    log file = /var/log/samba/%m.log
    max log size = 1000
    syslog = 0
    security = user
    encrypt passwords = true
    passdb backend = tdbsam guest
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    interfaces = 192.168.10.0/24 127.0.0.1
    ^^^^^^^^^^^^^^^

    This is not a valid interface line. Please change this to one of the accepted values as documented in smb.conf, and let us know whether the problem goes away.

    Man smb.conf indicates (if I read it correctly) that it is indeed a valid interface specification. Perhaps the docs need updating?

    192.168.10.0 is neither an IP address nor a broadcast address, it's a
    network address, which is not one of the supported values. If
    192.168.10.1 is the IP address of this machine, I think it should give
    better results.

    Thanks,
    --
    Steve Langasek
    postmodern programmer

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.4 (GNU/Linux)

    iD8DBQFBI7rNKN6ufymYLloRAoWpAJ9fWo6uRt2/twZaNMk5iHcTcPehQACeOkfo kuIVobzPrDzwFqVaf2x25s8=
    =B6P3
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From David Clymer@1:229/2 to All on Wed Aug 18 23:30:12 2004
    From: [email protected]

    Thus quoth Steve Langasek:
    To: David Clymer <[email protected]>
    Cc: [email protected]
    From: Steve Langasek <[email protected]>
    Subject: Re: Bug#265577: Acknowledgement (samba: nmbd shuts down frequently)

    On Wed, Aug 18, 2004 at 09:13:00AM -0400, David Clymer wrote:
    Thus quoth Steve Langasek:
    To: David Clymer <[email protected]>, [email protected]
    From: Steve Langasek <[email protected]>
    Subject: Re: Bug#265577: Acknowledgement (samba: nmbd shuts down frequently)

    On Tue, Aug 17, 2004 at 11:19:55AM -0400, David Clymer wrote:
    Below is my config, if it's of any use.

    /etc/samba/smb.conf:

    [global]
    panic action = /usr/share/samba/panic-action %d
    log level = 4
    workgroup = SERVERS
    netbios name = JEKYL
    server string = "CSB Router, Name, & Proxy Server"
    hosts allow = 192.168. 10.0.1.2 EXCEPT 192.168.10.2 192.168.2.
    log file = /var/log/samba/%m.log
    max log size = 1000
    syslog = 0
    security = user
    encrypt passwords = true
    passdb backend = tdbsam guest
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    interfaces = 192.168.10.0/24 127.0.0.1
    ^^^^^^^^^^^^^^^

    This is not a valid interface line. Please change this to one of the accepted values as documented in smb.conf, and let us know whether the problem goes away.

    Man smb.conf indicates (if I read it correctly) that it is indeed a valid interface specification. Perhaps the docs need updating?

    192.168.10.0 is neither an IP address nor a broadcast address, it's a
    network address, which is not one of the supported values. If
    192.168.10.1 is the IP address of this machine, I think it should give
    better results.


    Understood, thanks. 192.168.10.1 is the IP of the machine in question,
    and thus far, I have not experienced further problems. Again, thanks for
    the help/clarification.

    Apparently, requirements for the interfaces directive have increased in stringency since version 2.2. Perhaps a short mention of this could be
    added to the README?

    -davidc

    PS. Out of curiosity, why should a network address vs. an IP or broadcast address matter if given in conjunction with a netmask? Shouldn't any address matching 192.168.10.1/24 also match 192.168.10.0/24?



    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)