This bug was confirmed fixed, the issue in Jaunty is a new issue. Maybe
a duplicate of bug 462169. In doubt please open a new bug.
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug
The problem still exists in jaunty for me. Switching to using
/etc/network/interfaces over Network Manager would work to fix it, but
its still broken by default.
** Changed in: samba (Ubuntu)
Status: Fix Released => Confirmed
--
Samba does not start on boot.
https://bugs.launchpad.net/bug
Hi. I experienced this exact problem in Ubuntu 9.04, today.
While attempting to try to fix it I killed my network connection somehow
and had to remove & purge package network-manager.
All is well now, though. For anyone that's a newbie like me, here's how
I fixed it.
These three terminal command
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
No, this is good to close.
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
I fixed this in Hardy with the attached if-up.d script.
I can't reproduce in Jaunty though. Can anyone else? If not, I suspect
this should be closed.
** Attachment added: "samba.if-up"
http://launchpadlibrarian.net/26148408/samba.if-up
--
Samba does not start on boot.
https://bugs.launchpa
** Changed in: samba (Ubuntu)
Assignee: Ubuntu Server Team (ubuntu-server) => (unassigned)
Status: In Progress => Confirmed
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
> This should be already fixed in hardy.
It isn't totally fixed, unless samba is supposed to start before
interfaces are configured by DHCP, and that doesn't count as a bug.
my smb.conf has
interfaces = 127.0.0.1/8 10.255.255.255/8
bind interfaces only = true
so eth0 _has_ to be up and c
This should be already fixed in hardy. Thanks for the bug report.
Regards
chuck
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a member of Ubuntu
Bu
> Upstream has made some adjustments to nmbd in samba 3.0.28a so that it
will wait when the interfaces have gone away, but I don't know if this
affects the behavior on startup.
This doesn't solve the problem for the ntpdate init script, for
example. There's a general problem that numbering scrip
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => Ubuntu Server Team (ubuntu-server)
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Upstream has made some adjustments to nmbd in samba 3.0.28a so that it
will wait when the interfaces have gone away, but I don't know if this
affects the behavior on startup.
If it doesn't, then I think what we want here is an if-up.d script to
try to start nmbd whenever the network comes back.
*
Alex,
Thanks for that. Yes, I had that problem a while back (it caused me
problems with hddtemp daemon), so it's not that this time around, I'm
pretty sure.
Now, FWIW, I've written a quick'n'dirty script that makes samba wait at
startup until the interfaces listed in "interfaces = " in smb.conf a
This problem has fixed itself for me lately in Hardy. Try seeing if your
local loopback interface is up.
ifconfig lo
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ub
Me too (Gutsy/amd64). This is a real PITA.
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
Same in Hardy. (Also had it in Gutsy.)
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.
I was just going to report the same bug. I've seen this on Ubuntu
Feisty, and I still see it on Gutsy. The problem I've seen seems to be
that on DHCP client machines, it can take some time for network
interfaces other than loopback to come up. The networking init script
(which runs ifup -a) does
My second test did not fare so well. Even with sysvinit, there seems to
be a race condition with samba.
I believe the right course it to put logic into the startup script to
wait for the network. In my first test case, spanning-tree portfast was
set on the switch in question, which leads to fast
Confirmed that replacing upstart with sysvinit eliminates the problem.
This is no fix, but it does seem to point at upstart.
HOST INFO:
# uname -a
Linux mpk-acura1 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
GNU/Linux
[EMAIL PROTECTED]:/var/log/apt# cat /etc/issue
Ubuntu 7.10 \n \l
This problem is persisting in Gutsy as well.
I am suspecting race conditions with upstart as root cause. I will run
test cases with sysvinit and see what the results are.
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you are a
Did some searching. Possible similarities to Bug #84537. Also, mlind
has a comment in Bug #25931 that sounds somewhat similar. I will run a
couple of use tests by tomorrow.
--
Samba does not start on boot.
https://bugs.launchpad.net/bugs/125687
You received this bug notification because you ar
21 matches
Mail list logo
