I guess this bug is just too hard to fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to pptpd in Ubuntu.
https://bugs.launchpad.net/bugs/1296835
Title:
status_of_proc lacks a -p in /etc/init.d/pptpd
To manage notifications about
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
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/963368
Title:
dnssec-keygen takes forever to generate a keyfile
To manage notifications about this bug go to:
Public bug reported:
A command `dnssec-keygen -f KSK example.com` took more than 30 hours to
complete on my system. It's not something anyone would expect from a
simple keyfile generation utility.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bind9 1:9.7.0.dfsg.P1-1ubuntu0.4
Looks like it is. Also, I have similar configuration as in cremersdh's
last post:
interfaces = 192.168.0.0/24
bind interfaces only = yes
So, it really has to wait before all defined network interfaces are up.
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
Sometimes smbd daemon failes to start after system restart. As a result,
fileserver is not accessible after power failure and requires someone to
fix that manually, which sometimes is very hard to do. Today this
happened again and here's what was in logs:
===
Aug 10 14:40:32
--
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/823878
Title:
smbd failed to start after system restart
To manage notifications about this bug go to:
14 matches
Mail list logo
