[Bug 1716905] Re: package docker.io (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127
*** 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 installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1716905 Title: package docker.io (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1716905/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1754720] Re: package docker.io 1.13.1-0ubuntu1~16.04.2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 127
*** 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 installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1754720 Title: package docker.io 1.13.1-0ubuntu1~16.04.2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1754720/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1734746] Re: package docker.io (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 127
*** 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 installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1734746 Title: package docker.io (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1734746/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1724353] Re: cannot purge docker.io due to a bashism in nuke-graph-directory
*** 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 prompt
- not restarting Docker causes many issues (LP: #1658691)
- suggested methods for keeping containers up are to use a restart policy
("--restart=..." on "docker run"), Swarm Mode services, or rolling
replacement of k8s workers
* Backport 30519 for bashism (LP: #1744599)
Xenial and Artful are still affected.
** This bug has been marked a duplicate of bug 1744599
package docker.io (not installed) failed to install/upgrade: subprocess
installed post-removal script returned error exit status 127
--
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/1724353
Title:
cannot purge docker.io due to a bashism in nuke-graph-directory
To manage notifications about this bug go to:
https://bugs.launchpad.net/docker.io/+bug/1724353/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1753154] Re: package docker.io (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 127
*** 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 installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1753154 Title: package docker.io (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-removal возвратил код ошибки 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1753154/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1768212] Re: Package docker.io cannot be purged
*** 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 installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to docker.io in Ubuntu. https://bugs.launchpad.net/bugs/1768212 Title: Package docker.io cannot be purged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1768212/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1767617] Re: package docker.io (not installed) failed to install/upgrade: installed docker.io package post-removal script subprocess returned error exit status 127
*** 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 installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 127 -- 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/1767617 Title: package docker.io (not installed) failed to install/upgrade: installed docker.io package post-removal script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1767617/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1735953] Re: samba mount fails to write
** 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 bug go to: https://bugs.launchpad.net/samba/+bug/1735953/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1774431] Re: rpc.rquotad takes 100% CPU
** 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: (unassigned) => Christian Ehrhardt (paelzer) -- 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/1774431 Title: rpc.rquotad takes 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quota/+bug/1774431/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1418279] Re: Automount NFSv4 doesn't work
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. https://bugs.launchpad.net/bugs/1418279 Title: Automount NFSv4 doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1418279/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1680224] Re: auto.smb fails on Windows administrative shares
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. https://bugs.launchpad.net/bugs/1680224 Title: auto.smb fails on Windows administrative shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1680224] Re: auto.smb fails on Windows administrative shares
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 https://mirrors.edge.kernel.org/pub/linux/daemons/autofs/v5/patches-5.1.3/autofs-5.1.2-increase-worker-thread-per-thread-stack-size.patch -- 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/1680224 Title: auto.smb fails on Windows administrative shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1708788] Re: package autofs 5.1.1-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 "systemctl status autofs.service" and "journalctl -xe" for details. invoke-rc.d: initscript autofs, action "start" failed. [0;1;31m●[0m autofs.service - LSB: Automounts filesystems on demand Loaded: loaded (/etc/init.d/autofs; bad; vendor preset: enabled) Active: [0;1;31mfailed[0m (Result: exit-code) since Fri 2017-08-04 20:16:27 PDT; 3ms ago Docs: man:systemd-sysv-generator(8) Process: 5697 ExecStart=/etc/init.d/autofs start [0;1;31m(code=exited, status=127)[0m Tasks: 21 Memory: 3.9M CPU: 9ms CGroup: /system.slice/autofs.service └─2132 /usr/sbin/automount --pid-file /var/run/autofs.pid Aug 04 20:16:27 tully systemd[1]: Starting LSB: Automounts filesystems on d. Aug 04 20:16:27 tully autofs[5697]: * Starting automount... Aug 04 20:16:27 tully autofs[5697]:...done. Aug 04 20:16:27 tully autofs[5697]: /etc/init.d/autofs: 112: /etc/init.d/au...nd Aug 04 20:16:27 tully systemd[1]: [0;1;39mautofs.service: Control process exited, c...27[0m Aug 04 20:16:27 tully systemd[1]: [0;1;31mFailed to start LSB: Automounts filesyste...d.[0m Aug 04 20:16:27 tully systemd[1]: [0;1;39mautofs.service: Unit entered failed state.[0m Aug 04 20:16:27 tully systemd[1]: [0;1;39mautofs.service: Failed with result 'exit-...'.[0m Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package autofs (--configure): subprocess installed post-installation script returned error exit status 1 Setting up libapt-inst2.0:amd64 (1.2.24) ... It hints at something having gone wrong in line 112 of etc/init.d/autofs, but that line is just the end of the file. If this is still happening, could you please show us the output of: sudo apt update sudo apt -f install sudo systemctl -l status autofs.service Thanks ** 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. https://bugs.launchpad.net/bugs/1708788 Title: package autofs 5.1.1-1ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1708788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1728055] Re: GDM3 hangs, if local home directory is not accessible
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 broad in its current state, it would help if you could
narrow it down a bit.
** 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.
https://bugs.launchpad.net/bugs/1728055
Title:
GDM3 hangs, if local home directory is not accessible
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1728055/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
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 configuration or restarts. Same for when an address disappears. It's definitely a good default for network services. The moment you tell a service to bind to a specific IP, however, if that IP is not available then it will fail. That's where IP_FREEBIND comes in. It requires code changes, though. This systemd upstream article talks about the pros and cons of depending on network-online.target: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/. In general, it should be avoided if possible. -- 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/1774788 Title: Daemon won't start at boot up (18LTS fully patched) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1774788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1760855] Re: logrotate rules do not allow for samba being disabled.
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 report. https://bugs.launchpad.net/bugs/1760855 Title: logrotate rules do not allow for samba being disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1760855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1754506] Re: AutoFS does not automatically umount SMB shares
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1754506/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1774848] Re: can't delete broken count package python-samba 2:4.3.11+dfsg-0ubuntu0.16.04.12 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es e
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 bug notification because you are a member of Ubuntu Server, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1774848 Title: can't delete broken count package python-samba 2:4.3.11+dfsg- 0ubuntu0.16.04.12 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es erneut installieren, bevor Sie es zu entfernen versuchen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1774848/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
** 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: rsync (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) To manage notifications about this bug go to: https://bugs.launchpad.net/rsync/+bug/1774788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1774788] Re: Daemon won't start at boot up (18LTS fully patched)
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 21:12:27 bionic-rsync-1774788 rsyncd[269]: bind() failed: Cannot assign requested address (address-family 2) /var/log/syslog:Jun 4 21:12:27 bionic-rsync-1774788 rsyncd[269]: unable to bind any inbound sockets on port 873 /var/log/syslog:Jun 4 21:12:27 bionic-rsync-1774788 rsyncd[269]: rsync error: error in socket IO (code 10) at socket.c(555) [Receiver=3.1.2] The solution seems to be for rsync to adopt the socket option IP_FREEBIND. >From the ip(7) manpage: IP_FREEBIND (since Linux 2.4) If enabled, this boolean option allows binding to an IP address that is nonlocal or does not (yet) exist. This per‐ mits listening on a socket, without requiring the underlying network interface or the specified dynamic IP address to be up at the time that the application is trying to bind to it. This option is the per-socket equivalent of the ip_nonlo‐ cal_bind /proc interface described below. Until then, one workaround would be to configure the service file for rsyncd to wait for the network to be online. If you run: sudo systemctl edit rsync.service It will open an editor. Put these lines in: [Unit] After=network.target,network-online.target Then save. That will create /etc/systemd/system/rsync.service.d/override.conf with the two lines above. Alternatively you can just create the file above directly with the specified content without going through "systemctl edit". You can then reboot and see if that helps. Note that the job will fail, after reaching the network-online target, if you specify an IP address that doesn't exist at that stage. Another option I saw in https://unix.stackexchange.com/questions/442181 /sshd-failed-due-to-network-not-yet-available but haven't tested is to make a system-wide change in /proc. -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1774788 Title: Daemon won't start at boot up (18LTS fully patched) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1774788/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1773004] Re: qemu-system-x86_64 segfaults during guest kernel boot
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 of Ubuntu Server, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1773004 Title: qemu-system-x86_64 segfaults during guest kernel boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1773004/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1774765] Re: package haproxy 1.8.8-1ubuntu0.1 failed to install/upgrade: installed haproxy package post-installation script subprocess returned error exit status 1
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, action "start" failed. ● haproxy.service - HAProxy Load Balancer Loaded: loaded (/lib/systemd/system/haproxy.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2018-06-02 12:55:58 IST; 5ms ago Docs: man:haproxy(1) file:/usr/share/doc/haproxy/configuration.txt.gz Process: 6482 ExecStart=/usr/sbin/haproxy -Ws -f $CONFIG -p $PIDFILE $EXTRAOPTS [0;1;31m(code=exited, status=1/FAILURE)[0m Process: 6481 ExecStartPre=/usr/sbin/haproxy -f $CONFIG -c -q $EXTRAOPTS (code=exited, status=0/SUCCESS) Main PID: 6482 (code=exited, status=1/FAILURE) Jun 02 12:55:59 Dell haproxy[6495]: [ALERT] 152/125559 (6495) : Starting proxy mysql: cannot bind socket [127.0.0.1:3306] Jun 02 12:55:59 Dell systemd[1]: [0;1;39m[0;1;31m[0;1;39mhaproxy.service: Main process exited, code=exited, status=1/FAILURE[0m Jun 02 12:55:59 Dell systemd[1]: [0;1;39m[0;1;31m[0;1;39mhaproxy.service: Failed with result 'exit-code'.[0m Jun 02 12:55:59 Dell systemd[1]: [0;1;31m[0;1;39m[0;1;31mFailed to start HAProxy Load Balancer.[0m Jun 02 12:55:59 Dell systemd[1]: haproxy.service: Service hold-off time over, scheduling restart. Jun 02 12:55:59 Dell systemd[1]: haproxy.service: Scheduled restart job, restart counter is at 5. Jun 02 12:55:59 Dell systemd[1]: Stopped HAProxy Load Balancer. Jun 02 12:55:59 Dell systemd[1]: [0;1;39m[0;1;31m[0;1;39mhaproxy.service: Start request repeated too quickly.[0m Jun 02 12:55:59 Dell systemd[1]: [0;1;39m[0;1;31m[0;1;39mhaproxy.service: Failed with result 'exit-code'.[0m Jun 02 12:55:59 Dell systemd[1]: [0;1;31m[0;1;39m[0; It looks like you have another service already listening on port 3306. Perhaps it's mysql itself? Please attach these files: /etc/default/haproxy /etc/haproxy/haproxy.cfg And show the output of this command: sudo netstat -anp Thanks! ** Changed in: haproxy (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1774765 Title: package haproxy 1.8.8-1ubuntu0.1 failed to install/upgrade: installed haproxy package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1774765/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1773679] Re: Samba panics; samba-dbg package not found
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. https://bugs.launchpad.net/bugs/1773679 Title: Samba panics; samba-dbg package not found To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1773679/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
