[Group.of.nepali.translators] [Bug 1823098] Re: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf
** Also affects: ntp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ntp (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1823098 Title: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf Status in cloud-images: New Status in ntp package in Ubuntu: New Status in ntp source package in Xenial: New Status in ntp source package in Bionic: New Status in ntp source package in Focal: New Bug description: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. | ubuntu@juju-453c71-0:~$ cat /etc/*release | DISTRIB_RELEASE=16.04 | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" | VERSION_ID="16.04" | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp | ntp: /etc/init.d/ntp | ubuntu@juju-453c71-0:~$ apt-cache policy ntp | ntp: | Installed: 1:4.2.8p4+dfsg-3ubuntu5.9 | Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9 | Version table: | *** 1:4.2.8p4+dfsg-3ubuntu5.9 500 | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages Thanks, Haw To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1823098/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1940011] Re: Reduce cron spam from weekly update-notifier-common
** No longer affects: ubuntu-release-upgrader (Ubuntu Trusty) ** No longer affects: update-notifier (Ubuntu Trusty) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1940011 Title: Reduce cron spam from weekly update-notifier-common Status in ubuntu-release-upgrader package in Ubuntu: New Status in update-notifier package in Ubuntu: New Status in ubuntu-release-upgrader source package in Xenial: New Status in update-notifier source package in Xenial: New Status in ubuntu-release-upgrader source package in Bionic: New Status in update-notifier source package in Bionic: New Status in ubuntu-release-upgrader source package in Focal: New Status in update-notifier source package in Focal: New Status in ubuntu-release-upgrader source package in Jammy: New Status in update-notifier source package in Jammy: New Status in ubuntu-release-upgrader source package in Kinetic: New Status in update-notifier source package in Kinetic: New Bug description: Hi, We get these cron spam weekly: | Received: by mysystem.mydomain.local (Postfix) | id B19E32E806B; Sun, 15 Aug 2021 06:47:03 + (UTC) | Delivered-To: root@mysystem.mydomain.local | Received: by mysystem.mydomain.local (Postfix, from userid 0) | id 9DD002E8075; Sun, 15 Aug 2021 06:47:03 + (UTC) | From: Cron Daemon | To: root@mysystem.mydomain.local | Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) | MIME-Version: 1.0 | Content-Type: text/plain; charset=UTF-8 | Content-Transfer-Encoding: 8bit | X-Cron-Env: | X-Cron-Env: | X-Cron-Env: | X-Cron-Env: | Message-Id: <20210815064703.9DD002E8075@mysystem.mydomain.local> | Date: Sun, 15 Aug 2021 06:47:03 + (UTC) | | /etc/cron.weekly/update-notifier-common: | New release '18.04.5 LTS' available. | Run 'do-release-upgrade' to upgrade to it. This is output from /etc/cron.weekly/update-notifier-common calling /usr/lib/ubuntu-release-upgrader/release-upgrade-motd That's fine for when you have a system or two, but probably not when you manage many. Any chance the cron job can be updated so stdout is silenced? So: | # Check to see whether there is a new version of Ubuntu available | /usr/lib/ubuntu-release-upgrader/release-upgrade-motd > /dev/null Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1940011/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1957128] [NEW] ifenslave fails to detach slave from bonded interface
Public bug reported: Hi, When I try to detach a slave from a bonded interface, it fails as follows: | [hloeung@myhost etc]$ sudo ifenslave -v -d bond0 ens2f1 | ens2f1: is not enslaved to bond0 It's definitely part of the bond: | [hloeung@myhost etc]$ ls /sys/class/net/bond0/ -la | grep ens | lrwxrwxrwx 1 root root0 Jan 12 02:36 lower_ens2f0 -> ../../../pci:00/:00:02.0/:05:00.0/net/ens2f0 | lrwxrwxrwx 1 root root0 Jan 12 02:36 lower_ens2f1 -> ../../../pci:00/:00:02.0/:05:00.1/net/ens2f1 Running ifenslave with `sh -x` shows this: | ... | + [ -z ens2f1 ] | + master=bond0 | + shift | + [ -d /sys/class/net/bond0 ] | + [ -d /sys/class/net/bond0/bonding ] | + [ = 1 ] | + [ -d /sys/class/net/ens2f1 ] | + [ -z 1 ] | + [ ! -h /sys/class/net/bond0/slave_ens2f1 ] | + echo ens2f1: is not enslaved to bond0 | ens2f1: is not enslaved to bond0 | + continue | + exit 0 I think the bug is in this code: | if [ -z "$DETACH" ]; then | if [ -h "/sys/class/net/$master/slave_$slave" ] || |[ -h "/sys/class/net/$master/lower_$slave" ]; then | echo "$slave: already enslaved to $master" >&2 | continue | fi | ... | else | if [ ! -h "/sys/class/net/$master/slave_$slave" ] || |[ ! -h "/sys/class/net/$master/lower_$slave" ]; then | echo "$slave: is not enslaved to $master" >&2 | continue | fi Where rather than ||, it should be && in the else block (for detaching). ** Affects: ifenslave (Ubuntu) Importance: Undecided Status: Invalid ** Affects: ifenslave (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Changed in: ifenslave (Ubuntu) Status: New => Invalid ** Also affects: ifenslave (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ifenslave (Ubuntu Xenial) Status: New => Invalid ** Description changed: Hi, When I try to detach a slave from a bonded interface, it fails as follows: | [hloeung@myhost etc]$ sudo ifenslave -v -d bond0 ens2f1 | ens2f1: is not enslaved to bond0 It's definitely part of the bond: | [hloeung@myhost etc]$ ls /sys/class/net/bond0/ -la | grep ens | lrwxrwxrwx 1 root root0 Jan 12 02:36 lower_ens2f0 -> ../../../pci:00/:00:02.0/:05:00.0/net/ens2f0 | lrwxrwxrwx 1 root root0 Jan 12 02:36 lower_ens2f1 -> ../../../pci:00/:00:02.0/:05:00.1/net/ens2f1 Running ifenslave with `sh -x` shows this: | ... | + [ -z ens2f1 ] | + master=bond0 | + shift | + [ -d /sys/class/net/bond0 ] | + [ -d /sys/class/net/bond0/bonding ] | + [ = 1 ] | + [ -d /sys/class/net/ens2f1 ] | + [ -z 1 ] | + [ ! -h /sys/class/net/bond0/slave_ens2f1 ] | + echo ens2f1: is not enslaved to bond0 | ens2f1: is not enslaved to bond0 | + continue | + exit 0 I think the bug is in this code: | if [ -z "$DETACH" ]; then | if [ -h "/sys/class/net/$master/slave_$slave" ] || |[ -h "/sys/class/net/$master/lower_$slave" ]; then | echo "$slave: already enslaved to $master" >&2 | continue | fi | ... | else - | if [ ! -h "/sys/class/net/$master/slave_$slave" ] && + | if [ ! -h "/sys/class/net/$master/slave_$slave" ] || |[ ! -h "/sys/class/net/$master/lower_$slave" ]; then | echo "$slave: is not enslaved to $master" >&2 | continue | fi - Where rather than &&, it should be || in the else block (for detaching). + Where rather than ||, it should be && in the else block (for detaching). -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1957128 Title: ifenslave fails to detach slave from bonded interface Status in ifenslave package in Ubuntu: Invalid Status in ifenslave source package in Xenial: Invalid Bug description: Hi, When I try to detach a slave from a bonded interface, it fails as follows: | [hloeung@myhost etc]$ sudo ifenslave -v -d bond0 ens2f1 | ens2f1: is not enslaved to bond0 It's definitely part of the bond: | [hloeung@myhost etc]$ ls /sys/class/net/bond0/ -la | grep ens | lrwxrwxrwx 1 root root0 Jan 12 02:36 lower_ens2f0 -> ../../../pci:00/:00:02.0/:05:00.0/net/ens2f0 | lrwxrwxrwx 1 root root0 Jan 12 02:36 lower_ens2f1 -> ../../../pci:00/:00:02.0/:05:00.1/net/ens2f1 Running ifenslave with `sh -x` shows this: | ... | + [ -z ens2f1 ] | + master=bond0 | + shift | + [ -d /sys/class/net/bond0 ] | + [ -d /sys/class/net/bond0/bonding ] | + [ = 1 ] | + [ -d /sys/class/net/ens2f1 ] | + [ -z 1 ] | + [ ! -h /sys/class/net/bond0/slave_ens2f1 ] | + echo ens2f1: is not enslaved to bond0 | ens2f1: is not enslaved to bond0 | +
[Group.of.nepali.translators] [Bug 1565744] Re: "Mutex file:${APACHE_LOCK_DIR} default" should be disabled by default on Linux because it leads to errors
Can we get the following backported to Xenial (so 2.4.18-2ubuntu3.14)?
| apache2 (2.4.20-1) unstable; urgency=medium
|
| * On Linux, use pthread mutexes. On kfreebsd/hurd, continue using fctnl
| because they lack robust pthred mutexes. LP: #1565744, #1527044
Seeing it on a couple of Xenial hosts and the fix being to comment out
the following line from /etc/apache2/apache2.conf:
| Mutex file:${APACHE_LOCK_DIR} default
** Also affects: apache2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: apache2 (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1565744
Title:
"Mutex file:${APACHE_LOCK_DIR} default" should be disabled by default
on Linux because it leads to errors
Status in apache2 package in Ubuntu:
Fix Released
Status in apache2 source package in Xenial:
Confirmed
Bug description:
OS:
Ubuntu 14.04 LTS
Kernel:
3.13.0-79-generic x86_64
Apache:
2.4.7-1ubuntu4.5
In the default Apache 2.4 config on Ubuntu 14.04 LTS is the following
set in /etc/apache2/apache2.conf:
Mutex file:${APACHE_LOCK_DIR} default
(/debian/config-dir/apache2.conf in
http://archive.ubuntu.com/ubuntu/pool/main/a/apache2/apache2_2.4.7-1ubuntu4.5.debian.tar.gz)
which leads to the following output of "apache2ctl -t -D
DUMP_RUN_CFG":
Mutex default: dir="/var/lock/apache2" mechanism=fcntl
This leads constantly to a lot of these warning/emergency messages on
a server with 200 busy worker threads, 100 Requests/s, 300 KB/s:
[Tue Mar 08 16:08:18.596653 2016] [ssl:warn] [pid 8339:tid
140182179256064] (35)Resource deadlock avoided: AH02026: Failed to
acquire SSL session cache lock
[Wed Mar 09 07:09:31.099331 2016] [mpm_worker:emerg] [pid 26526:tid
139668485949184] (35)Resource deadlock avoided: AH00273:
apr_proc_mutex_lock failed. Attempting to shutdown process gracefully.
Solution (as suggested by Yann Ylavic from Apache):
Commenting (removing) the Mutex directive, which leads to the following
output of "apache2ctl -t -D DUMP_RUN_CFG":
Mutex default: dir="/var/run/apache2/" mechanism=default
Then, there are no error messages anymore.
For the discussion, see the corresponding Apache httpd-users mailing
list thread:
http://httpd.markmail.org/message/c7w5aujfmy2kfazi
(thread subject 'Lots of messages "[ssl:warn] Resource deadlock
avoided: AH02026: Failed to acquire SSL session cache lock"' from
2016-03-08)
Here some more information:
# apache2ctl -V
Server version: Apache/2.4.7 (Ubuntu)
Server built: Jul 24 2015 17:25:11
Server's Module Magic Number: 20120211:27
Server loaded: APR 1.5.1-dev, APR-UTIL 1.5.3
Compiled using: APR 1.5.1-dev, APR-UTIL 1.5.3
Architecture: 64-bit
Server MPM: worker
threaded: yes (fixed thread count)
forked: yes (variable process count)
Server compiled with
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=256
-D HTTPD_ROOT="/etc/apache2"
-D SUEXEC_BIN="/usr/lib/apache2/suexec"
-D DEFAULT_PIDLOG="/var/run/apache2.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="mime.types"
-D SERVER_CONFIG_FILE="apache2.conf"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1565744/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1823098] [NEW] /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf
Public bug reported: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. | ubuntu@juju-453c71-0:~$ cat /etc/*release | DISTRIB_RELEASE=16.04 | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" | VERSION_ID="16.04" | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp | ntp: /etc/init.d/ntp | ubuntu@juju-453c71-0:~$ apt-cache policy ntp | ntp: | Installed: 1:4.2.8p4+dfsg-3ubuntu5.9 | Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9 | Version table: | *** 1:4.2.8p4+dfsg-3ubuntu5.9 500 | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages Thanks, Haw ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Affects: ntp (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. + | ubuntu@juju-453c71-0:~$ cat /etc/*release + | DISTRIB_RELEASE=16.04 + | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" + | VERSION_ID="16.04" + + | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp + | ntp: /etc/init.d/ntp + + | ubuntu@juju-453c71-0:~$ apt-cache policy ntp + | ntp: + | Installed: 1:4.2.8p4+dfsg-3ubuntu5.9 + | Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9 + | Version table: + | *** 1:4.2.8p4+dfsg-3ubuntu5.9 500 + | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages + Thanks, Haw ** Also affects: ntp (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1823098 Title: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf Status in ntp package in Ubuntu: New Status in ntp source package in Xenial: New Bug description: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. |
[Group.of.nepali.translators] [Bug 1466926] Re: reload apache2 with mpm_event cause scoreboard is full
** Also affects: apache2 (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: apache2 (Ubuntu Zesty) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1466926 Title: reload apache2 with mpm_event cause scoreboard is full Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Trusty: Confirmed Status in apache2 source package in Xenial: Confirmed Status in apache2 source package in Zesty: Fix Released Bug description: On the clean install Ubuntu 14.04 with Apache without almost any client load the Apache server with the command "service apache2 reload" itself allocates slots marked with "Gracefully finishing" for which rejects new connections. For full rejection of new requests is sufficient to perform 4x command "service apache2 reload". Ubuntu 14.04.2 LTS Apache 2.4.7-ubuntu4.4 (mpm_event) Kernel 2.16.0-30-generic Reproduce problem: # 1/ service apache2 start __W_ ___. .. 2/ service apache2 reload .GGG GGG__W__ __ 3/ service apache2 reload ___W_GGG GGG__... .. 4/ service apache2 reload G___ W_ 5/ service apache2 reload -> Server Apache not responding With logs in apache error log file: ... [mpm_event:error] [pid 9381:tid 1234563234] AH00485: scoreboard is full, not at MaxRequestWorkers ... # My workaround was change to MPM module from "mpm_event" to "mpm_worker". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1466926/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1466926] Re: reload apache2 with mpm_event cause scoreboard is full
** Also affects: apache2 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apache2 (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apache2 (Ubuntu Xenial) Status: New => Confirmed ** Changed in: apache2 (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1466926 Title: reload apache2 with mpm_event cause scoreboard is full Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Trusty: Confirmed Status in apache2 source package in Xenial: Confirmed Bug description: On the clean install Ubuntu 14.04 with Apache without almost any client load the Apache server with the command "service apache2 reload" itself allocates slots marked with "Gracefully finishing" for which rejects new connections. For full rejection of new requests is sufficient to perform 4x command "service apache2 reload". Ubuntu 14.04.2 LTS Apache 2.4.7-ubuntu4.4 (mpm_event) Kernel 2.16.0-30-generic Reproduce problem: # 1/ service apache2 start __W_ ___. .. 2/ service apache2 reload .GGG GGG__W__ __ 3/ service apache2 reload ___W_GGG GGG__... .. 4/ service apache2 reload G___ W_ 5/ service apache2 reload -> Server Apache not responding With logs in apache error log file: ... [mpm_event:error] [pid 9381:tid 1234563234] AH00485: scoreboard is full, not at MaxRequestWorkers ... # My workaround was change to MPM module from "mpm_event" to "mpm_worker". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1466926/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1579278] Re: Consider changing default CPU frequency scaling governor back to "performance"
As Theodore Ts'o has pointed out[1]: """ ... with modern Intel processors, the ondemand CPU governor is actually counterproductive because waking up to decide whether the CPU is idle keeps it from entering the deepest sleep states, and so (somewhat counterintuitively) the performance governor will actually result in the best battery life. """ [1]https://plus.google.com/+TheodoreTso/posts/2vEekAsG2QT ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1579278 Title: Consider changing default CPU frequency scaling governor back to "performance" Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01%
[Group.of.nepali.translators] [Bug 1554848] Re: Please randomise automatic updates over a longer period
** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: New Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Bug description: Load on the main Ubuntu archive servers is rather peakish, and tends to create a traffic peak on our Internet links at fairly regular times each day, preventing customers from accessing the archive. This impacts the cloud archive mirrors using the ubuntu-repository-cache charm also, because they are hitting a squid cache which is backed by the main archive. This effect will be even more pronounced under the recently-announced automatic update policy for xenial. One solution which would alleviate this to some extent would be to spread the load over a longer period by increasing the random sleep time in the daily update script from 30 minutes to, say, 1-2 hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1554848/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
