You are not logged in.
Hello, samba is running well, however it is spamming my logs with this:
Feb 21 15:09:21 alarmpi smbd[2155]: [2014/02/21 15:09:21.561919, 0] ../source3/lib/util_sock.c:423(open_socket_in)
Feb 21 15:09:21 alarmpi smbd[2155]: open_socket_in(): socket() call failed: Address family not supported by protocol
Feb 21 15:09:21 alarmpi smbd[2155]: [2014/02/21 15:09:21.563595, 0] ../source3/smbd/server.c:684(smbd_open_one_socket)
Feb 21 15:09:21 alarmpi smbd[2155]: smbd_open_once_socket: open_socket_in: Address family not supported by protocol
Feb 21 15:09:21 alarmpi smbd[2155]: [2014/02/21 15:09:21.590267, 0] ../source3/lib/util_sock.c:423(open_socket_in)
Feb 21 15:09:21 alarmpi smbd[2155]: open_socket_in(): socket() call failed: Address family not supported by protocol
Feb 21 15:09:21 alarmpi smbd[2155]: [2014/02/21 15:09:21.591488, 0] ../source3/smbd/server.c:684(smbd_open_one_socket)
Feb 21 15:09:21 alarmpi smbd[2155]: smbd_open_once_socket: open_socket_in: Address family not supported by protocol
Can you please tell me what to disable in smb.conf? Thank you
my smb.conf:
http://pastie.org/private/elqqxaiucf2ulgsaqsnww
Offline
My best guess would be missing ipv6 support. SystemD should load it (it always complains it cannot do that here gehehe ).
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
Is there any way to solve it without enabling ipv6? It caused me several problems when it was enabled.
It doesnt have to be solved as solved, changing log level should be fine.
Offline
A little googling suggests you can bind samba to specific interfaces, IPV4 only. So something like
bind interfaces only = yes
interfaces = 127.0.0.1 host_ip_address
Just be aware that if your IP changes you'd need to change the config. But I wonder if you have ipv6 completely disabled. I don't see those errors on my system and I don't use IPV6. Did you specifically disable it, or just never do anything to configure ipv6 ? If you're sure you don't need/want it I'd go back and turn it off explicitly. The archwiki tells you how
Offline
Probably a slightly nicer syntax:
bind interfaces only = yes
interfaces = lo eth0 wlan
Offline
Thank you, it looks like this is the solution.
Just be aware that if your IP changes you'd need to change the config. But I wonder if you have ipv6 completely disabled. I don't see those errors on my system and I don't use IPV6. Did you specifically disable it, or just never do anything to configure ipv6 ? If you're sure you don't need/want it I'd go back and turn it off explicitly. The archwiki tells you how
It's been a long time since I installed and configured this server, I only remember there were some problems with ipv6 and I somehow disabled it (I don't need it, there will be no IPv6 till 2017 in this location). But I dont know what did I do..
Offline
Thank you, it looks like this is the solution.
dschrute wrote:Just be aware that if your IP changes you'd need to change the config. But I wonder if you have ipv6 completely disabled. I don't see those errors on my system and I don't use IPV6. Did you specifically disable it, or just never do anything to configure ipv6 ? If you're sure you don't need/want it I'd go back and turn it off explicitly. The archwiki tells you how
It's been a long time since I installed and configured this server, I only remember there were some problems with ipv6 and I somehow disabled it (I don't need it, there will be no IPv6 till 2017 in this location). But I dont know what did I do..
Can't you just make it listen on 0.0.0.0 or is that a stupid idea?
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline
Do you mean something like interfaces = 0.0.0.0? I think that brebs' solution is pretty much the same.
Offline
Do you mean something like interfaces = 0.0.0.0? I think that brebs' solution is pretty much the same.
Not exactly. If the interface name changes, this will not be affected by that change. Brebs solution does. But that could be intended though.
fs/super.c : "Self-destruct in 5 seconds. Have a nice day...\n",
Offline