Samba, Error Spamming

Tempest · 2012-02-01 01:35:52

So, I have Samba running on my server (which is using Arch, 64-bit), without any issues. It works fine, runs fine, and does what I need it to.

Except it keeps trying to do something more. My log files have thousands of entries like:

Jan 29 19:36:32 localhost smbd[26185]: [2012/01/29 19:36:32.943509,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:36:32 localhost smbd[26185]:   Can't become connected user!
Jan 29 19:36:32 localhost smbd[26186]: [2012/01/29 19:36:32.966109,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:36:32 localhost smbd[26186]:   Can't become connected user!
Jan 29 19:36:32 localhost smbd[26187]: [2012/01/29 19:36:32.977285,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:36:32 localhost smbd[26187]:   Can't become connected user!
Jan 29 19:36:32 localhost smbd[26188]: [2012/01/29 19:36:32.979339,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:36:32 localhost smbd[26188]:   Can't become connected user!
Jan 29 19:36:48 localhost smbd[26189]: [2012/01/29 19:36:48.664741,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:36:48 localhost smbd[26189]:   Can't become connected user!
Jan 29 19:36:49 localhost smbd[26190]: [2012/01/29 19:36:49.020482,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:36:49 localhost smbd[26190]:   Can't become connected user!
Jan 29 19:36:57 localhost smbd[26193]: [2012/01/29 19:36:57.601333,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:36:57 localhost smbd[26193]:   Can't become connected user!
Jan 29 19:36:58 localhost smbd[26194]: [2012/01/29 19:36:58.126317,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:36:58 localhost smbd[26194]:   Can't become connected user!
Jan 29 19:37:36 localhost smbd[26195]: [2012/01/29 19:37:36.554393,  0] smbd/service.c:970(make_connection_snum)
Jan 29 19:37:36 localhost smbd[26195]:   Can't become connected user!

Notice how the PID keeps going up. Also notice the time between events. It's doing this all the time!

Here's my smb.conf:

[global]
  workgroup = BEHEMOTH
  server string = %h server (Samba, Arch)
  dns proxy = no

  security = user
  valid users = +smb_user

  force create mode = 644
  force directory mode = 755

#=================== Share Definitions ====================
[Private]
  comment = Private Storage
  writable = yes
  path = /bulk/private/%u
  valid users = +priv_stor

[Public]
  comment = Public Storage
  writable = yes
  path = /bulk/public
  valid users = +pub_stor

[Media]
  comment = Multimedia and Programs
  path = /bulk/media
  valid users = +media_write, +media_read
  read list = +media_read
  write list = +media_write
  read only = yes

[Landing]
  comment = Temporary Landing
  path = /bulk/landing
  valid users = +smb_admin
  writable = yes

[Restoration]
  comment = Restoration Landing
  path = /bulk/restoration
  valid users = +smb_admin
  writable = yes

[Virtualization]
  comment = Virtualization Storage
  path = /bulk/virtualization
  valid users = +smb_admin
  writable = yes

[TSAN]
  comment = TSAN
  path = /bulk/tsan
  valid users = +smb_admin
  writable = yes
  force user = rtorrent
  browseable = no

Nice and simple, really. All groups exist. All directories they refer to exist. All the shares work like they're supposed to.

Here's some other spam from Samba in the log. I don't have a printer installed and I have nothing about printers in my smb.conf, so I have no idea what Samba is thinking:

Jan 31 20:32:21 localhost smbd[22570]: [2012/01/31 20:32:21.838819,  0] printing/print_cups.c:110(cups_connect)
Jan 31 20:32:21 localhost smbd[22570]:   Unable to connect to CUPS server localhost:631 - No such file or directory
Jan 31 20:32:21 localhost smbd[22541]: [2012/01/31 20:32:21.839212,  0] printing/print_cups.c:487(cups_async_callback)
Jan 31 20:32:21 localhost smbd[22541]:   failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL

I would love some help cleaning this up. I could probably look up a way to stop the error messages, but the fact that it's just spamming processes in the background is a little unsettling.

I can provide more configuration if necessary.

Edit: I just restarted Samba. There must have been an update. My issues are exactly the same as before, but now the line number in service.c is 962, not 970. Just thought it was worth mentioning.

Edit2: I searched service.c (of HEAD, maybe not what Arch builds with) and found the place the error is probably being generated. Unfortunately, Samba doesn't seem kind enough to dump which user can't become connected.

Last edited by Tempest (2012-02-01 01:46:12)

dschrute · 2012-02-01 02:56:24

Samba will try to load printers by default, even if there are none. Try adding

load printers = no

in the global section.

As for the "Can't become connected user..." error, I'm not sure, but as a guess I'd look at the share where you "force user = rtorrent" . Maybe try disabling that temporarily + see if the error goes away. Again, that's just a guess.

Tempest · 2012-02-01 15:11:50

I'll add the

load printers = no

part and see if that helps.

This problem has been haunting me for some time, since before the TSAN share existed (and certainly before the user was forced).

I should remind others that I can still access the TSAN share fine, and creating files there properly sets the owner to rtorrent:rtorrent.

Arch Linux

#1 2012-02-01 01:35:52

Samba, Error Spamming

#2 2012-02-01 02:56:24

Re: Samba, Error Spamming

#3 2012-02-01 15:11:50

Re: Samba, Error Spamming

Board footer