FS#36178 - [samba] fails to initialize properly at startup

Attached to Project: Arch Linux
Opened by Alexander (heaven) - Wednesday, 17 July 2013, 06:07 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 06 August 2013, 06:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
The problem — can't browse samba shares until restart the nmbd and smbd services.
Tried to enable NetworkManager-wait-online.service but no luck.

Additional info:
1. My PC is connected to the network using networkmanager and Linksys AE3000 usb wi-fi adapter which makes the network start up a bit delayed.
2. Samba is configured to be a master browser.
3. The config and log files are attached.

Steps to reproduce:
1. Use networkmanager with wi-fi connection
2. Reboot
3. Try to browse samba shares in dolphin

Also may be useful:
LU-10-4 — is my router (also with Samba on board)

$ sudo killall -HUP smbd nmbd
Before:
Got SIGHUP dumping debug info.
[2013/07/17 09:00:55, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.1.103: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = LU-10-4
ARCH 40819a03 (Samba Server)
LU-10-4 40849a03 (Samba 3.0.28a)
[2013/07/17 09:00:55, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.110.1: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = UNKNOWN
ARCH 40819a03 (Samba Server)
[2013/07/17 09:00:55, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.118.1: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = UNKNOWN
ARCH 40819a03 (Samba Server)

After services restart:
Got SIGHUP dumping debug info.
[2013/07/17 09:06:28, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.1.103: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = ARCH
ARCH 408c9a03 (Samba Server)
LU-10-4 40819a03 (Samba 3.0.28a)
[2013/07/17 09:06:28, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.110.1: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = ARCH
ARCH 408c9a03 (Samba Server)
[2013/07/17 09:06:28, 0] ../source3/nmbd/nmbd_workgroupdb.c:276(dump_workgroups)
dump_workgroups()
dump workgroup on subnet 192.168.118.1: netmask= 255.255.255.0:
WORKGROUP(1) current master browser = ARCH
ARCH 408c9a03 (Samba Server)


$ smbtree -N
Before:
WORKGROUP
\\LU-10-4 Samba 3.0.28a
\\LU-10-4\IPC$ IPC Service (Samba 3.0.28a)

After restart the services:
WORKGROUP
\\LU-10-4 Samba 3.0.28a
\\LU-10-4\IPC$ IPC Service (Samba 3.0.28a)
\\ARCH Samba Server
\\ARCH\Video
\\ARCH\Other
\\ARCH\IPC$ IPC Service (Samba Server)
   smb.conf (0.6 KiB)
   nmbd.log (4.3 KiB)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Tuesday, 06 August 2013, 06:35 GMT
Reason for closing:  Not a bug
Comment by Alexander (heaven) - Wednesday, 17 July 2013, 06:09 GMT
BTW, had exactly the same problem with wicd and if I am not wrong with wired connection also.
Comment by Tobias Powalowski (tpowa) - Monday, 05 August 2013, 18:36 GMT
Well you need to setup your network correctly, so this is not a samba bug at all.
networkmanager has a wait-for-online service, netctl has a waiting function too, or use plain systemd service files to wait for a certain network device.
Comment by Alexander (heaven) - Tuesday, 06 August 2013, 06:31 GMT
  • Field changed: Percent Complete (100% → 0%)

Description:
The problem — can't browse samb...
...
Tried to enable NetworkManager-wait-online.service but no luck.
Comment by Tobias Powalowski (tpowa) - Tuesday, 06 August 2013, 06:34 GMT
I tell you once again get your network configured properly and don't bug me that this is a samba bug.
I'll not open this again. If networkmanager does not work for you open a bug against this or try my mentioned things above with netctl or systemd directly.

Loading...