Debian's fix: https://salsa.debian.org/samba-
team/samba/commit/47a6fe2ea22551c1b8d11a17332244ebdd0f94fb
We should get it the next time we sync/merge with them.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Thanks for filing this bug in Ubuntu.
This is the error log:
Setting up haproxy (1.8.8-1ubuntu0.1) ...
Job for haproxy.service failed because the control process exited with error
code.
See "systemctl status haproxy.service" and "journalctl -xe" for details.
invoke-rc.d: initscript haproxy,
** Bug watch added: Samba Bugzilla #13463
https://bugzilla.samba.org/show_bug.cgi?id=13463
** Also affects: rsync via
https://bugzilla.samba.org/show_bug.cgi?id=13463
Importance: Unknown
Status: Unknown
** Changed in: rsync (Ubuntu)
Status: New => Triaged
** Changed in:
Thanks for filing this bug in Ubuntu.
Could you please try the following, and show us the output:
sudo apt update
sudo apt -f install
Also please attach these files:
/var/log/dpkg.log
/var/log/apt/term.log
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received this
** Changed in: autofs (Ubuntu)
Importance: Undecided => Low
--
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/1754506
Title:
AutoFS does not automatically umount SMB shares
To manage
You can also attach the actual crash file if you prefer, and we can
install the dbgsym packages in a test system to get the full backtrace.
Or make it available via some other means, as it will have a memory dump
of the qemu process.
--
You received this bug notification because you are a member
Thanks for filing this bug in Ubuntu.
The scenario is confirmed: when specifying an address to bind to, rsync will
fail if that address is not available:
/var/log/syslog:Jun 4 21:12:27 bionic-rsync-1774788 rsyncd[269]: rsyncd
version 3.1.2 starting, listening on port 873
/var/log/syslog:Jun 4
The default behaviour of these services is to bind to "0.0.0.0", which
means "any IP" essentially. That means they will work even when the nic
isn't there yet, because localhost is. It also means that once a new nic
comes up, they will listen on all its addresses too, without any other
changes in
I'm hoping to soon collect all these small (and some not so small) samba
bugs in one big swoop and fix them with a single SRU.
** Tags removed: server-next
** Tags added: bite-size
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug
And
https://mirrors.edge.kernel.org/pub/linux/daemons/autofs/v5/patches-5.1.3/autofs-5.1.2
-fix-offset-mount-location-multiple-expansion.patch, mentioned in
comment #10 too
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
I believe these are the upstream patches:
https://mirrors.edge.kernel.org/pub/linux/daemons/autofs/v5/patches-5.1.3/autofs-5.1.2-use-malloc-for-expanded-map-location.patch
How do you fetch your users from ldap, using sssd? Or nss_ldap? Or
something else? Does that need authentication, or are anonymous searches
allowed?
Does the mount()ing work if you temporarily create the user locally in
/etc/{passwd,group,shadow} but not his/her home directory?
This bug is a bit
Thanks for filing this bug in Ubuntu, and sorry for taking so long to
get to it.
This is the error from the logs:
update-rc.d: warning: start and stop actions are no longer supported; falling
back to defaults
Job for autofs.service failed because the control process exited with error
code. See
Is this a privileged container? Can you mount the NFS share manually
with the mount command?
** Changed in: autofs (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to autofs in Ubuntu.
** Changed in: quota (Ubuntu)
Status: Triaged => In Progress
** Changed in: quota (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: quota (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: quota (Ubuntu Bionic)
Assignee:
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1735953
Title:
samba mount fails to write
To manage notifications about this
*** This bug is a duplicate of bug 1744599 ***
https://bugs.launchpad.net/bugs/1744599
** This bug is no longer a duplicate of bug 1724353
cannot purge docker.io due to a bashism in nuke-graph-directory
** This bug has been marked a duplicate of bug 1744599
package docker.io (not
*** This bug is a duplicate of bug 1744599 ***
https://bugs.launchpad.net/bugs/1744599
** This bug is no longer a duplicate of bug 1724353
cannot purge docker.io due to a bashism in nuke-graph-directory
** This bug has been marked a duplicate of bug 1744599
package docker.io (not
*** This bug is a duplicate of bug 1744599 ***
https://bugs.launchpad.net/bugs/1744599
** This bug is no longer a duplicate of bug 1724353
cannot purge docker.io due to a bashism in nuke-graph-directory
** This bug has been marked a duplicate of bug 1744599
package docker.io (not
*** This bug is a duplicate of bug 1744599 ***
https://bugs.launchpad.net/bugs/1744599
** This bug is no longer a duplicate of bug 1724353
cannot purge docker.io due to a bashism in nuke-graph-directory
** This bug has been marked a duplicate of bug 1744599
package docker.io (not
*** This bug is a duplicate of bug 1744599 ***
https://bugs.launchpad.net/bugs/1744599
** This bug is no longer a duplicate of bug 1724353
cannot purge docker.io due to a bashism in nuke-graph-directory
** This bug has been marked a duplicate of bug 1744599
package docker.io (not
*** This bug is a duplicate of bug 1744599 ***
https://bugs.launchpad.net/bugs/1744599
Turns out there was another bug about this issue, and it was fixed in
bionic:
docker.io (17.03.2-0ubuntu2) bionic; urgency=medium
* Replace "--no-restart-on-upgrade" with "--no-start" and a debconf
*** This bug is a duplicate of bug 1744599 ***
https://bugs.launchpad.net/bugs/1744599
** This bug is no longer a duplicate of bug 1724353
cannot purge docker.io due to a bashism in nuke-graph-directory
** This bug has been marked a duplicate of bug 1744599
package docker.io (not
23 matches
Mail list logo
