nmbd job fails to start on boot

[Nathanel Titane]

Binary package hint: samba

Samba fails to start on boot to enable remote file access on ubuntu and windows.

I was able to fix the nmbd startup issue on natty and maverick!

It has to do with the init scrip at /etc/init/nmbd.conf

The start line needs to state start on local-filesystems ONLY!

The loopback ethernet interfaces start too late to satisfy the chronological dependency for nmbd to load as process...

Thus, /etc/init/nmbd.conf content should be:

description "NetBIOS name server"
author "Steve Langasek <email address hidden>"

start on (local-filesystems)
stop on runlevel [!2345]

expect fork
respawn

pre-start script
 mkdir -p /var/run/samba

 [ -f /etc/samba/smb.conf ] || { stop; exit 0; }

 install -o root -g root -m 755 -d /var/run/samba
 NMBD_DISABLED=`testparm -s --parameter-name='disable netbios' 2>/dev/null`

 [ "x$NMBD_DISABLED" = xYes ] && { stop; exit 0; }

 exit 0
end script

exec nmbd -D

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: samba 2:3.5.8~dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Mon Apr 4 17:46:02 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 nautilus 1:2.32.2.1-0ubuntu11.1
 gvfs 1.7.3-0ubuntu2
SambaClientRegression: Yes
SourcePackage: samba
UpgradeStatus: No upgrade log present (probably fresh install)

[Clint Byrum (clint-fewbar)]

Cypher2, thanks for taking the time to file this bug report and help us make Ubuntu better.

The nmbd.conf you pasted here is not the current one from natty.

The current one has this as its start condition:

start on (local-filesystems and net-device-up IFACE!=lo)

This means it will be started when any interface *except* lo is configured. Since nmbd is only used for announcing your address to other computers, this makes at least some sense in that it will start nmbd when a real network interface is available.

I'm not sure I understand then what it is you want to change. Can you please explain what you expect to happen, and what actually happens?

Thanks!

Marking Incomplete pending response.

[Nathanel Titane (nathanel.titane)]

The one I posted is the fixed version, without the "and net-device-up
IFACE!=lo"

go figure why, but since maverick.. it's been the only way nmbd has been
able to start on boot for me...

when the "and net-device-up IFACE!=lo" is present, only smbd starts and i am
unable to view the network computers or access their shares as samba
requires both smbd and nmbd to be operationnal to function.... removing that
upstart dependency has fixed it for me without any further bugs or issues to
report...

I guess it's simply unnecessary in the config?

Samba used to work damn fine for me up until maverick...

On Sat, Apr 9, 2011 at 6:23 PM, Clint Byrum <email address hidden> wrote:

> Cypher2, thanks for taking the time to file this bug report and help us
> make Ubuntu better.
>
> The nmbd.conf you pasted here is not the current one from natty.
>
> The current one has this as its start condition:
>
> start on (local-filesystems and net-device-up IFACE!=lo)
>
> This means it will be started when any interface *except* lo is
> configured. Since nmbd is only used for announcing your address to other
> computers, this makes at least some sense in that it will start nmbd
> when a real network interface is available.
>
> I'm not sure I understand then what it is you want to change. Can you
> please explain what you expect to happen, and what actually happens?
>
> Thanks!
>
> Marking Incomplete pending response.
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/750786
>
> Title:
> nmbd job fails to start on boot
>
> Status in “samba” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: samba
>
> Samba fails to start on boot to enable remote file access on ubuntu
> and windows.
>
> I was able to fix the nmbd startup issue on natty and maverick!
>
> It has to do with the init scrip at /etc/init/nmbd.conf
>
> The start line needs to state start on local-filesystems ONLY!
>
> The loopback ethernet interfaces start too late to satisfy the
> chronological dependency for nmbd to load as process...
>
> Thus, /etc/init/nmbd.conf content should be:
>
>
> description "NetBIOS name server"
> author "Steve Langasek <email address hidden>"
>
> start on (local-filesystems)
> stop on runlevel [!2345]
>
> expect fork
> respawn
>
> pre-start script
> mkdir -p /var/run/samba
>
> [ -f /etc/samba/smb.conf ] || { stop; exit 0; }
>
> install -o root -g root -m 755 -d /var/run/samba
> NMBD_DISABLED=`testparm -s --parameter-name='disable netbios'
> 2>/dev/null`
>
> [ "x$NMBD_DISABLED" = xYes ] && { stop; exit 0; }
>
> exit 0
> end script
>
> exec nmbd -D
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: samba 2:3.5.8~dfsg-1ubuntu1
> ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
> Uname: Linux 2.6.38-7-generic x86_64
> Architecture: amd64
> Date: Mon Apr 4 17:46:02 2011
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
> ProcEnviron:
> LANGUAGE=en_CA:en
> LANG=en_CA.UTF-8
> SHELL=/bin/bas...

