Bug 550356
| Summary: | samba not publishing shares, very likely due to service nmb dying following successful boot | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Lipps <paul.lipps> |
| Component: | samba | Assignee: | Guenther Deschner <gdeschner> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | azelinka, davidben, eagleton, gdeschner, K_osforever, larryoleary, mstuff, orion, paul.lipps, ssorce, wulfsdale |
| Target Milestone: | --- | Flags: | paul.lipps:
needinfo-
|
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 486231 | Environment: | |
| Last Closed: | 2011-04-06 15:23:15 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Paul Lipps
2009-12-24 17:32:16 UTC
I can confirm comment #18. This bug is still prevalent in F12 on my x86_64 wired desktop. Failure rate is about 90%. This problem affects BOTH smbd and nmbd. When running smbd without nmbd it will also fail to start. I believe it is caused by the network not being fully initialized before the smb and nmb daemons are started. More specifically in my case nmbd and smbd are jumping the gun, they are started before IP4 is configured, i.e. before the "Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started" line in messages. The "set NETWORKWAIT=yes in /etc/sysconfig/network" solution solves the problem, by waiting until the network is fully up before proceeding, but is not very elegant or efficient. nmbd and smbd should either (1) not be triggered/started until completion of network initialization or (2) have the ability to add and bind interfaces as they come on line during the boot process. Same problem here, agree with comment #18. Filed upsream bug to get nmbd to stay up and load interfaces dynamically. In the meantime: /etc/NetworkManager/dispatcher.d/91-nmbd: #!/bin/bash if [ -x /usr/bin/logger ]; then LOGGER="/usr/bin/logger -s -p user.notice -t NetworkManagerDispatcher" else LOGGER=echo fi service=nmbd if [ -n "$1" ] && [ $2 == "up" ]; then if /sbin/chkconfig ${service} then if /sbin/service ${service} status >& /dev/null then $LOGGER "${service} is running, restart" /sbin/service ${service} restart else $LOGGER "${service} is not running, start" /sbin/service ${service} start fi fi fi # Only shut down if there are no networks up if [ -n "$1" ] && [ $2 == "down" ] && [ -z "`/usr/bin/nm-tool | grep '^State: *connected'`" ]; then $LOGGER "stopping ${service}" /sbin/service ${service} stop fi Should be a usable work around. Should this Bug be closed Dup as Bug 486231 has been re-opened? (In reply to comment #2) > Same problem here, agree with comment #18. Filed upsream bug to get nmbd to > stay up and load interfaces dynamically. Orion, what is the ticket number or link to upstream bug report? thanks, W. See the external bug link on this bug. I am not sure which of these bugs to add comments, so commenting on both. I have regular problems with SMB running, and NMB being dead, from my PC. I am running Fedora 12 x86_64, samba-3.4.5-55.fc12.x86_64 When I check NMB, I notice it randomly ends up dead: $ service nmb status nmbd dead but pid file exists I have NM managing my WIRED eth0 network, it's listed as 'System eth0'. It does pick up IP address from DHCP (IP fixed via DHCP). But I've also noticed NMB will sometimes die randomly while my PC is running. Do I need to add a log file from my PC also? This issue still exists on Fedora 13. This was expected, I am just confirming it. I will add update to this when I get back to my desktop, as I have changed my setup noted above, under Fedora 13, and still having issues with nmbd crashing randomly. I moved my desktop back to using the 'network' service, configured static IP address for eth0, to get around this issue of NMB service not working. It seemed the main problem for me was getting IPs via DHCP would cause nmb to fail on start. I am not sure if the DHCP IP address was also causing nmb service to randomly die, but I haven't noticed that problem occur since the change. Still an issue with the recent samba version ? If so, please provide more debugging information. I believe that all necessary information is already in this bug. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Yes this is still an issue with a fully updated Fedora 13 i386 installation. I would be glad to provide log and backtrace information from my current installation if someone could provide some info on how to provide it. I think I can locate the samba log file, not sure how to obtain a backtrace though. Well, It isn't an issue for me anymore (F13 x86_64 static IP on Network Manager) Actually I think it was fixed quite a while ago.. Makes me wonder why the status is 'new' on this report. *** This bug has been marked as a duplicate of bug 486231 *** |