One needs to be careful with installing other python versions on a
system and making them available system-wide. Upstream samba doesn't yet
fully support python3, and the samba version shipped in ubuntu 16.04
most definitely does not support it either.
What's failing for you guys is this bit in po
It looks fine now, I believe it was due to the old bug that is now fixed
(the one about unitialized values). Also, you should probably remove the
segler-alex ppa as it does not have xenial packages.
I'll mark this bug as invalid for samba as it happened in another
package, related to debconf, whic
Thanks for filing this bug in Ubuntu.
The logs indicate that the smbd service, part of samba, failed to start, but do
not tell why:
invoke-rc.d: initscript smbd, action "start" failed.
[0;1;31m●[0m smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; disabled; ve
> This is to say that I do not in fact have a WINS server specified; that
> judging by the logs
> my winbind is relying on broadcasts, and bombing out in that case if started
> before
> network-online.target.
Ok, reproduced. When there is no wins server specified, somehow winbind
doesn't "detect
Ah, and that's only in the "no wins specified" case, otherwise it
recovers just fine.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1789097
Title:
winbind does not work after reboot on Min
basically if the interface is available when winbind starts, winbind
keeps working if it's brought down and up again. But if winbind starts
when the interface isn't available, then it won't recover without a
restart. That's my finding so far.
--
You received this bug notification because you are
** Bug watch added: Samba Bugzilla #13607
https://bugzilla.samba.org/show_bug.cgi?id=13607
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=13607
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Serv
Thanks for filing this bug in Ubuntu.
This seems to be a duplicate of bug #1731502, where there was no network
available when nmbd was restarted:
Status: "nmbd: No local IPv4 non-loopback interfaces available,
waiting for interface ..."
I suggest the following commands, after the network is a
Can you simplify the configuration needed to reproduce this bug? For
example, does it happen when using gssapi authentication with apache,
without the NFSv4 bit?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to krb5 in Ubuntu.
https://bugs.la
Or can you elaborate a bit more how you have this setup?
And, before I forget, do you have a crash file somewhere in /var/crash?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1788459
Title:
The version of quagga in bionic is 1.2.4-1, which is the same as in Debian.
Looks like Debian later on reverted the sysv script removal:
quagga (1.2.4-2) unstable; urgency=low
* Correct previous changelog entry for CVE numbers
* Re-enable building of watchquagga
* Re-instate sysvinit script
The sysv script checked for a Quagga.conf file, and if it's there, ignores the
need for the other config files:
# If the integrated config file is used the others are not checked.
if [ -r "$C_PATH/Quagga.conf" ]; then
return 0
fi
...
# check for config f
Ok, I think I understand it now.
The individual service files have a condition to start the service, and that is
the config file:
/lib/systemd/system/bgpd.service:
ConditionPathExists=/etc/quagga/bgpd.conf
/lib/systemd/system/zebra.service
ConditionPathExists=/etc/quagga/zebra.conf
and so on.
13 matches
Mail list logo
