I'm not entirely certain that this was actually fixed on lucid, despite
the changelog entry added to 2:3.4.3-2ubuntu2 ...
I look at the package branch at that revision, and it does not install
/etc/network/if-up.d/samba. Likewise, now that I see bug #836849
reported, it would appear that what
I don't know why this file is being installed in later versions. The
reason it's not installed for lucid is seen here:
samba (2:3.4.5~dfsg-2ubuntu2) lucid; urgency=low
* Switch smbd and nmbd over to upstart jobs, to ensure nmbd starts reliably
after the network is up. LP: #523868.
*
I also had this problem of occasional hangs during boot, when networking is
configured on ubuntu karmic.
The hangs still occurred, even though I disabled samba via update-rc.d. Found
out that samba-related
stuff is called in /etc/dhcp3/dhclient-enter-hooks.d/samba. The following patch
may be
Hi Steve. I observed that my Ubuntu 10.04 system would wait for an
indefinite period at start-up if there was no available non-loopback
interface available. I presumed this was a bug related to the upstart
job for nmbd.
--
nmbd dies on startup when network interfaces are not up yet
I have performed a controlled experiment and can't replicate the
behaviour, so it must have been a mis-diagnosis. Sorry.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Based on the above, perhaps the upstart script for samba / nmbd has a
bug as the script will stop the system from booting if no net adapters
come up. A preferred behaviour would be for nmbd to fail to start but
let the machine boot.
Better still, if nmbd could have the same behaviour that smbd
It does not stop the system from booting. nmbd is not required for a
system to boot.
The upstart job is implemented to accurately declare nmbd's dependency
on having a working network interface available. If you think nmbd
should start even when no network is available, that is a non-trivial
There was bogus adapter information in /etc/network/interfaces . I
removed that. Consequently, my computer failed to boot as the samba /
nmbd script was waiting for a network event which would never happen.
The only adapter listed in /etc/network/interfaces was lo, which would
not generate the
Myself and a friend have both had to use Samba with IP addresses, until
I found that by restarting nmbd, name resolution works again. (Ubuntu
10.04).
My machine automatically logs in. I don't use the network manager
applet; I have DHCPd running on my server and use bridging.
Perhaps nmbd needs
Hi Nick,
Does this mean that the first network interface that comes up on your
system is not a broadcast interface?
We don't have a way to detect this from /etc/init/nmbd.conf. If you have
a point-to-point interface coming up before your broadcast interfaces,
that would definitely account for
Right, let me precise a bit more what I’m doing.
I have a home network with various W$ and Ubuntu PCs + a Mandriva (2007)
server.
This server is used for sharing files, printing, scanning, photo/videos web
pages, ssh…
Due to variety of OSes, file sharing between W$ PCs and this server uses SMB
On Mon, May 17, 2010 at 05:16:47PM -, Nicolas M wrote:
Now, with Ubuntu, here is what I get, with standard nmbd and smbd conf
files :
- At boot time : only smbd started.
- nmbd must be started manually or samba restarted when network is
up to have nmbd +
Following your guidelines, I think I understand better how nmbd is
behaving.
nmbd is started after a user logs in, and if the network-manager is
running.
In fact, as I'm setting a server, I configured the Wifi so that it could
connect with wpa_supplicant at the end of boot, but I did not use the
Excuse me to enter this thread lately, but something looks weird to me
here.
I've just experienced the same issue with Lucid, trying to set up samba server,
on a Wifi hooked laptop.
With current samba-server package, result after Lucid boots is:
- smbd is running
- nmbd is not running
leading
On Sun, May 16, 2010 at 12:28:45PM -, Nicolas M wrote:
= So my question here: why having a different startup condition for
smbd and nmbd, as both daemons need to be running for samba to operate ?
Because:
- nmbd is only needed for operations in some environments, so smbd should
not
Ok Steve, not being a Samba guru, was just trying to figure this out.
After having browsed through the well known Using Samba
(http://www.samba.org/samba/docs/using_samba/toc.html), I did not get
this understanding of smbd versus nmbd.
I've been using Samba like that (smbd+nmbd, with or without
Why do you think you need nmbd to start at all when you don't have a
network?
I think you need to be explicit here about what problem you were seeing
when using the standard nmbd.conf.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You
With Lucid i have the same proble. Resolved with file described below:
location of file:
/etc/network/if-up.d/samba
#! /bin/sh
# Reload samba when an interface comes up, to allow it to start
# listening on new addresses.
set -e
# Don't bother to restart samba server when lo is configured.
if [
No, you do *not* have the same problem. Please file a new bug report.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
I just installed the latest 10.04 (including updates) and the same
problem happened to me.
In case someone might find this information useful,
this is how I fixed it:
In file /etc/init/smbd.conf
change this:
start on local-filesystems
into this:
start on (local-filesystems and
This has just cropped up on my PC too (Xubuntu 9.10), after installing
lirc, hangs on bootup just before the login screen (slim). (smb.conf is
vanilla). Wouldn't work in recovery mode, told me about the nmbd pid but
wouldn't let me do anything about it so CTRL-ALT-DEL was necessary.
Samba
** Bug watch added: Debian Bug tracker #576415
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576415
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which
@Christian Perrier
If you search for fixed in in this page, you'll find:
This bug was fixed in the package samba - 2:3.4.3-2ubuntu2
Then you go to:
https://launchpad.net/ubuntu/+source/samba/2:3.4.3-2ubuntu2
And you'll find:
On Mon, Apr 05, 2010 at 08:58:19AM +0200, Christian PERRIER wrote:
This has just cropped up on my PC too (Xubuntu 9.10), after installing
lirc, hangs on bootup just before the login screen (slim). (smb.conf is
vanilla). Wouldn't work in recovery mode, told me about the nmbd pid but
This has just cropped up on my PC too (Xubuntu 9.10), after installing
lirc, hangs on bootup just before the login screen (slim). (smb.conf is
vanilla). Wouldn't work in recovery mode, told me about the nmbd pid but
wouldn't let me do anything about it so CTRL-ALT-DEL was necessary.
Samba version
I believe this script is the key point.
/etc/network/if-up.d/samba
After I add this:
-
#!/bin/sh
exit 0
-
The could not access PID file for nmbd disappeared.
--
nmbd dies on startup when network interfaces are not up yet
On Sat, Jan 23, 2010 at 10:20:19PM -, ripeart wrote:
Hello, this is affecting me also, rendering my server unusable.
This bug is fixed in both karmic and lucid. If you have not yet installed
the updated samba package from karmic-updates, you should do so. If you
have the current
have you tried: sudo /etc/init.d/samba start? This is not meant for a
production server we're only in Alpha 2. I have to issue the previous
command in order for my laptop to be seen by my other computers. the
bookmark idea was to see other computers. I hope this helps.
--
nmbd dies on startup
Hello, this is affecting me also, rendering my server unusable. I have
the same issues as everyone above however with the additional that my
system stops at the error. I cannot log in locally, nor can I ssh into
the box. I can however ping the box. Is there anyway to get past this
error so I can
This bug was fixed in the package samba - 2:3.4.3-2ubuntu2
---
samba (2:3.4.3-2ubuntu2) lucid; urgency=low
* debian/rules, debian/samba.if-up: allow NetworkManager as a recognized
address
family... it's obviously /not/ an address family, but it's what gets
sent when using
Steve asked for me to attach 'log level = 3' logs.
I did clean install of alpha2, added the above to /etc/samba/smb.conf and
rebooted. after login there is no nmbd process.
** Attachment added: log level 3 log.nmbd
http://launchpadlibrarian.net/38115707/log.nmbd
--
nmbd dies on startup
** Attachment added: log.smbd corresponding to comment 65 log.nmbd
http://launchpadlibrarian.net/38115727/log.smbd
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Is anyone still able to reproduce this problem in lucid? I haven't been
able to reproduce it, so I wonder if this wasn't ultimately an eglibc
(getaddrinfo) bug that's been fixed, and the extra handling of nmbd is
unnecessary now.
--
nmbd dies on startup when network interfaces are not up yet
** Changed in: samba (Ubuntu Lucid)
Milestone: lucid-alpha-2 = lucid-alpha-3
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba
finaly!
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
This bug was fixed in the package samba - 2:3.4.0-3ubuntu5.3
---
samba (2:3.4.0-3ubuntu5.3) karmic-proposed; urgency=low
* debian/samba.if-up: allow NetworkManager as a recognized address
family... it's obviously /not/ an address family, but it's what gets
sent when using
** Tags added: verification-done
** Tags removed: verification-needed
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
I COnfirm that this upgrade worked ok...nmbd does not dies anymore...
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
Confirmed its fixed the startup issue in 3.4.0-3ubuntu5
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Hi...i have 3.4.0-3ubuntu5.1 and this issue is not solved at all...!!!
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
I can also confirm that while I'm running 3.4.0-3ubuntu5.1 the issue hasn't
been solved either.
After booting, running /etc/init.d/samba status shows nmbd not running.
On Tue, Jan 5, 2010 at 10:22 AM, razor7 mar...@mgscreativa.com wrote:
Hi...i have 3.4.0-3ubuntu5.1 and this issue is not
On Tue, Jan 05, 2010 at 04:04:16PM -, thebrotherofasis wrote:
I can also confirm that while I'm running 3.4.0-3ubuntu5.1 the issue hasn't
been solved either.
It's not supposed to have been solved in 3.4.0-3ubuntu5.1. The fix is in
3.4.0-3ubuntu5.3, present in karmic-proposed.
--
Steve
** Changed in: samba (Ubuntu Karmic)
Status: Fix Committed = Fix Released
** Changed in: samba (Ubuntu Karmic)
Status: Fix Released = Fix Committed
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug
on my system the process starts but remains in zombie state
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Hi guys...how should I know if i have this fix installed or not? I can
not see it in my update manager list...and Samba still doesn't work at
startup
Thanks a lot!
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug
** Changed in: ubuntu-release-notes
Status: Fix Released = Fix Committed
** Changed in: ubuntu-release-notes
Status: Fix Committed = Confirmed
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification
** Changed in: ubuntu-release-notes
Status: Confirmed = Fix Released
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
This might be somehow related, though it's about samba stopping randomly -
rather than not starting at all:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/498734
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug
I installed this update and is seems to fix the problem. When are we
going to see this fix get transfered from -proposed to -recomended?
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a
skyhard,
We normally allow 7 days for regression testing in -proposed before
copying to -updates. Do you run into bug #426267, that Bane describes
above?
Bane, regarding bug #426267 - was this working for you in Ubuntu 9.10
prior to the update?
--
nmbd dies on startup when network interfaces
No, I didn't run into that bug. Just to add I have the amd64 version of
karmic
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
Steve, yes it worked.
On Wed, Dec 16, 2009 at 7:35 PM, skyhard miran.merl...@gmail.com
wrote:
No, I didn't run into that bug. Just to add I have the amd64 version of
karmic
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received
nmbd is now starting OK but now I have this problem since the update:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/426267
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member
Update accepted into -proposed, please test:
samba (2:3.4.0-3ubuntu5.3) karmic-proposed; urgency=low
* debian/samba.if-up: allow NetworkManager as a recognized address
family... it's obviously /not/ an address family, but it's what gets
sent when using NM, so we'll cope for now.
--
Ok, thanks. It turns out the only thing that's needed in order to
reproduce this problem is to have an empty /etc/resolv.conf; somehow my
earlier testing didn't turn this up, but now that I have this I can
reproduce the error regardless of the samba config.
Which let me find the problem with the
** Description changed:
Binary package hint: samba
After installation with the daily build (20091027.2) ubuntu server i386 cd
there is no nmbd running on my system. The logfile tells me that the daemons
was startet but there is no process. The /var/run/samba/nmbd.pid file is still
there
** Changed in: samba (Ubuntu Lucid)
Milestone: lucid-alpha-1 = lucid-alpha-2
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba
DHCP vs. static IP does not completely explain this; I've been entirely
unable to reproduce the problem even when testing nmbd startup with all
interfaces deliberately shut down, and nmbd continues to start up fine.
Can someone who's able to reproduce the problem also give me their
Samba never starts for me during boot, se every time want to use the network I
have to start the samba service manually!
Here are the contents of the files
/etc/resolv.conf:
# Generated by NetworkManager
domain telemach.net
search telemach.net
nameserver 213.143.65.11
nameserver 213.143.65.12
Here are mine:
/etc/resolv.conf:
# Generated by NetworkManager
nameserver 208.67.222.222
nameserver 208.67.220.220
/etc/nsswitch.conf:
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed,
skyhard,
On Wed, Dec 09, 2009 at 10:19:38PM -, skyhard wrote:
Samba never starts for me during boot, se every time want to use the
network I have to start the samba service manually!
The bug being tracked here is specifically related to the nmbd server not
starting. Can you please
/var/log/samba/log.nmbd:
[2009/12/07 11:44:01, 0] nmbd/nmbd.c:854(main)
nmbd version 3.4.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/12/07 11:44:01, 0] nmbd/nmbd.c:693(open_sockets)
[2009/12/07 12:16:09, 0] nmbd/nmbd.c:854(main)
nmbd version 3.4.0 started.
nmbd lof after changing loglevel to 3
[2009/12/09 20:10:55, 0] nmbd/nmbd.c:854(main)
nmbd version 3.4.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/12/09 20:10:55, 2] lib/tallocmsg.c:106(register_msg_pool_usage)
Registered MSG_REQ_POOL_USAGE
[2009/12/09 20:10:55,
martin,
On Wed, Dec 09, 2009 at 10:26:30PM -, razor7 wrote:
hosts: files mdns4_minimal [NOTFOUND=return] wins dns mdns4 #changed
to avoid OpenDNS issues
The use of 'wins' here suggests you may have a different bug. Please
provide the /etc/samba/smb.conf and
skyhard, your log.nmbd doesn't appear to have come from a system with
'log level = 3' set?
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
(without the additional logging verbosity, we get no information about
why nmbd has exited, making it useless for debugging)
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
razor7,
Thanks - the one last piece of information I need from you is your
/etc/samba/smb.conf.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Attachment added: razor7 smb.conf
http://launchpadlibrarian.net/36644611/smb.conf
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Attachment added: razor7 log.nmbd
http://launchpadlibrarian.net/36644827/log.nmbd
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Here you are...all the files you requested.
To add more weirdness, i had to restart my PC after changing log level,
and to upload log.nmbd file, but surprise! nmbd war working...jajaja
¿¿??, so i restarted again...and nmbd stopped working again.
Best regards!
--
nmbd dies on startup when
** Attachment added: razor7 nsswitch.conf
http://launchpadlibrarian.net/36644906/nsswitch.conf
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Attachment added: razor7 resolv.conf
http://launchpadlibrarian.net/36644909/resolv.conf
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I have the problem with an AMD single core.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs
Hi folks...i don't think this issue is processor dependant...Best
regards!
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
I just wanted to add what I know.
On a Celeron D 2.53, 650i, 4 GB, I did not have this issue, or at least I
didn't notice it.
When I switched over to AMD X2 4800+, 780G, 2 GB, I began to experience this
issue.
For what it's worth, if I reboot warm, the issue only occurs about half the
time.
still not working on mine, keep having to manually restart samba after
every boot in Karmic. Jaunty worked fine in this area.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of
The same to me...not solved at all!
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing
Update was done. Bug not solved.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Accepted into karmic-proposed. Please test and submit feedback here.
Thank you!
** Tags added: verification-needed
** Changed in: samba (Ubuntu Karmic)
Status: In Progress = Fix Committed
--
nmbd dies on startup when network interfaces are not up yet
scratch my comment 2 above.
I changed runlevel to 19. seemed to work once, but doesn't work any
more.
samba still dies on startup and i have to load manually each time with
sudo /etc/init.d/samba start
--
nmbd dies on startup when network interfaces are not up yet
I confirm the bug...the PID file is there, but no process at all using
ps -e
restarting samba says this start-stop-daemon: warning: failed to kill
1507: No such process (1507 is supposed to be nmbd)
Please advise to solve this annoyance!
Thanks a lot!
--
nmbd dies on startup when network
I've fixed this on mine.
Loaded BUM, and changed runlevel from 20 to 19 for samba.
Now, it loads up fine for me on boot up.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of
Yes. I tried incrementing the log level in smb.conf and rebooting, but
the information logged remains the same, until reaching log level 8 or
higher. Then nmbd suddenly appears to start normally. There appears to
be something racy going on here.
--
nmbd dies on startup when network interfaces
For a possible workaround, maybe we could look at this bug (note: not
the same problem, and no longer available in Launchpad):
https://lists.ubuntu.com/archives/ubuntu-server-
bugs/2009-May/012893.html
Personally I would prefer something in /etc/network/if-*.d/ which would
also serve users
The uploaded package adds a lot of new files (such as exports/*.syms and
various Makefiles and *.pc). The actual change looks fine to me, if
samba's init script does the right thing on start if smbd is already
running (which seems to be the case from visual inspection).
I rejected the package,
Can someone who is seeing this problem in Ubuntu 9.10 please send the
following:
- a copy of /var/log/samba/log.nmbd showing the boot-time failure
- a copy of your /etc/samba/smb.conf
Here you go. I set log level = 3 (possibly overkill) to make an error
show up, for otherwise nmbd seems to
And here the smb.conf (not changed AFAIK except for log level = 3)
** Attachment added: smb.conf
http://launchpadlibrarian.net/35955631/smb.conf
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because
Thanks, looks like this is the key bit of the log:
[2009/11/22 22:31:50, 3]
../lib/util/util_net.c:56(interpret_string_addr_internal)
interpret_string_addr_internal: getaddrinfo failed for name 0.0.0.0 [Address
family for hostname not supported]
--
nmbd dies on startup when network
** Tags added: iso-testing
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
For what it's worth:
I have installed 9.10 more than 15 times. Most of the times I lost sharing
and could not be seen
on the network. I could restart Samba and the network would be ok; until the
next boot. I could not get Open as administrator to work, nor any of the
context menu extra stuff.
** Changed in: samba (Ubuntu Karmic)
Status: In Progress = Fix Released
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
** Changed in: samba (Ubuntu Karmic)
Status: Fix Released = In Progress
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
Is there any workaround available?
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
The workaround, as stated in the release notes, is to manually run 'sudo
service samba restart' after boot.
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team,
I'm uploading a possible fix for this to karmic-proposed, but there's
already another SRU in progress for samba so it shouldn't actually be
accepted for testing until we have confirmation of the fix for bug
#462626. So if someone is in a position to help test that (Windows 7
domain
We should fix this differently in karmic vs. lucid; for lucid we should
convert samba to native upstart jobs, then we only need one nmbd job
that is started once at the correct time instead of having to try
multiple times to start the init script.
This is a more intrusive fix, though, so I'm not
** Also affects: samba (Ubuntu Lucid)
Importance: High
Assignee: Steve Langasek (vorlon)
Status: In Progress
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
While I'm fairly certain that the uploaded fix is correct, surprisingly,
I've been unable to reproduce the original problem despite forcibly
disabling my network interface. Can someone who is seeing this problem
in Ubuntu 9.10 please send the following:
- a copy of /var/log/samba/log.nmbd
Same problem here. is there a fix somewhere ?
Max
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
where can I get this fix?
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
1 - 100 of 103 matches
Mail list logo