Find the answer to your Linux question:
Results 1 to 4 of 4
Hello All: I am running Samba on a Fedora 17 server and it seems to be working; however, I am wondering if I have a problem with the way I ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Sep 2012
    Posts
    2

    SAMBA log files with strange errors


    Hello All:
    I am running Samba on a Fedora 17 server and it seems to be working; however, I am wondering if I have a problem with the way I set it up that could be adversely affecting either performance or security (or something else). There are messages in the log files that I don't understand and cannot seem to learn about via Googling for hours.

    Here is my smb.conf followed by some log file examples...
    Code:
    [global]
            workgroup = MYENTERPRISE
            netbios name = Oudebok
            server string = LAN Fileserver
            log file = /var/log/samba/%m.log
            max log size = 50
            security = user
            encrypt passwords = yes
            browseable = yes
    #       hosts allow = 172.16.1.
    # Modified to allow for VPN connections to Samba shares
            hosts allow = 172.16.1. 10.123.214. localhost
            bind interfaces only = true
            interfaces = eth0 172.16.1. tap0 10.123.214. lo 127.0.0.1
    # Modified to eliminate getpeername error
            smb ports = 139
    # Added to ensure that Oudebok is the primary source for browseable Samba resources
            local master = Yes
            preferred master = Yes
            os level = 17
    
    [homes]
            comment = Oudebok Home Directories
            valid users = %S
            read only = No
            browseable = No
    #       guest ok = No
    
    [printers]
            comment = All Printers
            path = /usr/spool/samba
            printable = Yes
            browseable = No
    
    [FILESHARE]
            comment = Oudebok Fileshare Directory
            path = /fileshare
            read only = No
    Code:
    tail -20 /var/log/samba/log.nmbd
    [2012/12/21 08:47:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 08:52:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 08:57:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 09:02:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 09:07:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 09:12:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 09:17:02,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 09:22:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 09:27:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    [2012/12/21 09:32:12,  0] nmbd/nmbd_packets.c:759(queue_query_name)
      queue_query_name: interface 1 has NULL IP address !
    Can anyone here help me figure out what is going on with these errors, or what else I can post to investigate this?
    Thanks in advance!
    Tom

  2. #2
    Linux User
    Join Date
    Dec 2011
    Location
    Turtle Island West
    Posts
    344
    Samba can be very verbose in it's logging. That's what samba log files look like. You should see mine going back to 2005. Anything is a reason to log. Nothing is a reason to log. From the looks of your log dump, samba is just saying "Hey! I'm here!" every 5 minutes on the dot because it has nothing to do. Samba will make an empty log file like:
    Code:
    -rw-r----- 1 root root      0 Oct  4  2006 log.190.48.73.169
    -rw-r----- 1 root root      0 Dec 10  2006 log.219.241.126.52
    -rw-r----- 1 root root      0 Aug 26  2006 log.219.74.62.206
    -rw-r----- 1 root root      0 Oct  5  2006 log.220.209.25.102
    -rw-r----- 1 root root      0 Jul  7  2006 log.222.147.240.105
    -rw-r----- 1 root root      0 Jul  7  2006 log.222.149.41.45
    just from a ping on it's port.

    Anyway, that's my best guess.

  3. #3
    Linux Guru
    Join Date
    Nov 2007
    Posts
    1,754
    Samba's nmbd process replicates NetBIOS-type broadcasts/name resolution for "Windows for Workgroups." Your log is nmbd telling you that one of your interfaces (NIC's) has a "null" IP address. Whether or not this is valid may depend on your config. Try pasting your error message into Google. The "lo" and 127.0.0.1 are redundant - I'd remove the "lo" based on the bug report.

  4. #4
    Just Joined!
    Join Date
    Sep 2012
    Posts
    2
    Thanks to both of you for your replies. Although I did not see the Bug Report when first searching for help via Google, I followed your link to it and I understand now that it was the same scenario for me. I removed "lo" as you suggested and (after restarting smbd and nmbd) the logging of that particular error has stopped. So I noticed this error or warning in the log after restarting:

    Code:
    [2012/12/27 08:02:35,  0] nmbd/nmbd.c:66(terminate)
      Got SIGTERM: going down...
    [2012/12/27 08:02:35,  0] nmbd/nmbd.c:861(main)
      nmbd version 3.6.6-92.fc17 started.
      Copyright Andrew Tridgell and the Samba Team 1992-2011
    [2012/12/27 08:02:35,  0] nmbd/nmbd.c:889(main)
      standard input is not a socket, assuming -D option
    ...which I pasted into Google and spent a couple of hours sifting through pages where it doesn't appear to be relevant, just part of a log or screen capture. Is it reasonable for me to conclude that this entry ("standard input is not a socket, assuming -D option") is unimportant?

    Thanks again for your assistance!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •