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 <nathanel.tit...@gmail.com
> wrote:

> alright.. i'll revert back to the original config and verbose it...
>
>
> On Sun, Apr 10, 2011 at 11:10 AM, Clint Byrum <cl...@fewbar.com> 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 <cl...@fewbar.com> 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 <steve.langa...@ubuntu.com>"
>> > >
>> > >  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
>> >
>> > --
>> > 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 <steve.langa...@ubuntu.com>"
>> >
>> >   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
>>
>> --
>> 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 <steve.langa...@ubuntu.com>"
>>
>>  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
>
>


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

514 . 583 . 7386

-- 
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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to