Comments on: The specified network name is no longer available samba

By: Nicholas

Nicholas — Thu, 03 Nov 2011 04:24:57 +0000

This can be caused by having no space left on your samba server causing logging to fail alongside your patience.

Look for a message like:

tdb(/var/cache/samba/locking.tdb): expand_file write of 8192 bytes failed (No space left on device)

By: hm2k

hm2k — Fri, 12 Mar 2010 12:15:54 +0000

Turns out, once I had tried updating again, I had to readd my user using smbpasswd –a

Never mind.

By: hm2k

hm2k — Fri, 12 Mar 2010 11:46:02 +0000

I’ve now tried rolling back to 3.0.30 and restarting the smb service, but I still get the following error:

[root@blade log]# tail -f samba
[2010/03/12 12:46:06, 0] lib/util_sock.c:set_socket_options(237)
Unknown socket option SO_SNBUF
[2010/03/12 12:46:06, 0] lib/util_sock.c:set_socket_options(237)
Unknown socket option TCP_NODELAY_SO_RCVBUF
[2010/03/12 12:46:06, 0] lib/util_sock.c:set_socket_options(237)
Unknown socket option SO_SNBUF
[2010/03/12 12:46:09, 0] lib/util_sock.c:set_socket_options(237)
Unknown socket option TCP_NODELAY_SO_RCVBUF
[2010/03/12 12:46:09, 0] lib/util_sock.c:set_socket_options(237)
Unknown socket option SO_SNBUF

I’m not sure what to do at the moment…

By: hm2k

hm2k — Fri, 12 Mar 2010 11:32:58 +0000

Yesterday I restarted my server after updating my packages.

It installed the following:

samba i386 3.0.33-0.18.el4_8.1 installed 30 M
samba-common i386 3.0.33-0.18.el4_8.1 installed 20 M

When I restarted I found I had the same problem as I do here, even though this is now a later version than the above.

I’m going to try and roll back to the 3.0.30 version to see if that fixes it and then go from there…