[Clint Byrum (clint-fewbar)]

Excerpts from Cypher2's message of Sun Apr 10 06:48:36 UTC 2011:
> The one I posted is the fixed version, without the "and net-device-up
> IFACE!=lo"
>
> go figure why, but since maverick.. it's been the only way nmbd has been
> able to start on boot for me...
>
> when the "and net-device-up IFACE!=lo" is present, only smbd starts and i am
> unable to view the network computers or access their shares as samba
> requires both smbd and nmbd to be operationnal to function.... removing that
> upstart dependency has fixed it for me without any further bugs or issues to
> report...
>
> I guess it's simply unnecessary in the config?
>
> Samba used to work damn fine for me up until maverick...

Thats interesting. Samba was converted to upstart in lucid and had the same
start condition then.

I wonder if you wouldn't mind booting with the kernel option '--verbose' and
posting the contents of /var/log/boot.log with your start condition, and with
the original one?

One thing that I have seen with smbd is that it "starts" but respawns rapidly
until the loopback interface comes up. The test I describe above will determine
if nmbd is doing that as well.

>
> On Sat, Apr 9, 2011 at 6:23 PM, Clint Byrum <email address hidden> wrote:
>
> > Cypher2, thanks for taking the time to file this bug report and help us
> > make Ubuntu better.
> >
> > The nmbd.conf you pasted here is not the current one from natty.
> >
> > The current one has this as its start condition:
> >
> > start on (local-filesystems and net-device-up IFACE!=lo)
> >
> > This means it will be started when any interface *except* lo is
> > configured. Since nmbd is only used for announcing your address to other
> > computers, this makes at least some sense in that it will start nmbd
> > when a real network interface is available.
> >
> > I'm not sure I understand then what it is you want to change. Can you
> > please explain what you expect to happen, and what actually happens?
> >
> > Thanks!
> >
> > Marking Incomplete pending response.
> >
> > ** Changed in: samba (Ubuntu)
> > Status: New => Incomplete
> >
> > --
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> > https://bugs.launchpad.net/bugs/750786
> >
> > Title:
> > nmbd job fails to start on boot
> >
> > Status in “samba” package in Ubuntu:
> > Incomplete
> >
> > Bug description:
> > Binary package hint: samba
> >
> > Samba fails to start on boot to enable remote file access on ubuntu
> > and windows.
> >
> > I was able to fix the nmbd startup issue on natty and maverick!
> >
> > It has to do with the init scrip at /etc/init/nmbd.conf
> >
> > The start line needs to state start on local-filesystems ONLY!
> >
> > The loopback ethernet interfaces start too late to satisfy the
> > chronological dependency for nmbd to load as process...
> >
> > Thus, /etc/init/nmbd.conf content should be:
> >
> >
> > description "NetBIOS name server"
> > author "Steve Langasek <email address hidden>"
> >
> > start on (local-filesystems)
> > stop on runlevel [!2345]
> >
> > expect fork
> > respawn
> >
> > pre-start script
> > mkdir -p /var/run/samba
> >
> > [ -f /etc/sa...

[Nathanel Titane (nathanel.titane)]

alright.. i'll revert back to the original config and verbose it...

On Sun, Apr 10, 2011 at 11:10 AM, Clint Byrum <email address hidden> wrote:

> Excerpts from Cypher2's message of Sun Apr 10 06:48:36 UTC 2011:
> > The one I posted is the fixed version, without the "and net-device-up
> > IFACE!=lo"
> >
> > go figure why, but since maverick.. it's been the only way nmbd has been
> > able to start on boot for me...
> >
> > when the "and net-device-up IFACE!=lo" is present, only smbd starts and i
> am
> > unable to view the network computers or access their shares as samba
> > requires both smbd and nmbd to be operationnal to function.... removing
> that
> > upstart dependency has fixed it for me without any further bugs or issues
> to
> > report...
> >
> > I guess it's simply unnecessary in the config?
> >
> > Samba used to work damn fine for me up until maverick...
>
> Thats interesting. Samba was converted to upstart in lucid and had the same
> start condition then.
>
> I wonder if you wouldn't mind booting with the kernel option '--verbose'
> and
> posting the contents of /var/log/boot.log with your start condition, and
> with
> the original one?
>
> One thing that I have seen with smbd is that it "starts" but respawns
> rapidly
> until the loopback interface comes up. The test I describe above will
> determine
> if nmbd is doing that as well.
>
> >
> > On Sat, Apr 9, 2011 at 6:23 PM, Clint Byrum <email address hidden> wrote:
> >
> > > Cypher2, thanks for taking the time to file this bug report and help us
> > > make Ubuntu better.
> > >
> > > The nmbd.conf you pasted here is not the current one from natty.
> > >
> > > The current one has this as its start condition:
> > >
> > > start on (local-filesystems and net-device-up IFACE!=lo)
> > >
> > > This means it will be started when any interface *except* lo is
> > > configured. Since nmbd is only used for announcing your address to
> other
> > > computers, this makes at least some sense in that it will start nmbd
> > > when a real network interface is available.
> > >
> > > I'm not sure I understand then what it is you want to change. Can you
> > > please explain what you expect to happen, and what actually happens?
> > >
> > > Thanks!
> > >
> > > Marking Incomplete pending response.
> > >
> > > ** Changed in: samba (Ubuntu)
> > > Status: New => Incomplete
> > >
> > > --
> > > You received this bug notification because you are a direct subscriber
> > > of the bug.
> > > https://bugs.launchpad.net/bugs/750786
> > >
> > > Title:
> > > nmbd job fails to start on boot
> > >
> > > Status in “samba” package in Ubuntu:
> > > Incomplete
> > >
> > > Bug description:
> > > Binary package hint: samba
> > >
> > > Samba fails to start on boot to enable remote file access on ubuntu
> > > and windows.
> > >
> > > I was able to fix the nmbd startup issue on natty and maverick!
> > >
> > > It has to do with the init scrip at /etc/init/nmbd.conf
> > >
> > > The start line needs to state start on local-filesystems ONLY!
> > >
> > > The loopback ethernet interfaces start too late to satisfy the
> > > chronological dependency for nmbd to load as process...
> > >
> > > Thus, /etc/init/nmbd.conf content ...

[Nathanel Titane (nathanel.titane)]

Here is boot.log with default:
-------------------------------------------------
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
fsck from util-linux-ng 2.17.2
udevd[424]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/51-android.rules:1

/dev/sda1: clean, 178236/15269888 files, 3541805/61049344 blocks
init: ureadahead-other main process (761) terminated with status 4

init: Failed to spawn network-manager main process: unable to execute: No
such file or directory

 * Starting AppArmor profiles 
[ OK ]
 * Starting Kernel Oops catching service kerneloops  * Stopping
System V initialisation compatibility[ OK ]
 * Starting System V runlevel compatibility[ OK ]
 * Starting CPU interrupts balancing daemon[ OK ]
 * Starting ACPI daemon[ OK ]
 * Starting save kernel messages[ OK ]
 * Starting automatic crash report generation[ OK ]
 * Starting anac(h)ronistic cron[ OK ]
 * Starting regular background program processing daemon[ OK ]
 * Starting deferred execution scheduler[ OK ]

[ OK ]
speech-dispatcher disabled; edit /etc/default/speech-dispatcher
 * Starting the Winbind daemon winbind 
-----------------------------------------------------------------------------------

On Sun, Apr 10, 2011 at 12:00 PM, Nathanel Titane <<email address hidden>
> wrote:

> alright.. i'll revert back to the original config and verbose it...
>
>
> On Sun, Apr 10, 2011 at 11:10 AM, Clint Byrum <email address hidden> wrote:
>
>> Excerpts from Cypher2's message of Sun Apr 10 06:48:36 UTC 2011:
>> > The one I posted is the fixed version, without the "and net-device-up
>> > IFACE!=lo"
>> >
>> > go figure why, but since maverick.. it's been the only way nmbd has been
>> > able to start on boot for me...
>> >
>> > when the "and net-device-up IFACE!=lo" is present, only smbd starts and
>> i am
>> > unable to view the network computers or access their shares as samba
>> > requires both smbd and nmbd to be operationnal to function.... removing
>> that
>> > upstart dependency has fixed it for me without any further bugs or
>> issues to
>> > report...
>> >
>> > I guess it's simply unnecessary in the config?
>> >
>> > Samba used to work damn fine for me up until maverick...
>>
>> Thats interesting. Samba was converted to upstart in lucid and had the
>> same
>> start condition then.
>>
>> I wonder if you wouldn't mind booting with the kernel option '--verbose'
>> and
>> posting the contents of /var/log/boot.log with your start condition, and
>> with
>> the original one?
>>
>> One thing that I have seen with smbd is that it "starts" but respawns
>> rapidly
>> until the loopback interface comes up. The test I describe above will
>> determine
>> if nmbd is doing that as well.
>>
>> >
>> > On Sat, Apr 9, 2011 at...

[Nathanel Titane (nathanel.titane)]

Actually, I'M sorry... please disregard the previous log... it had a typo
and didn't even load up...

Here's the good default one:

--------------------------------------------
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
udevd[432]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/51-android.rules:1

fsck from util-linux-ng 2.17.2
/dev/sda1: clean, 178242/15269888 files, 3541919/61049344 blocks
init: ureadahead-other main process (756) terminated with status 4

init: Failed to spawn network-manager main process: unable to execute: No
such file or directory

 * Starting AppArmor profiles 
[ OK ]
 * Stopping Flush boot log to disk[ OK ]
-----------------------------------------------------------------------

Pay attention tho the "init: Failed to spawn network-manager main process:
unable to execute: No such file or directory" around the end....

On Sun, Apr 10, 2011 at 12:10 PM, Nathanel Titane <<email address hidden>
> wrote:

> Here is boot.log with default:
> -------------------------------------------------
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ..

[Nathanel Titane (nathanel.titane)]

And here is the modified upstart containing only th elocal FSs dep.
---------------------------------------------------------------------------------------------------
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
fsck from util-linux-ng 2.17.2
udevd[429]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/51-android.rules:1

/dev/sda1: clean, 178247/15269888 files, 3542118/61049344 blocks
init: ureadahead-other main process (757) terminated with status 4

init: Failed to spawn network-manager main process: unable to execute: No
such file or directory

 * Starting AppArmor profiles 
[ OK ]
------------------------------------------------------------------------------------------------

On Sun, Apr 10, 2011 at 12:14 PM, Nathanel Titane <<email address hidden>
> wrote:

> Actually, I'M sorry... please disregard the previous log... it had a typo
> and didn't even load up...
>
> Here's the good default one:
>
> --------------------------------------------
> Begin: Loading essential drivers ... done.
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ..

[Chuck Short (zulcss)]

Can you attach your /var/log/samba/log.nmbd as well?

Thanks
chuck

[Nathanel Titane (nathanel.titane)]

On Sun, Apr 10, 2011 at 12:39 PM, Chuck Short <email address hidden>wrote:

> Can you attach your /var/log/samba/log.nmbd as well?
>
> Thanks
> chuck
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/750786
>
> Title:
> nmbd job fails to start on boot
>
> Status in “samba” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: samba
>
> Samba fails to start on boot to enable remote file access on ubuntu
> and windows.
>
> I was able to fix the nmbd startup issue on natty and maverick!
>
> It has to do with the init scrip at /etc/init/nmbd.conf
>
> The start line needs to state start on local-filesystems ONLY!
>
> The loopback ethernet interfaces start too late to satisfy the
> chronological dependency for nmbd to load as process...
>
> Thus, /etc/init/nmbd.conf content should be:
>
>
> description "NetBIOS name server"
> author "Steve Langasek <email address hidden>"
>
> start on (local-filesystems)
> stop on runlevel [!2345]
>
> expect fork
> respawn
>
> pre-start script
> mkdir -p /var/run/samba
>
> [ -f /etc/samba/smb.conf ] || { stop; exit 0; }
>
> install -o root -g root -m 755 -d /var/run/samba
> NMBD_DISABLED=`testparm -s --parameter-name='disable netbios'
> 2>/dev/null`
>
> [ "x$NMBD_DISABLED" = xYes ] && { stop; exit 0; }
>
> exit 0
> end script
>
> exec nmbd -D
>
> ProblemType: Bug
> DistroRelease: Ubuntu 11.04
> Package: samba 2:3.5.8~dfsg-1ubuntu1
> ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
> Uname: Linux 2.6.38-7-generic x86_64
> Architecture: amd64
> Date: Mon Apr 4 17:46:02 2011
> InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
> ProcEnviron:
> LANGUAGE=en_CA:en
> LANG=en_CA.UTF-8
> SHELL=/bin/bash
> RelatedPackageVersions:
> nautilus 1:2.32.2.1-0ubuntu11.1
> gvfs 1.7.3-0ubuntu2
> SambaClientRegression: Yes
> SourcePackage: samba
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/750786/+subscribe
>

--
*TND*esigns | Graphic & Industrial Design Solutions Inc.

514 . 583 . 7386

[Tommaso Cucinotta (cucinotta)]

Hi,

a part of this problem is still there in 11.04, with samba, just upgraded from proposed-updates (2:3.5.8~dsfg-1ubuntu2.2), despite the log reports

    * debian/samba.smbd.upstart: Do not attempt to start smbd until network
    device is up, previously smbd was starting too early and often failing.
    (LP: #771305)

I'm experimenting it in this "flavour": samba seems to be working, as I'm seeing a shared folder, but _printers only_ are not shared. As usual, a manual restart (sudo service smbd restart) fixes the issue (and the printer magically shows up in the WinVista client), but on reboot it's always the same: I can see the folder shares, not the printer.

Configuration of smbd.conf and nmbd.conf is all default, I also tried the modification of cipher2 (remove the "and net-device-up !loopback" from nmbd.conf) without success. Also, I tried to add a "and started nmbd" to "smbd.conf", as I spotted from the thread that the problem might be due to smbd and nmbd booting up concurrently, again without success.

Something very strange I have in /var/log/boot.log:

  Rather than invoking init scripts through /etc/init.d, use the service(8)
  utility, e.g. service S20smbd start

  Since the script you are attempting to invoke has been converted to an
  Upstart job, you may also use the start(8) utility, e.g. start S20smbd
  start: Unknown job: S20smbd

As you can see, it seems smbd's name is being actually mistaken as "S20smbd", i.e., the rc.d link. However, I double-checked the rc.d links, and I can't see anything irregular:

$ ls -l /etc/rc*/*smb*
lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc2.d/S20smbd -> ../init.d/smbd
lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc3.d/S20smbd -> ../init.d/smbd
lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc4.d/S20smbd -> ../init.d/smbd
lrwxrwxrwx 1 root root 14 2011-05-03 13:08 /etc/rc5.d/S20smbd -> ../init.d/smbd

and the smbd.conf is there in /etc/init/smbd.conf.

Now I'm going to try this samba4.

[Felix (apoapo)]

To let you know that you are not alone.. I experienced the not starting nmbd in maverick and natty also. My workaround is to restart it via rc.local like:

sleep 30
service nmbd restart

I am glad to see that you are already investigating this. Thank you!

[Launchpad Janitor (janitor)]

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

[Stefan Brozinski (stefan-brozinski)]

On Ubuntu 14.04 nmbd fails to start on boot. There may be a regression in the upstart script.
The following change fixed the problem for me:

Change the "start on" condition in /etc/init/nmbd.conf to:

start on (started smbd)

(Thanks to Dan Corso who proposed this fix in comment #49 in bug #596064)