[Bug 1887656] Re: prometheus-pgbouncer-exporter is incompatible with pgbouncer
** 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887656 Title: prometheus-pgbouncer-exporter is incompatible with pgbouncer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-pgbouncer-exporter/+bug/1887656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972710] [NEW] Package unnecessarily depend son postgresql-common
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 doing so leaves the client with a full, unexpected, and unmanaged installation of postgreslq-server running on it. If this is being done to re-use the postgres service account, this is a security issue as the unexpected sql server never gets configured off the package defaults. This package should either reuse the generic service account, or just create one for itself. ** Affects: prometheus-pgbouncer-exporter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972710 Title: Package unnecessarily depend son postgresql-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-pgbouncer-exporter/+bug/1972710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322186] Re: pgbouncer init.d fails to start with no message when start=0
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 configuration PGBouncer needs to talk to a production postgresql server, it is logical to have it disabled after initial install, anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322186 Title: pgbouncer init.d fails to start with no message when start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgbouncer/+bug/1322186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887656] Re: prometheus-pgbouncer-exporter is incompatible with pgbouncer
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: prometheus-pgbouncer-exporter is incompatible with pgbouncer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-pgbouncer-exporter/+bug/1887656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887656] Re: prometheus-pgbouncer-exporter is incompatible with pgbouncer
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://bugs.launchpad.net/bugs/1887656 Title: prometheus-pgbouncer-exporter is incompatible with pgbouncer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-pgbouncer-exporter/+bug/1887656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906710] [NEW] Ansible 2.5 too old to handle Python 3.8 on Ubuntu 20.04
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 playbooks for use on our network. I quickly encountered issues attempting to do anything requiring python on the targeted hosts if those hosts are Ubuntu 20.04 or newer. Python 3.8 is the oldest version available for install on Ubuntu 20.04. Ansible 2.5 is not compatible with Python 3.8 on targeted hosts, it requires Python 3.7 or Python 2.x on the targeted hosts. I do not have the political power here to install python 2.x on hosts that don't already have it installed so that is not a viable solution. Ansible 2.5 is using long-deprecated library calls that have been removed in Python 3.8, which is the only version available for Ubuntu 20.04. More recent releases of Ansible have adjusted for the change in the Python 3.8 libraries. These releases are not available in the 18.04 LTS repos. Thus, version of ansible in 18.04 LTS is not able to manage targets running Ubuntu 20.04 or newer. I have checked bionic-updates and bionic-backports and there is no newer release of Ansible present. We need a backport release of Ansible made available for Ubuntu 18.04 so that 18.04 control hosts can manage Ubuntu 20.04 and newer targets. I've resorted to purging the LTS ansible packages and installing Ansible with pip3 instead, and using venv to run it on my personal login. This really isn't a good solution to the problem, however. Simple test: ubuntu 18.04$ ansible all -m ping where the hosts file ansible is reading contains a mix of Ubuntu 16.04, 18.04, and 20.04 targets. I expect them to all respond with a 'pong' message. I get 'pong' back from Ubuntu 18.04 and older hosts. For Ubuntu 20.04 and newer hosts, I get a stack trace out of python complaining about the inability to identify the release and dist on the target. ** Affects: ansible (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906710 Title: Ansible 2.5 too old to handle Python 3.8 on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1906710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
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 is some perl modules installed via CPAN, and none of those touch anything to do with Systemd, so I'm not sure why this is happening. I did see a post-install upgrade issue with the rkhunter package failing to find /usr/bin/egrep, but I ignored that issue and continued. I'm going to rollback, look for the lib involved, and see if I can remove it before retrying the do-release-upgrade -d to 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712748] Re: package glusterfs-server 3.11.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 directly on the console, it installs as expected. This is installing glusterfs-server 3.13.2-1build1 directly from Ubuntu 18.04 repos, not from a PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712748 Title: package glusterfs-server 3.11.2-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/glusterfs/+bug/1712748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825043] [NEW] The new check_load settings are too low
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 respond to check_load with nrpe. I'm having to go back through all the 18.04 clients I monitor and manually override the default values with sane values placed in nrpe_local.cfg instead. I don't know if the -r option simply isn't working as expected, or if the default values now used are just too low. A newly-built 18.04 is running BitDefender that that alone is causing non-stop warnings and criticals from nagios now, because now it's warning at 15% of available CPU. Old version: /etc/nagios/nrpe.cfg:command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c 30,25,20 New version: /etc/nagios/nrpe.cfg:command[check_load]=/usr/lib/nagios/plugins/check_load -r -w .15,.10,.05 -c .30,.25,.20 You want a host to have its cpu load up to match the number of cores it has, so you'd want these up around 1, at minimum, for 100% busy, not 15% of busy. That's just silly. ** Affects: nagios-nrpe (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825043 Title: The new check_load settings are too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1825043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
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 systemd package upgrade were the two SuperMicros running bonded 10G interfaces. On both of those hosts, the bond defined in netplan seems to have lost its configuration during the systemd upgrade. There were multiple kern.log messages regarding the bond leaving one of its ports in a disabled state after the update. Both hosts logged this on the same second that dpkg.log shows the systemd package itself entering 'status installed', so I'm confident it was that systemd package rather than pam-systemd that followed several seconds later. I am still willing to provides logs and configurations if you tell me what you need to see. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
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, but a full reboot did. We are using the default 18.04 netplan setup, we haven't reversed back to ifupdown like the other reporter. Both hosts lost their networking immediately after the systemd update was applied this morning, which installed version 237-3ubuntu10.19. I can delve through them to find any logs or config files you want. These are Supermicro rack mounts with dual 10G interfaces, built as headless servers, so no ubuntu-desktop or X11 is installed on them. We have sssd installed on these with the required pam customizations to configure sssd to live in our Active Directory environment. pam-auth- updated printed about local mods to common-* so it wasn't updating. Those are the only unusual outputs from this mornings unattended- upgrades-dpkg.log file. I can attach any logs or other files you care to view. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
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 it over later this morning. Two identical hosts did not apply this systemd update this morning and they're both still online. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694922] Re: /etc/cron.monthly/ieee-data fails every month on redirected URLS
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ieee-data/+bug/1694922/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662137] Re: 16.04 recovery shell works only for two minutes
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 partition from there. A 5 minute process has become a two-day nightmare. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662137 Title: 16.04 recovery shell works only for two minutes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1662137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1681474] [NEW] Man Pages missing, dependency missing
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 figured out what I needed to do because I'm a perl developer already. Could this package please: *) Provide /usr/share/doc/metainit/README *) /etc/metainit/SKELETON *) /usr/share/man/man3/MetaInit::Parse.3.gz, or more appropriately a man5/metainit file format man page *) a See Also section in the set of man pages that reference each other Ubuntu 14.04.05 LTS metainit 0.0.5 ** Affects: metainit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1681474 Title: Man Pages missing, dependency missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metainit/+bug/1681474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 1574900] Re: libpam-mysql undefined symbol: make_scrambled_password
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 install vsdfpd from
http://dinofly.com/files/linux/vsftpd_3.0.2-1ubuntu2_amd64.deb
https://ubuntuforums.org/archive/index.php/t-2218804.html is the spot
where I found this fix a year ago. I've been waiting for an official
fix ever since but if one has been released, I missed it. I'm still
running this custom version.
It is entirely possible that the bug I'm experiencing with 5.5 is
different but related to what is causing the problem covered in 1574900,
but as the symptoms seem to be identical, I tend to assume it is the
same bug.
The host involved here is my employer's primary public ftp server where
we give 3rd parties (customers, contractors, etc) the ability to upload
large files and we have a simple mysql db where their virtual users are
kept. If you need a guinea pig host for testing, I can easily spin up a
clone of this system for testing purposes.
-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Nish
Aravamudan
Sent: Monday, March 20, 2017 11:56 AM
To: Joi L. Ellis
Subject: [Bug 1574900] Re: libpam-mysql undefined symbol:
make_scrambled_password
@jlellis: There is no MySQL 5.7 in Trusty. Are you using a PPA? Or are
you saying that MySQL 5.5 also has this problem?
--
You received this bug notification because you are subscribed to pam- mysql in
Ubuntu.
Matching subscriptions: pam-mysql
https://bugs.launchpad.net/bugs/1574900
Title:
libpam-mysql undefined symbol: make_scrambled_password
Status in pam-mysql package in Ubuntu:
Fix Released
Status in pam-mysql source package in Xenial:
Fix Committed
Status in pam-mysql source package in Yakkety:
Fix Committed
Status in pam-mysql package in Fedora:
Unknown
Bug description:
[Impact]
* libpam-mysql is unable to be used because of an upstream symbol
change in libmysqlclient.
* Upstream libpam-mysql has fixed this by updating the source to use
the now-exported API.
[Test Case]
Steps to reproduce (with vsftpd):
Installation requirements: mysqlserver 5.7.x, libpam-mysql, vsftpd
create vsftpd user:
useradd --home /home/vsftpd --gid nogroup -m --shell /bin/false vsftpd
create mysql database and user:
== // Start SQL
CREATE DATABASE vsftpd;
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP ON vsftpd.* TO
'vsftpd'@'localhost' IDENTIFIED BY 'ftpdpass';
GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, DROP ON vsftpd.* TO
'vsftpd'@'localhost.localdomain' IDENTIFIED BY 'ftpdpass';
FLUSH PRIVILEGES;
USE vsftpd;
CREATE TABLE `accounts` (
`id` INT NOT NULL AUTO_INCREMENT PRIMARY KEY ,
`username` VARCHAR( 30 ) NOT NULL ,
`pass` VARCHAR( 50 ) NOT NULL ,
UNIQUE (
`username`
));
insert into accounts(username,pass) values('user',password('password'));
==// End SQL
Configure PAM:
insert into /etc/pam.d/vsftpd:
auth required pam_mysql.so verbose=1 user=vsftpd host=localhost db=vsftpd
table=accounts usercolumn=username passwdcolumn=pass crypt=3 passwd=ftpdpass
account required pam_mysql.so verbose=1 user=vsftpd host=localhost
db=vsftpd table=accounts usercolumn=username passwdcolumn=pass crypt=3
passwd=ftpdpass
Configure vsftpd (/etc/vsftpd.conf) :
listen=YES
anonymous_enable=NO
local_enable=YES
write_enable=YES
local_umask=022
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
nopriv_user=vsftpd
chroot_local_user=YES
secure_chroot_dir=/var/run/vsftpd
pam_service_name=vsftpd
guest_enable=YES
guest_username=vsftpd
local_root=/home/vsftpd/$USER
user_sub_token=$USER
virtual_use_local_privs=YES
restart vsftpd:
/etc/init.d/vsftpd restart
check /var/log/auth.log
[Regression Potential]
* There is currently no fix or workaround, as the library is
basically broken as installed from Ubuntu.
* I believe the regression potential to be very low because the
current code does not work.
---
In Ubuntu 16.04, the libpam-mysql package does not work. It crashes
with the below error:
PAM unable to dlopen(pam_mysql.so): /lib/security/pam_mysql.so:
undefined symbol: make_scrambled_password
I fixed this issue by download the source for the package and applying
the patches that come from this source RPM:
http://dinofly.com/files/linux/pam_mysql-0.7-0.20.rc1.fc23.src.rpm
I then created unofficial packages after applying the patch. They can
be downloaded here:
http://www.dinofly.com/files/linux/libpam-mysql_0.7~RC1-4ubuntu3_amd64.deb
http://www.dinofly.com/files/linux/libpam-mysql_0.7~RC1-4ubuntu3_i386.deb
[Bug 1574900] Re: libpam-mysql undefined symbol: make_scrambled_password
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 Ubuntu. https://bugs.launchpad.net/bugs/1574900 Title: libpam-mysql undefined symbol: make_scrambled_password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-mysql/+bug/1574900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
@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 motd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585614 Title: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
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-support (all from amd64 arch.) The error in auth.log is: vsftpd: PAM unable to dlopen(pam_mysql.so): /lib/x86_64-linux-gnu/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference. vsftpd: PAM adding faulty module: pam_mysql.so (I had to manually type the above, as MS hyperv can't do simple clipboard operations like Xen has managed for over a decade now. So please forgive any typos that might be there.) I don't think this is an apache or pam bug, as libm.so is provided by libc6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585614 Title: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
