Public bug reported:
TL;DR: Ansible 2.5 is too old to manage any targeted hosts running
Python 3.8 or newer (Ubuntu 20.04 and higher) and lacking a python 2.x
install.
I have Ubuntu 18.04 on my office laptop. I installed the most recent
ansible from the repos on it and started developing ansible
I have this issue on a hyper-v gen2 secure-boot Ubuntu 16.04 Desktop
install. Because it's gen2 Hyper-v I can't boot my usual
SystemRescueCD, and dropping into recovery mode from the grub menu is
also worthless due to this bug. My last option is to boot from an
install cd and try to resize the pa
Is there any plan to backport this fix to Ubuntu 16.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694922
Title:
/etc/cron.monthly/ieee-data fails every month on redirected URLS
To manage n
Two of our Ubuntu 18.04 hosts applied this update this morning and both
dropped offline. They're both using netplan and have bonded interfaces.
The bond layer was offline. I had to reboot to get the network stack
running again. I left one host offline so the coworker who configured
them can look
I followed up with my coworker who originally built our two misbehaving
boxes. He also ended up having to reboot the second box I left for him,
to get the br01 bridge configuration back in working order. Simply
running 'netplan apply' and restarting the systemd network service did
not resolve it,
I've done some more digging into the systemd package update issue. We
have a number of Ubuntu 18.04 hosts, most of them are virtual machines
running simple eth0 configurations under Hyper-V. All of those VMs
updated the systemd package without issue. The only hosts which had
issues after the sys
I've just encountered this issue myself, on a VM that started life as
Ubuntu 16.04, do-release-upgrade to 18.04, then to 20.04, and now it
fails to boot with a similar error: /lib/systemd/libsystemd-
shared-245.so: undefined symbol: seccomp_api_get
The only non-Ubuntu-standard stuff on this VM i
Public bug reported:
The new default check_load definition in /etc/nagios/nrpe.cfg is way too
low for real-life. It seems the command definition changed between
Ubuntu 16.04 and 18.04 to use a -r option, but I'm finding this simply
causes false alarms the moment a nagios client is configured to r
I'm installing glusterfs-server on some new hardware. If I ssh to the
new host, sudo -i, then apt-get install glsuterfs-server, it fails with
the timeout, and pstree shows that the process is hung up in systemd-
ask-tty, but nothing ever appears on the terminal.
When I do the same process directl
I've been following this thread for a while now, as this issue also
exists in Trusty. I am using someone's custom-patched vsftpd deb. Is
there any plan to backport this release to trusty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
This issue with libpam predates mysql 5.7. It's present in trusty's
vsftpd 3.0.2-1ubuntu2.14.04.1, mysql 5.5.54-0ubuntu0.14.04.1, and the
standard libpam package. My workaround last year when I encountered the
issue was to remove both vsftpd and libpam-mysql from the default repos
and to manually
Public bug reported:
Figuring out how to use this package requires studying the package file
contents and the perl sources. The perl environment provides easy ways
to create man pages from perl doc, but the package doesn't provide a
dependency on the perl-doc package, either. I eventually figure
This change in libm.so has also broken the pam_mysql.so library, thus my
vsftpd service is also broken. My nagios started alarming about this
breaking around 6:30 am this morning, dpkg.log shows only 5 packages
were updated in this morning's automatic update: man-db, libc-bin,
libc6, and multiarch
@adconrad As it happens, it did. I just came back to update my comment
to say so and found your question.
This suggests the libc6 update (not glibc, my server doesn't have glibc
package installed) should have required a reboot? I don't recall if the
server mentioned a reboot was required in the
I second the motion. The sources this package is built from have not
been updated since 2016 and are no longer functional. This package
needs to be removed if it can't be updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
The Prometheus community has a much more current version written in GO.
https://github.com/prometheus-community/pgbouncer_exporter
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887656
Title:
promet
This behavior is documented in the README.Debian file provided with the
package.
"- The pgbouncer daemon is disabled by default, to enable it you need
to set START to 1 in /etc/default/pgbouncer."
This is not the only Debianized package to behave this way. Given the
amount of manual configurati
Public bug reported:
The prometheus-pgbouncer-exporter only opens a socket to an existing
pgbouncer daemon if pgbouncer is installed and running. Exporter does
not use a psql client or talk directly to PostgresSQL services. This
package does not need to depend on postgresql-common at all, and do
** Patch added: "0001-Correct-name-of-pgbouncer-metric.-Fixes-LP-1887656.patch"
https://bugs.launchpad.net/ubuntu/+source/prometheus-pgbouncer-exporter/+bug/1887656/+attachment/5588239/+files/0001-Correct-name-of-pgbouncer-metric.-Fixes-LP-1887656.patch
--
You received this bug notification b
19 matches
Mail list logo
