lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: samba (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
maverick has seen the end of its life and is no longer receiving any
updates. Marking the maverick task for this ticket as Won't Fix.
** Changed in: samba (Ubuntu Maverick)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Hi guys,
try this... replace the start on line with:
start on (started smbd)
it tells upstart to respect priorities (worked for me).
Bye,
Daniele
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
This bug affects me. I am running 10.04 (LTS) on an Oracle VM
VirtualBox. I am also setting up a ipv6 tunnel with Hurricane Electric,
so I am fiddling with /etc/NetworkManager/{interfaces, system-
connections/'Auto eth1'} /etc/network/interfaces.
--
You received this bug notification because
Can someone at least tell me how I can debug this? There is absolutely
nothing in logs. nmbd just does not start even with start on (local-
filesystems) sometimes. smbd starts, nmbd doesn't.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Yesterday after reboot neither smbd, nor nmbd started. There was nothing
in logs. Ubuntu server is such a failure.
--
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/596064
Title:
nmbd
After another reboot, smbd started, nmbd didn't, but this time there was
a message in log:
May 18 18:27:37 shadow-server init: nmbd pre-start process (882)
terminated with status 1
After one more reboot both smbd and nmbd startd. Can someone finally fix
this? Can this god damn init be more
Few days ago nmbd stopped starting on boot for me. I did not change
anything at all.
===
user@host:~$ cat /etc/init/nmbd.conf
description NetBIOS name server
author Steve Langasek steve.langa...@ubuntu.com
start on (local-filesystems and net-device-up IFACE=eth0)
stop on runlevel [!2345]
Also, sometimes it starts, sometimes not.
--
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/596064
Title:
nmbd fails to start on boot - problem with upstart
To manage notifications
I added some debug into /etc/init/nmbd.conf so it looks like this:
===
description NetBIOS name server
author Steve Langasek steve.langa...@ubuntu.com
start on (local-filesystems and net-device-up IFACE=eth0)
stop on runlevel [!2345]
expect fork
respawn
pre-start script
Changing to start on (local-filesystems) did not help, still not
starting.
--
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/596064
Title:
nmbd fails to start on boot - problem with
Some more testing revealed that if I comment out user's cron @reboot job
that starts two virtualbox machines, nmbd starts. So I guess upstart
fails to continue starting daemons if there is a high system load at
boot time.
This makes me very sad. User job can affect server's start up... I have
I just hit this bug, after updating samba to start after eth0 was up because of
bug
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/823878
dylan@strut-google-server:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=Ubuntu 10.04.3
** Changed in: samba (Ubuntu Lucid)
Status: New = Confirmed
--
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/596064
Title:
nmbd fails to start on boot - problem with upstart
To
Geez, isn' t there a META issue function in launchpad?
nmbd doesn' t startup since 9.04, and now trying to really fix it, without
rc.local delayed work arounds, I found a fix for each version of Ubuntu server.
Bugs since 2009.
Anyone know why the samba init.d got split up into smbd and nmbd? It
I fixed 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...
--
Please open a different bug report; although it's related, it's a
different issue.
Nice catch, btw.
--
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/596064
Title:
nmbd fails to start
oki doki, bug registered as #750786 for natty!
--
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/596064
Title:
nmbd fails to start on boot - problem with upstart
--
Ubuntu-server-bugs
Still happening in natty amd64
I have to start nmbd manually for full network share (load and
access)...
using the mkdir -p fix did not resolve...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
On Sun, 2011-03-27 at 18:23 +, Cypher2 wrote:
Still happening in natty amd64
I have to start nmbd manually for full network share (load and
access)...
using the mkdir -p fix did not resolve...
I suspect you're hitting a different issue, please file a separate bug report.
Cheers,
actually no.. same issue: when i start the system, only smbd is loaded as
process. when looking at /var/run/samba it is active and populated with no
nmbd PID file. only when I switch to console and run 'sudo start nmbd' that
it loads a process and assigns PID to it.
when I restart or shutdown
Is there a fix for 10.04 LTS, which only runs 2:3.4.7~dfsg-1ubuntu3.4? I
don't often reboot my server, but invariably forget to check that nmbd
is running when I do!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
On Sun, 2011-03-06 at 20:49 +, Paul Tansom wrote:
Is there a fix for 10.04 LTS, which only runs 2:3.4.7~dfsg-1ubuntu3.4? I
don't often reboot my server, but invariably forget to check that nmbd
is running when I do!
There is no fix for Maverick yet, but according to the Launchpad page
Chuck
I'm using a wireless connection with wicd (wlan interface is wlan0). Adding
mkdir -p /var/run/samba does not solve the problem.
Changing
start on (local-filesystems and net-device-up IFACE!=lo)
to
start on (local-filesystems)
in /etc/init/nmbd.conf fixes it and nmbd starts. But this is not
Hi giox069,
That's a different issue than this bug (which is already fixed). Can you
please file a separate bug report about that?
--
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/596064
Kylepablo, this bug was fixed in 2:3.5.6~dfsg-4ubuntu2, so a version
newer than what you are running.
--
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/596064
Title:
nmbd fails to start
@Jelmer: ok, I will do further investigation on how wicd works and then
file a separate bug report.
--
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/596064
Title:
nmbd fails to start
This bug is still present for me. I have to do nmbd -D manually.
Ubuntu 10.10
samba2:3.5.4~dfsg-1ub
nmbd.conf is attached.
** Attachment added: nmbd.conf
https://bugs.launchpad.net/ubuntu/lucid/+source/samba/+bug/596064/+attachment/1811589/+files/nmbd.conf
--
You received
Confirmed. Adding mkdir -p /var/run/samba just after the pre-start
script line of /etc/init/nmbd.conf fixes it.
Ubuntu 10.10
samba 2:3.5.4~dfsg-1ub
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
** Branch linked: lp:ubuntu/samba
--
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/596064
Title:
nmbd fails to start on boot - problem with upstart
--
Ubuntu-server-bugs mailing list
** Branch linked: lp:~jelmer/samba/596064-nmb-fails-to-start
--
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/596064
Title:
nmbd fails to start on boot - problem with upstart
--
This bug was fixed in the package samba - 2:3.5.6~dfsg-4ubuntu2
---
samba (2:3.5.6~dfsg-4ubuntu2) natty; urgency=low
* debian/samba.nmbd.upstart: create /var/run/samba directory before running
testparm. Fixes start-up of nmb after boot. (LP: #596064)
Thanks to Jelmer
** Changed in: samba (Ubuntu)
Assignee: Chuck Short (zulcss) = Jelmer Vernooij (jelmer)
--
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/596064
Title:
nmbd fails to start on boot
It should be:
mkdir -p /var/run/samba
Otherwise if the directory already exists it won't be able to start. So
mkdir -p will start in all conditions.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
On Fri, 2010-12-10 at 20:52 +, Jean-Michel Dault wrote:
It should be:
mkdir -p /var/run/samba
Otherwise if the directory already exists it won't be able to start. So
mkdir -p will start in all conditions.
I'm pretty sure install -d exits with success if the directory already
What appears to be happening is that the first time nmbd gets run
testparm fails (because pid dir /var/run/samba doesn't exist yet) so
nmbd is not started.
After that smbd gets run and its pre-init will create /var/run/samba. So
the next time nmbd's pre-init script will work.
--
nmbd fails to
It looks like the creation of /var/run/samba should happen earlier in
the script.
What about the attached patch?
--
nmbd fails to start on boot - problem with upstart
https://bugs.launchpad.net/bugs/596064
You received this bug notification because you are a member of Ubuntu
Server Team, which
I can reproduce it on Lucid and Maverick under the following conditions:
- the network is a WLAN
- the connection is made by Network Manager or WICD
I don't know what the condition net-device-up IFACE!=lo in
/etc/init/nmbd.conf is really needed for. Can it be recommended to leave
it out and to
I havent been able to reproduce this on maverick yet.
chuck
--
nmbd fails to start on boot - problem with upstart
https://bugs.launchpad.net/bugs/596064
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
@Chuck, were you able to reproduce it on Lucid? Do you consider this
was Fix Released for Maverick, somewhere along the cycle?
--
nmbd fails to start on boot - problem with upstart
https://bugs.launchpad.net/bugs/596064
You received this bug notification because you are a member of Ubuntu
** Tags added: server-mrs
--
nmbd fails to start on boot - problem with upstart
https://bugs.launchpad.net/bugs/596064
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
** Changed in: samba (Ubuntu)
Importance: High = Medium
** Changed in: samba (Ubuntu)
Assignee: (unassigned) = Chuck Short (zulcss)
** Changed in: samba (Ubuntu Lucid)
Assignee: Chuck Short (zulcss) = (unassigned)
** Also affects: samba (Ubuntu Maverick)
Importance: Medium
I tested what my /etc/init/nmbd.conf was doing at the command line:
---
r...@server2:/var/log# /usr/bin/testparm -s --parameter-name='disable netbios'
Load smb config files from /etc/samba/smb.conf
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Processing section [netlogon]
Should probably be lumped together with bug 572410
** Also affects: samba (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu Lucid)
Assignee: (unassigned) = Chuck Short (zulcss)
--
nmbd fails to start on boot - problem with upstart
I experienced this (nmbd do not startup at boot), recently after
upgrading from ubuntu 9.10 server to 10.04 LTS.
The solution suggested in the Post#7 by Mr Abhishek Mukherjee worked.
(Just adding the line mkdir /var/run/samba at just after the pre-start
script line of /etc/init/nmbd.conf)
Nice investigation, thanks!
nmbd would only start when its start is run after smbd's upstart script
pre-start. We indeed need to fix that race.
** Changed in: samba (Ubuntu)
Importance: Medium = High
** Changed in: samba (Ubuntu)
Status: Incomplete = Triaged
--
nmbd fails to start
Hi,
Can you test out samba_3.4.7~dfsg-1ubuntu4~test in
https://edge.launchpad.net/~zulcss/+archive/server-bug-fixes when it
gets built?
Thanks
chuck
--
nmbd fails to start on boot - problem with upstart
https://bugs.launchpad.net/bugs/596064
You received this bug notification because you are
There is something interesting that happened after we changed the script
the way you had described. NMBD started at boot. After some
troubleshooting, we noticed the following errors in the /tmp/nmbd-
upstart.log
$ cat /tmp/nmbd-upstart.log
Load smb config files from /etc/samba/smb.conf
Here is the log
Sat Jun 26 17:31:19 IST 2010
Load smb config files from /etc/samba/smb.conf
rlimit_max: rlimit_max (1024) below minimum Windows limit (16384)
Processing section [printers]
Processing section [print$]
Loaded services file OK.
Output is No
--
nmbd fails to start on boot - problem
OK, so the issue seems to be that testparm -s --parameter-
name='disable netbios' sometimes fails (or returns 'Yes') when
started at boot-time. The start on (local-filesystems and net-device-up
IFACE!=lo) should however be late enough...
To confirm, could you try with:
pre-start script
date
I played with the nmbd.conf script and changed the 2 lines that seem at fault
looks to of worked not done repeat tests
NMBD_DISABLED=`testparm -s --parameter-name=disable netbios
2/tmp/nmbd-upstart.log`
[ $NMBD_DISABLED = Yes ] { stop; exit 0; }
I don't think removing the x's from the second
I and Abhishek are working in the same lab setup.
Here are the answers to U'r Q
$ testparm -s --parameter-name='disable netbios' 2/dev/null
$ echo $?
rka...@rka-29-desktop:~$ testparm -s --parameter-name='disable netbios'
2/dev/null
No
rka...@rka-29-desktop:~$ echo $?
0
Also, on the machine
Those two lines are about checking if NetBIOS is disabled in smb.conf, and if
yes, not start nmbd.
If it works reliably for you once you comment those lines, something must fail
on this testparm check.
Could you try running the following (on one of the machines that fail if the
check is
No manual changes were made to samba configuration file. Here it goes.
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba
54 matches
Mail list logo
