Linux Questions

2414 readers

20 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

stay on topic
be nice (no name calling)
do not post long blocks of text such as logs
do not delete your posts
only post questions (no information posts)

Tips for giving and receiving help

be as clear and specific
say thank you if a solution works
verify your solutions before posting them as facts.

Any rule violations will result in disciplinary actions

founded 2 years ago

MODERATORS

possiblylinux127@lemmy.zip

What the f*** is wrong with Samba? (lemmy.zip)

submitted 3 weeks ago* (last edited 3 weeks ago) by hodgepodgin@lemmy.zip to c/linuxquestions@lemmy.zip

6 comments fedilink hide all child comments

Every now and then my Samba share stops working.

$ smbclient -U sambauser '\\192.168.12.11\Apartment'
do_connect: Connection to 192.168.12.11 failed (Error NT_STATUS_CONNECTION_REFUSED)

This is incredibly annoying, since it happens somewhat frequently too. I restart the container, with no fix. It might be client-side, but I'm boggled by how that could even occur. There are no logs in systemd for smbd. The firewall is disabled.

/etc/samba/smb.conf: https://pastebin.com/HNgw8YcV

you are viewing a single comment's thread
view the rest of the comments

[–] phanto@lemmy.ca 11 points 3 weeks ago (1 children)

This is kind of embarrassing, but I had a bunch of samba issues that went away when I made a "touch heartbeat.txt" on the mount every three minutes in my crontab. It was timing out and not re-establishing the connection reliably, so screw it. Never stops sending a miniscule bit of data every few minutes. Solved. Been running that way for like five years!

I also "fixed" a slow memory leak on a process by restarting the process every night at 1am in my crontab too! I'm the worst kind of admin.

[–] hodgepodgin@lemmy.zip 5 points 3 weeks ago

I think it has something to do with KDE not killing smbnotifier processes. If I kill the Samba daemon, I notice a ton of TCP traffic as the processes try to reset connections, then eventually terminating. If I then start the daemon again, those processes disappear and I can access the share through Dolphin.