[Samba] smbd errors in syslog - how to get rid of them? - Samba

This is a discussion on [Samba] smbd errors in syslog - how to get rid of them? - Samba ; Listmates, I know the following are harmless, but how do I keep them from filling up my syslog? log level = 03. They still appear with log level = 1. Any thoughts? The logs: Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: [Samba] smbd errors in syslog - how to get rid of them?

  1. [Samba] smbd errors in syslog - how to get rid of them?

    Listmates,

    I know the following are harmless, but how do I keep them from filling
    up my syslog? log level = 03. They still appear with log level = 1. Any
    thoughts? The logs:

    Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    lib/util_sock.c:get_peer_addr(1232)
    Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was
    Transport endpoint is not connected
    Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    lib/util_sock.c:get_peer_addr(1232)
    Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was
    Transport endpoint is not connected
    Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    lib/access.c:check_access(327)
    Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    lib/util_sock.c:get_peer_addr(1232)
    Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was
    Transport endpoint is not connected
    Jan 23 22:01:30 bonza smbd[16474]: Denied connection from (0.0.0.0)
    Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    lib/util_sock.c:get_peer_addr(1232)
    Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was
    Transport endpoint is not connected
    Jan 23 22:01:30 bonza smbd[16474]: Connection denied from 0.0.0.0
    Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    lib/util_sock.c:write_data(562)
    Jan 23 22:01:30 bonza smbd[16474]: write_data: write failure in
    writing to client 192.168.7.143. Error Connection reset by peer
    Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    lib/util_sock.c:send_smb(769)
    Jan 23 22:01:30 bonza smbd[16474]: Error writing 5 bytes to client.
    -1. (Connection reset by peer)


    --
    David C. Rankin, J.D., P.E.
    Rankin Law Firm, PLLC
    510 Ochiltree Street
    Nacogdoches, Texas 75961
    Telephone: (936) 715-9333
    Facsimile: (936) 715-9339
    www.rankinlawfirm.com
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  2. Re: [Samba] smbd errors in syslog - how to get rid of them? {solved}

    David C. Rankin wrote:
    > Listmates,
    >
    > I know the following are harmless, but how do I keep them from
    > filling up my syslog? log level = 03. They still appear with log level =
    > 1. Any thoughts? The logs:
    >
    > Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    > lib/util_sock.c:get_peer_addr(1232)
    > Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was


    smb ports = 139 in the Globals section of smb.conf

    --
    David C. Rankin, J.D., P.E.
    Rankin Law Firm, PLLC
    510 Ochiltree Street
    Nacogdoches, Texas 75961
    Telephone: (936) 715-9333
    Facsimile: (936) 715-9339
    www.rankinlawfirm.com
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  3. Re: [Samba] smbd errors in syslog - how to get rid of them? {solved}

    David C. Rankin schrieb:
    > David C. Rankin wrote:
    >> Listmates,
    >>
    >> I know the following are harmless, but how do I keep them from
    >> filling up my syslog? log level = 03. They still appear with log level
    >> = 1. Any thoughts? The logs:
    >>
    >> Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    >> lib/util_sock.c:get_peer_addr(1232)
    >> Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was

    >
    > smb ports = 139 in the Globals section of smb.conf


    Are there any disadvantages when setting this options? I know that
    Windowsclients can't communicate over 445 any more but is there a
    disadvantage?

    Niki
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

  4. Re: [Samba] smbd errors in syslog - how to get rid of them? {solved}

    Niki Hammler wrote:
    > David C. Rankin schrieb:
    >> David C. Rankin wrote:
    >>> Listmates,
    >>>
    >>> I know the following are harmless, but how do I keep them from
    >>> filling up my syslog? log level = 03. They still appear with log
    >>> level = 1. Any thoughts? The logs:
    >>>
    >>> Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0]
    >>> lib/util_sock.c:get_peer_addr(1232)
    >>> Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was

    >>
    >> smb ports = 139 in the Globals section of smb.conf

    >
    > Are there any disadvantages when setting this options? I know that
    > Windowsclients can't communicate over 445 any more but is there a
    > disadvantage?
    >
    > Niki
    >

    Not that I have experienced. We have about 12 windows boxes working
    happily from 2 linux boxes and after added the port and shutting down
    all the chatter ofer 445, I think it works better!

    --
    David C. Rankin, J.D., P.E.
    Rankin Law Firm, PLLC
    510 Ochiltree Street
    Nacogdoches, Texas 75961
    Telephone: (936) 715-9333
    Facsimile: (936) 715-9339
    www.rankinlawfirm.com
    --
    To unsubscribe from this list go to the following URL and read the
    instructions: https://lists.samba.org/mailman/listinfo/samba

+ Reply to Thread