[Bug 1916235] [NEW] systemd generates errors when using NSS and LDAP
Public bug reported:
Ubuntu 20.04.2 LTS
systemd 245.4-4ubuntu3.4
The system is configured to use LDAP via nsswitch.conf:
passwd: files systemd ldap
group: files systemd ldap
shadow: files ldap
gshadow:files
Using libnss-ldap 265-5ubuntu1. When logging in with ssh there is a
slight delay, and in the logs I see:
Feb 19 12:49:54 myserver sshd[105417]: Accepted publickey for mylogin from
1.2.3.4 port 60796 ssh2: RSA SHA256:somekey
Feb 19 12:49:54 myserver sshd[105417]: pam_unix(sshd:session): session opened
for user mylogin by (uid=0)
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: reconnecting to LDAP
server...
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:54 myserver systemd-logind: nss_ldap: reconnecting to LDAP server
(sleeping 1 seconds)...
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: could not connect to any
LDAP server as (null) - Can't contact LDAP server
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: failed to bind to LDAP
server ldaps://myldapserver.mydomain/: Can't contact LDAP server
Feb 19 12:49:55 myserver systemd-logind: nss_ldap: could not search LDAP server
- Server is unavailable
Feb 19 12:49:55 myserver systemd-logind[105119]: New session 331 of user
mylogin.
With debugging for the systemd-logind process I can see the additional
information:
Feb 19 12:55:22 myserver systemd-logind[106567]: Failed to do shadow
lookup for UID 12345, ignoring: Bad file descriptor
And with strace I see:
stat("/etc/ldap.conf", {st_mode=S_IFREG|0644, st_size=9102, ...}) = 0
geteuid() = 0
socket(AF_INET, SOCK_STREAM, IPPROTO_IP) = -1 EAFNOSUPPORT (Address family not
supported by protocol)
fcntl(-1, F_SETFD, FD_CLOEXEC) = -1 EBADF (Bad file descriptor)
sendto(33, "<83>Feb 19 12:56:59 systemd-logind: nss_ldap: could not connect to
any LDAP server as (null) - Can't contact LDAP server", 120, MSG_NOSIGNAL,
NULL, 0) = 120
sendto(33, "<86>Feb 19 12:56:59 systemd-logind: nss_ldap: failed to bind to
LDAP server ldaps://myldapserver.mydomain/: Can't contact LDAP server", 131,
MSG_NOSIGNAL, NULL, 0) = 131
sendto(33, "<86>Feb 19 12:56:59 systemd-logind: nss_ldap: reconnecting to LDAP
server...", 76, MSG_NOSIGNAL, NULL, 0) = 76
Looking in /usr/lib/systemd/system/systemd-logind.service we see:
RestrictAddressFamilies=AF_UNIX AF_NETLINK
IPAddressDeny=any
So the problem is that systemd-logind can't open an AF_INET socket. And
additionally, it can't make any network connections.
This only occurs in 20.04. In 20.10 this is fixed by a newer systemd,
and it doesn't appear to be present in older systemd versions (at least,
I don't have an issue on 18.04).
The fix, from systemd 246, which is included in 20.10, is:
https://github.com/systemd/systemd/pull/15377
I have applied this change (which patches cleanly to the systemd source
package in 20.04) and the problem is resolved.
A temporary workaround for others experiencing this issue would be to
run "systemctl edit systemd-logind" and enter the following:
[Service]
RestrictAddressFamilies=AF_INET
IPAddressAllow=any
Then restart the systemd-login service, or reboot. Obviously this could
have other implications for the security of the system - I'm not sure if
processes launched by systemd-logind also have more relaxed permissions.
It'd be great if the above patch could be applied to the package in
20.04.
** Affects: systemd (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/1916235
Title:
systemd generates errors when using NSS and LDAP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916235/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638210] Re: saidar segmentation fault
This is the same as Debian bug #916220. It's fixed by libstatgrab 0.92. Unfortunately, it's not yet in Debian upstream, or Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638210 Title: saidar segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libstatgrab/+bug/1638210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838461] [NEW] STDIN discarded when using -A to attach a file
Public bug reported: mail discards STDIN when using -A to attach a file. For example: echo "My message body." | mail -s "Hello!" -A /some/data someb...@example.com The file /some/data is attached, but the message body is discarded. This is at least broken on 18.04. Debian has fixed this bug and it has been fixed upstream. I expect their patch can be used: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918806#27 ** Affects: mailutils (Ubuntu) Importance: Undecided Status: New ** Summary changed: - STDIN discard when using -A to attach a file + STDIN discarded when using -A to attach a file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838461 Title: STDIN discarded when using -A to attach a file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailutils/+bug/1838461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649877] Re: PostgreSQL dies with fatal semctl eror
An update, years later. Still broken on 16.04, but working on 18.04. Linux pgtest1604 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux postgresql-9.5 9.5.13-0ubuntu0.16.04 Linux pgtest1804 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux postgresql-10 10.4-0ubuntu0.18.04 Disappointing to see this issue received no attention on 16.04, but I suppose there is at least a way forward now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649877 Title: PostgreSQL dies with fatal semctl eror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.5/+bug/1649877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771934] Re: package libapache2-mod-php7.2 7.2.5-0ubuntu0.18.04.1 failed to install/upgrade: installed libapache2-mod-php7.2 package post-installation script subprocess returned error exit status
See bug #1782806 for what I think is the cause of this. It's a combination of a bug in the apache2 package, and different behaviour by the Puppet Apache module. Not a PHP issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771934 Title: package libapache2-mod-php7.2 7.2.5-0ubuntu0.18.04.1 failed to install/upgrade: installed libapache2-mod-php7.2 package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1771934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782806] [NEW] Typo in apache2-maintscript-helper causes MPM check to misfire
Public bug reported: The following line appears to have a typo: a2query -m "$mpm_$MPM" > /dev/null 2>&1 || a2query_ret=$? It should read: a2query -m "mpm_$MPM" > /dev/null 2>&1 || a2query_ret=$? Since $mpm is not defined. Later on there are references to enabling and disabling "mpm_$MPM". https://salsa.debian.org/apache- team/apache2/blob/master/debian/debhelper/apache2-maintscript- helper#L290 This appears to trip up the Puppet apache module since it creates a prefork module (rather than mpm_prefork), which results in the above query returning a positive response. This is what's happening in bug #1771934. Fix is obvious and trivial so can hopefully be implemented soon. Appears only to affect bionic since xenial had different code. ** Affects: apache2 (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/1782806 Title: Typo in apache2-maintscript-helper causes MPM check to misfire To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1782806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649877] [NEW] PostgreSQL dies with fatal semctl eror
Public bug reported: PostgreSQL is dying with the following error: 2016-12-14 11:21:02 UTC [4672-1] postgres@postgres FATAL: semctl(4685831, 3, SETVAL, 0) failed: Invalid argument 2016-12-14 11:21:02 UTC [3203-2] LOG: server process (PID 4672) exited with exit code 1 2016-12-14 11:21:02 UTC [3203-3] LOG: terminating any other active server processes 2016-12-14 11:21:02 UTC [3217-2] WARNING: terminating connection because of crash of another server process 2016-12-14 11:21:02 UTC [3217-3] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2016-12-14 11:21:02 UTC [3217-4] HINT: In a moment you should be able to reconnect to the database and repeat your command. 2016-12-14 11:21:02 UTC [3203-4] LOG: all server processes terminated; reinitializing 2016-12-14 11:21:02 UTC [3203-5] LOG: could not remove shared memory segment "/PostgreSQL.1769907787": No such file or directory 2016-12-14 11:21:02 UTC [3203-6] LOG: semctl(4489217, 0, IPC_RMID, ...) failed: Invalid argument 2016-12-14 11:21:02 UTC [3203-7] LOG: semctl(4521986, 0, IPC_RMID, ...) failed: Invalid argument 2016-12-14 11:21:02 UTC [3203-8] LOG: semctl(4554755, 0, IPC_RMID, ...) failed: Invalid argument 2016-12-14 11:21:02 UTC [3203-9] LOG: semctl(4587524, 0, IPC_RMID, ...) failed: Invalid argument 2016-12-14 11:21:02 UTC [3203-10] LOG: semctl(4620293, 0, IPC_RMID, ...) failed: Invalid argument 2016-12-14 11:21:02 UTC [3203-11] LOG: semctl(4653062, 0, IPC_RMID, ...) failed: Invalid argument 2016-12-14 11:21:02 UTC [3203-12] LOG: semctl(4685831, 0, IPC_RMID, ...) failed: Invalid argument 2016-12-14 11:21:02 UTC [3203-13] LOG: semctl(4718600, 0, IPC_RMID, ...) failed: Invalid argument I have determined that this happens when the postgres user has a high numbered UID, and it only happens on xenial and yakkety (trusty is fine). This is the procedure I used after spinning up a cloud image (but also verified on a normal install): sudo apt-get update sudo apt-get -y dist-upgrade sudo shutdown -r now sudo groupadd -g 99199 postgres sudo useradd -u 99199 -c "PostgreSQL administrator,,," -d /var/lib/postgresql -g postgres -s /bin/bash postgres sudo apt-get -y install postgresql autopostgresqlbackup sudo crontab -e 06 11 * * * cd / && /etc/cron.daily/autopostgresqlbackup sudo less /var/log/postgresql/*.log Obviously set the time for the cron entry so it happens as soon as possible. The manual group and user creation is to demonstrate the problem. In reality I had adduser.conf configured to put system accounts in a higher range, and the account was created normally by package installation. When I repeat exactly the same procedure but manually set the UID and GID to 199 instead, it works fine. Versions on xenial: Linux pgtest 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux postgresql-9.5 9.5.5-0ubuntu0.16.04 And on yakkety: Linux pgtest 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux postgresql-9.5 9.5.5-0ubuntu0.16.10 And on trusty: Linux pgtest 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2 15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux postgresql-9.3 9.3.15-0ubuntu0.14.04 All patches applied as of today 2016-12-14. I've tried to explore whether this is related to systemd (an obvious difference between trusty and the newer releases), or whether it's the PostgreSQL or kernel version, but haven't yet found any useful information. Happy to assist in debugging. ** Affects: postgresql-9.5 (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/1649877 Title: PostgreSQL dies with fatal semctl eror To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.5/+bug/1649877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624904] [NEW] Need to create /var/run/identd
Public bug reported:
This looks similar to #74968, but since that bug has been fixed this
must be a new/regression.
The error I see on xenial with pidentd 3.0.19.ds1-7 is:
Sep 18 18:17:09 myrtle identd[43486]: started
Sep 18 18:17:09 myrtle identd[43486]: s_open("/var/run/identd/identd.pid",
O_WRONLY): No such file or directory
I checked the package in yakkety and it includes this change:
--- debian/pidentd.tmpfile 1970-01-01 01:00:00.0 +0100
+++ debian.new/pidentd.tmpfile 2016-06-08 21:39:12.0 +0100
@@ -0,0 +1 @@
+d /var/run/identd 0755 identd nogroup - -
By creating an /etc/tmpfiles.d/pidentd.conf with that line then the
problem is resolved.
So a solution would be to update the xenial package to include that
change, or maybe just backport the newer yakkety package if the other
changes look safe.
** Affects: pidentd (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/1624904
Title:
Need to create /var/run/identd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidentd/+bug/1624904/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548009] Re: ZFS pools should be automatically scrubbed
Could /usr/lib/zfs-linux/scrub not just give the full path to zpool instead? Then PATH wouldn't need modifying at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548009 Title: ZFS pools should be automatically scrubbed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1548009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1600579] [NEW] zfsutils-linux scrub cron job fails
Public bug reported:
The cron job for zfsutils-linux fails to run. The problem is that $PATH
(on xenial, at least) is set to /bin:/usr/bin. The zpool binary is in
/sbin and the /usr/lib/zfs-linux/scrub script (below) doesn't give the
full path or modify $PATH. Further, the 2>&1 ensures that the useful
error is sent to awk and not stderr where it'd be more easily noticed.
The fix is to just s,zpool,/sbin/zpool, in the script. And probably
remove the stderr redirection, since I'm not sure if it's actually
useful here.
This is the script as it currently is, for reference:
#!/bin/sh -eu
# Scrub all healthy pools.
zpool list -H -o health,name 2>&1 | \
awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
while read pool
do
zpool scrub "$pool"
done
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
The cron job for zfsutils-linux fails to run. The problem is that $PATH
(on xenial, at least) is set to /bin:/usr/bin. The zpool binary is in
/sbin and the script (below) doesn't give the full path or modify $PATH.
Further, the 2>&1 ensures that the useful error is sent to awk and not
stderr where it'd be more easily noticed.
The fix is to just s,zpool,/sbin/zpool, in the script. And probably
remove the stderr redirection, since I'm not sure if it's actually
useful here.
+ This is the script as it currently is, for reference:
+
#!/bin/sh -eu
# Scrub all healthy pools.
zpool list -H -o health,name 2>&1 | \
- awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
+ awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
while read pool
do
- zpool scrub "$pool"
+ zpool scrub "$pool"
done
** Description changed:
The cron job for zfsutils-linux fails to run. The problem is that $PATH
(on xenial, at least) is set to /bin:/usr/bin. The zpool binary is in
- /sbin and the script (below) doesn't give the full path or modify $PATH.
- Further, the 2>&1 ensures that the useful error is sent to awk and not
- stderr where it'd be more easily noticed.
+ /sbin and the /usr/lib/zfs-linux/scrub script (below) doesn't give the
+ full path or modify $PATH. Further, the 2>&1 ensures that the useful
+ error is sent to awk and not stderr where it'd be more easily noticed.
The fix is to just s,zpool,/sbin/zpool, in the script. And probably
remove the stderr redirection, since I'm not sure if it's actually
useful here.
This is the script as it currently is, for reference:
#!/bin/sh -eu
# Scrub all healthy pools.
zpool list -H -o health,name 2>&1 | \
awk 'BEGIN {FS="\t"} {if ($1 ~ /^ONLINE/) print $2}' | \
while read pool
do
zpool scrub "$pool"
done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600579
Title:
zfsutils-linux scrub cron job fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1600579/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 499585] Re: /etc/cups/interfaces doesn't exist; lpadmin fails to add interface scripts
And 12.04... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/499585 Title: /etc/cups/interfaces doesn't exist; lpadmin fails to add interface scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/499585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054605] Re: Mount very slow for 22TB ext4 filesystem on Ubuntu Server 12.04.1 running kernel 3.2.0-30-generic
This appears fixed to me in the latest kernel: linux-image-3.2.0-32-generic 3.2.0-32.51 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054605 Title: Mount very slow for 22TB ext4 filesystem on Ubuntu Server 12.04.1 running kernel 3.2.0-30-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1054605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066942] [NEW] cps_ plugin autodetection is broken
Public bug reported:
Summary: Please apply https://github.com/munin-
monitoring/munin/commit/3281ce622bbd5dbf2c0ac5be8c951cb9a488e47a to the
munin-node package.
I'm using these packages:
ii munin-common 1.4.6-3ubuntu3.1 network-wide
graphing framework (common)
ii munin-node 1.4.6-3ubuntu3.1 network-wide
graphing framework (node)
On 12.04.1 (precise).
The problem is with the cps_ plugin. It suggests the following plugins:
# /usr/share/munin/plugins/cps_ suggest
cps_1.1.1.1_21
cps_1.1.1.1_80
cps_1.1.1.1_873
cps_2.2.2.2_21
cps_2.2.2.2_80
cps_2.2.2.2_873
When these get created by munin-node-configure I end up with the
following:
# ls -la /etc/munin/plugins/cps_cps_212.219.56.18*
lrwxrwxrwx 1 root root 29 Aug 18 18:37 /etc/munin/plugins/cps_cps_1.1.1.1_21 ->
/usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Aug 18 18:37 /etc/munin/plugins/cps_cps_1.1.1.1_80 ->
/usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Aug 18 18:37 /etc/munin/plugins/cps_cps_1.1.1.1_873
-> /usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Oct 15 16:26 /etc/munin/plugins/cps_cps_2.2.2.2_21 ->
/usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Aug 18 18:37 /etc/munin/plugins/cps_cps_2.2.2.2_80 ->
/usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Oct 15 16:26 /etc/munin/plugins/cps_cps_2.2.2.2_873
-> /usr/share/munin/plugins/cps_
The code in cps_ parses $0:
unless ($0 =~ /cps(?:_([^_]+)|)_(.+)\s*$/) {
die "Could not parse name $0.\n";
}
my $vip = $1;
my $port = $2;
As you can see, the cps_cps_ should be cps_. It's doubling this up which
breaks the regex and therefore breaks the plugin.
The fix is quite simple:
--- cps_.orig 2012-10-15 16:14:14.580595524 +0100
+++ cps_2012-10-15 16:14:25.092431645 +0100
@@ -103,7 +103,7 @@
foreach my $vip (sort keys %{$ipvs}) {
foreach my $port (sort keys %{$ipvs->{$vip}}) {
- print "cps_${vip}_$port\n";
+ print "${vip}_$port\n";
}
}
exit 0;
This creates the plugins with a single cps_ at the start and then
everything works as expected.
The fix can also be seen upstream here:
https://github.com/munin-
monitoring/munin/commit/3281ce622bbd5dbf2c0ac5be8c951cb9a488e47a
It'd be great if this fix could be applied.
** Affects: munin (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/1066942
Title:
cps_ plugin autodetection is broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1066942/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054605] Re: Mount very slow for 22TB ext4 filesystem on Ubuntu Server 12.04.1 running kernel 3.2.0-30-generic
I've tested the latest mainline kernel (v3.6-rc7-quantal, as requested) and it's working fine. The latest precise kernel (released after my last update) still doesn't work: linux-image-3.2.0-31-generic 3.2.0-31.50 But this one does: linux-image-3.6.0-030600rc7-generic 3.6.0-030600rc7.201209232235 linux-image-extra-3.6.0-030600rc7-generic 3.6.0-030600rc7.201209232235 I hope this helps. ** Tags removed: needs-upstream-testing ** Tags added: kernel-fixed-upstream ** Tags removed: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054605 Title: Mount very slow for 22TB ext4 filesystem on Ubuntu Server 12.04.1 running kernel 3.2.0-30-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1054605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054605] Re: Mount very slow for 22TB ext4 filesystem on Ubuntu Server 12.04.1 running kernel 3.2.0-30-generic
I'm seeing the same issue on a 13T filesystem. I have two identical machines, but one has been updated more than the other. The one with 3.2.0-29.46 works fine, whilst the one with 3.2.0-30.48 has the long delays when mounting the filesystem. Happy to provide output of apport-collect if required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054605 Title: Mount very slow for 22TB ext4 filesystem on Ubuntu Server 12.04.1 running kernel 3.2.0-30-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1054605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1052815] Re: Perl warnings break plugins
Sorry, what an obvious thing to forget! munin-common 1.4.6-3ubuntu3.1 munin-node 1.4.6-3ubuntu3.1 This is on Ubuntu 12.04.1 (precise). I figured they'd probably have been fixed upstream, but it'd be good to see the fix make its way in to the Ubuntu package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052815 Title: Perl warnings break plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1052815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1052815] [NEW] Perl warnings break plugins
Public bug reported: munin-node-configure -sh # The following plugins caused errors: # apache_processes: # Junk printed to stderr # users: # Junk printed to stderr /usr/share/munin/plugins/users Use of qw(...) as parentheses is deprecated at /usr/share/munin/plugins/users line 82. tty.value 0 pty.value 0 pts.value 3 X.value 0 other.value 0 /usr/share/munin/plugins/apache_processes Use of qw(...) as parentheses is deprecated at /usr/share/munin/plugins/apache_processes line 164. busy80.value 50 idle80.value 50 free80.value 1167 ** Affects: munin (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/1052815 Title: Perl warnings break plugins To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1052815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 227869] Re: Server installer should not use -server kernel for non-PAE CPU's
Adding my voice as well, and asking about workarounds. I ran into the same problem with installing 8.04.1 server onto a USB disk for use with a VIA CPU for a low power, silent, personal server. Is there a workaround or easy way to switch kernels? I'm not super technical, but if someone pointed me to directions I could probably follow them. Thanks in advance. -- Server installer should not use -server kernel for non-PAE CPU's https://bugs.launchpad.net/bugs/227869 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 201485] Re: package sun-java6-bin 6-03-0ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 127
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/12615357/Dependencies.txt ** Attachment added: "DpkgTerminalLog.gz" http://launchpadlibrarian.net/12615358/DpkgTerminalLog.gz -- package sun-java6-bin 6-03-0ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 127 https://bugs.launchpad.net/bugs/201485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 201485] [NEW] package sun-java6-bin 6-03-0ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 127
Public bug reported: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=7.10 DISTRIB_CODENAME=gutsy DISTRIB_DESCRIPTION="Ubuntu 7.10" ProblemType: Package Architecture: i386 Date: Tue Mar 11 07:34:56 2008 DistroRelease: Ubuntu 7.10 ErrorMessage: subprocess post-installation script returned error exit status 127 Package: sun-java6-bin 6-03-0ubuntu2 PackageArchitecture: i386 SourcePackage: sun-java6 Title: package sun-java6-bin 6-03-0ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 127 Uname: Linux ubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux ** Affects: sun-java6 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package -- package sun-java6-bin 6-03-0ubuntu2 failed to install/upgrade: subprocess post-installation script returned error exit status 127 https://bugs.launchpad.net/bugs/201485 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
