[Bug 750786] Re: nmbd job fails to start on boot

[Cypher2]

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 <nathanel.titane at gmail.com
> 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 ..

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/750786

Title:
  nmbd job fails to start on boot