sec= in mount.cifs is a client setting, I was quoting the mount.cifs
manpage where it says when that changed defaults in the (client
machine's) kernel.
Either way, I believe the solution to what you reported is in the first
paragraph of comment #21.
--
You received this bug notification because
Thanks for filing this bug in Ubuntu.
It looks like nmbd is failing to start due to a network configuration problem:
Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for
interface ..."
Also, there are hints pointing at a local configuration issue, but the log is
trunc
> should be fixed so as not to waste everyone's time; even if that does just
> involve outputting a
> message like "About to try something as a fallback in case a previous step
> failed. A 'systemctl
> preset failed message' is expected so please ignore it." first.
That's exactly what was done
I think you are trying to run the samba-ad-dc service (samba-ad-
dc.service) on a non-AD-DC configured machine. The smb.conf you attached
shows that you are using "security = user" which is a standalone server
role, not an active directory controller.
If this is really your intention (NOT running
Thanks for filing this bug in Ubuntu.
The logs indicate that the nmbd service failed to start:
Status: "nmbd: No local IPv4 non-loopback interfaces available, waiting for
interface ..."
This usually indicates a local network configuration problem.
You should revise these parameters:
Thanks for filing this bug in Ubuntu.
Unfortunately I can't determine the problem with the information at
hand.
Could you please try the following commands and show their outputs to
see if we can get more information:
sudo apt update
sudo apt -f install
And then:
sudo apt install --reinstall sa
Thanks for filing this bug in Ubuntu.
Unfortunately the attached information is not enough to properly
diagnose this problem.
Could you please run the following commands and report back:
sudo apt update
sudo apt -f install
If the above doesn't fix it, then continue with:
sudo apt install --rein
Thanks for filing this bug in Ubuntu.
The nmbd service is failing to start, and it shows this in the status
output:
Status: "nmbd: No local IPv4 non-loopback interfaces available,
waiting for interface ..."
Exact details will be given in the /var/log/samba/log.nmbd file, but it
looks like you
Did you solve your problem?
--
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/1704394
Title:
package samba 2:4.5.8+dfsg-0ubuntu0.17.04.3 failed to install/upgrade:
sub-processo script
Thanks for filing this bug in Ubuntu.
You have a syntax error in your /etc/samba/smb.conf file. Look at the
very end:
[Home Share }
comment = /home/dave/
writable = yes
valid users = dave
You probably meant for it to be:
[Home Share]
comment = /home/dave/
writable = yes
valid users = dave
Since
Thanks for reporting this bug in Ubuntu.
Could you please try the following commands and see if they help:
sudo apt update
sudo apt install --reinstall samba-libs
Thanks
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a memb
Do you know if this patch or bug report was ever submitted upstream?
I'm trying to update samba to 4.6.5 in artful
(https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/326418)
and then I can look more closely at this issue.
** Tags added: server-next
--
You received thi
Thanks for filing this bug in Ubuntu.
Could you please try the following commands and see if they solve the
problem for you:
sudo apt update
sudo apt install --reinstall libgssapi-krb5-2 libk5crypto3
Thanks
** Changed in: krb5 (Ubuntu)
Status: New => Incomplete
--
You received this b
Thanks for filing this bug in Ubuntu.
Could you please try the following commands and let us know if it fixes
the problem?
sudo apt update
sudo apt install --reinstall libk5crypto3
Thanks!
** Changed in: krb5 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification be
Upstream says this was fixed in samba 4.2.0 and should then work
correctly for all currently supported Ubuntu releases. The oldest one,
Ubuntu Trusty, has samba 4.3.x in -updates.
Therefore I'm marking this as fix released in Ubuntu as well.
** Changed in: samba (Ubuntu)
Status: Triaged =>
** Also affects: apache2 via
https://bz.apache.org/bugzilla/show_bug.cgi?id=61301
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/170416
Ok, thanks for getting back to us.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1698772
Title:
package clamav-base 0.99.2+dfsg-6 failed to install/upgrade: package
is in a very b
No, the test fails in artful even with llvm 3.8 or 3.9. It's something
else in the toolchain I believe.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1692073
Title:
check_clamav test
** Changed in: freeradius (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeradius in Ubuntu.
https://bugs.launchpad.net/bugs/1704387
Title:
Merge freeradius 3.0.14+dfsg-2 (main) from Debian
Thanks for filing this bug in Ubuntu.
Could you please try the following commands and see if they resolve the
problem:
sudo apt update
sudo apt install --reinstall libnl-route-3-200
If that doesn't sort it, then please try:
sudo apt -f install
And post back the results. Also, you say you were
What kind of vpn are you using, is it openvpn? How did you establish it,
was it via the network-manager plugin? Or do you manually bring up an
openvpn client? If it's some other vpn, could you clarify how it is used
please?
Thanks
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
Thanks for filing this bug in Ubuntu.
Did you originally install quagga from a source other than Ubuntu? I ask
because the installed package, quagga-mr, doesn't seem to be from
Ubuntu:
Commandline: apt-get install quagga
Requested-By: burak (1000)
Install: quagga:amd64 (0.99.24.1-2ubuntu1.2)
Remo
Thanks for filing this bug in Ubuntu.
Since it looks like a kernel issue, I'm changing the affected
project/package accordingly.
** Package changed: mtx (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mtx in
23 matches
Mail list logo
