[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
The O'Reilly book _DNS and BIND_ says:
[QUOTE]
10.4.3.2 Interface interval
We've said already that BIND, by default, listens on all of a host's
network interfaces. BIND 8 is actually smart enough to notice when a
network interface on the host it's running on comes up or goes down. To
do this, it periodically scans the host's network interfaces. This
happens once each interface interval, which is 60 minutes by default. If
you know the host your name server runs on has no dynamic network
interfaces, you can disable scanning for new interfaces by setting the
interface interval to zero to avoid unnecessary hourly overhead:
options {
interface-interval 0;
};
On the other hand, if your host brings up or tears down network interfaces more
often than every hour, you may want to reduce the interval.
[/QUOTE]
But when I tried it, named noticed right away that I had brought up an
interface. Will investigate further.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
NM-controlled dnsmasq prevents other DNS servers from starting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+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 1081495] Re: E: Sub-process /usr/bin/dpkg returned an error code (1)
On an openstack instance, tgt installs ok on ami-0176 but not on ami-0173 (https://launchpadlibrarian.net/124433581/terminal.log). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1081495 Title: E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1081495/+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 1081495] Re: E: Sub-process /usr/bin/dpkg returned an error code (1)
Err, http://paste.ubuntu.com/1412280/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1081495 Title: E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1081495/+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 1066834] Re: LevelForFileTypesDetection=0 produces unexpected results
This bug is beyond annoying as I documented at
https://sourceforge.net/p/awstats/discussion/43430/thread/d2d5b969/
Here is the text from the posts that I did there:
After I upgraded from 6.95 to 7.0, the top ten pages started listing
.png files, etc. I tried downgrading and the problem didn't go away. I
put debug statements in awstats.pl and $NotPageList{png} has the correct
value. Any hints of what type of debug statements I should add to figure
out this problem?
Eric Klien
It seems that setting LevelForFileTypesDetection to 2 (from 0) stops the
statistics from adding more .png hits to the top 10 page list although
the old .png hits are still listed. (The apache log files are purged by
awstats after processing them since my logs get pretty big.) This seems
to be related to the bug documented at
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1066834
I cleaned up the stuff between BEGIN_SIDER and END_SIDER in the relevant
.txt file and the problem seems to be solved. The fact that downgrading
didn't clean up the mistake in the .txt file threw me off for a while
when I tried to diagnose the problem.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to awstats in Ubuntu.
https://bugs.launchpad.net/bugs/1066834
Title:
LevelForFileTypesDetection=0 produces unexpected results
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1066834/+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 1086775] [NEW] bind9 uses high CPU after lucid->precise upgrade
Public bug reported: Summary: bind9 uses very high CPU after an upgrade from Lucid to Precise. I have traced this to a directory permissions problem as /var/cache/bind is not writeable by the bind group after an upgrade, but is writeable after a clean install. Ubuntu release: root@dev1-kvm-cluster:~# lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 Package version: root@dev1-kvm-cluster:~# apt-cache policy bind9 bind9: Installed: 1:9.8.1.dfsg.P1-4ubuntu0.4 Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.4 Version table: *** 1:9.8.1.dfsg.P1-4ubuntu0.4 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status 1:9.8.1.dfsg.P1-4 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Expected behaviour: Upgrading Lucid->Precise when bind9 is installed does not use >100% CPU Observed behaviour: Upgrading Lucid->Precise when bind9 is installed does not use >100% CPU Root cause: On an upgraded machine: root@dev1-kvm-cluster:~# ls -la /var/cache/bind total 8 drwxr-xr-x 2 root bind 4096 Jun 5 2012 . drwxr-xr-x 14 root root 4096 Dec 5 10:18 .. On a clean install of Precise: amb@adamant:~$ ls -la /var/cache/bind total 16 drwxrwxr-x 2 root bind 4096 Dec 4 21:00 . drwxr-xr-x 8 root root 4096 Dec 3 20:54 .. -rw-r--r-- 1 bind bind 698 Dec 4 21:00 managed-keys.bind -rw-r--r-- 1 bind bind 512 Dec 4 21:00 managed-keys.bind.jnl Workaround: # chmod 775 /var/cache/bind # service bind9 restart Logs from the upgraded machine (see 'working directory not writeable' and 'permission denied') 05-Dec-2012 12:23:35.719 found 2 CPUs, using 2 worker threads 05-Dec-2012 12:23:35.720 using up to 4096 sockets 05-Dec-2012 12:23:35.726 loading configuration from '/etc/bind/named.conf' 05-Dec-2012 12:23:35.727 reading built-in trusted keys from file '/etc/bind/bind.keys' 05-Dec-2012 12:23:35.727 using default UDP/IPv4 port range: [1024, 65535] 05-Dec-2012 12:23:35.728 using default UDP/IPv6 port range: [1024, 65535] 05-Dec-2012 12:23:35.729 listening on IPv6 interfaces, port 53 05-Dec-2012 12:23:35.731 listening on IPv4 interface lo, 127.0.0.1#53 05-Dec-2012 12:23:35.732 listening on IPv4 interface eth0, 10.40.0.5#53 05-Dec-2012 12:23:35.734 listening on IPv4 interface eth1, 10.157.128.1#53 05-Dec-2012 12:23:35.735 listening on IPv4 interface eth1, 10.161.208.1#53 05-Dec-2012 12:23:35.736 listening on IPv4 interface eth0.60, 10.157.16.12#53 05-Dec-2012 12:23:35.738 generating session key for dynamic DNS 05-Dec-2012 12:23:35.738 sizing zone task pool based on 7 zones 05-Dec-2012 12:23:35.744 using built-in root key for view _default 05-Dec-2012 12:23:35.744 set up managed keys zone for view _default, file 'managed-keys.bind' 05-Dec-2012 12:23:35.744 Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones 05-Dec-2012 12:23:35.744 automatic empty zone: 254.169.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 2.0.192.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 100.51.198.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 113.0.203.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: D.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 8.E.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 9.E.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: A.E.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: B.E.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA 05-Dec-2012 12:23:35.749 command channel listening on 127.0.0.1#953 05-Dec-2012 12:23:35.749 command channel listening on ::1#953 05-Dec-2012 12:23:35.749 the working directory is not writable 05-Dec-2012 12:23:35.749 ignoring config file logging statement due to -g option 05-Dec-2012 12:23:35.750 zone 0.in-addr.arpa/IN: loaded serial 1 05-Dec-2012 12:23:35.750 zone 157.10.in-addr.arpa/IN: loaded serial 1 05-Dec-2012 12:23:35.751 zone 127.in-addr.arpa/IN: loaded serial 1 05-Dec-2012 12:23:35.752 zone 255.in-addr.arpa/IN: loaded serial 1 05-Dec-2012 12:23:35.753 zone extility.install/IN: loaded serial 1300877104 05-Dec-2012 12:23:35.754 zone localhost/IN: loaded serial 2 05-Dec-2012 12:23:35.754 managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found 05-Dec-2012 12:23:35.754 managed-keys.bind.jnl: create: permission denied 05-Dec-2012 12:23:35.754 managed-keys-zone ./IN: sync_keyzone:dns_journal_open -> unexpected error ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- You
[Blueprint servercloud-r-xen] Xen work for R-series
Blueprint changed by Stefan Bader: Work items changed: Work items: [lars-kurth] sort contributions pie chart by percentage: TODO [dunlapg] Link to slides that were shown: DONE [ijc] Ian and Adam discuss grub2 booting Xen first: TODO [dunlapg] MaaS for installing Xen: TODO [stefan-bader-canonical] Upstream getty for PV console (hvc0): TODO [dunlapg] Get pvgrub working on Ubuntu: TODO [stefan-bader-canonical] Convert startup scripts to upstart (nice-to-have): TODO [dunlapg] 4.2 is target for Raring: DONE - [stefan-bader-canonical] Re-activate qemu-dm in Xen 4.2: INPROGRESS + [stefan-bader-canonical] Re-activate qemu-dm in Xen 4.2: DONE -- Xen work for R-series https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-xen -- 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 483928]
Oops, forgot to change the version. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/483928 Title: ssh-keyscan(1) exits prematurely on some non-fatal errors To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/483928/+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 483928]
I don't think anyone will fault you for having more momentous matters to attend to! As it is, I've gone without doing a network scan for that long anyway. Thanks for formally submitting the patch; hopefully this issue will be put to rest soon. Best of luck with the transition to a retired life, and may you continue to make contributions of value to our community :) (The old patch applied to 6.1p1 with fuzz, yet without rejections, only because it hadn't been updated in a while.) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/483928 Title: ssh-keyscan(1) exits prematurely on some non-fatal errors To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/483928/+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 483928]
Created attachment 2197 Besides comments, inludes patch for openssh-6.1p1 I knew I forgot to do something. I meant to CC you but obviously forgot. I apologize for the delay. I finally got around to submitting the patch last week via direct email to openssh-unix-...@mindrot.org. Again I apologize for this particular delay. I retired at the end of May (2012) after 38 years at Purdue University and the last six months there were a frenzy of "close down shop" activity. I still retain minimal access to some of the Purdue computers via what they call my "career account". This missive is being submitted from one of them. I was lucky enough to get a basic clone of my workstation to take home but I didn't get it up and running until about a month ago. Since then I've been learning a lot of new stuff since my main access is now a Windows box (I know, I know). The patch submission was the first major thing I did with it. A copy of the patch for openssh-6.1p1 is attached. Fuzzy??? Did I bug something up or is it because the patch you're using is somewhat dated? --Paul//aab -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/483928 Title: ssh-keyscan(1) exits prematurely on some non-fatal errors To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/483928/+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 483928]
And a year later, this issue still afflicts OpenSSH 6.1p1 (as packaged by Ubuntu). Aab's patch still applies, if fuzzily, and still hardens up ssh-keyscan so that it can deal with my company's network. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/483928 Title: ssh-keyscan(1) exits prematurely on some non-fatal errors To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/483928/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
** Description changed: Summary: bind9 uses very high CPU after an upgrade from Lucid to Precise. I have traced this to a directory permissions problem as /var/cache/bind is not writeable by the bind group after an upgrade, but is writeable after a clean install. Ubuntu release: root@dev1-kvm-cluster:~# lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 Package version: root@dev1-kvm-cluster:~# apt-cache policy bind9 bind9: - Installed: 1:9.8.1.dfsg.P1-4ubuntu0.4 - Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.4 - Version table: - *** 1:9.8.1.dfsg.P1-4ubuntu0.4 0 - 500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages - 100 /var/lib/dpkg/status - 1:9.8.1.dfsg.P1-4 0 - 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages + Installed: 1:9.8.1.dfsg.P1-4ubuntu0.4 + Candidate: 1:9.8.1.dfsg.P1-4ubuntu0.4 + Version table: + *** 1:9.8.1.dfsg.P1-4ubuntu0.4 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages + 100 /var/lib/dpkg/status + 1:9.8.1.dfsg.P1-4 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Expected behaviour: Upgrading Lucid->Precise when bind9 is installed does not use >100% CPU Observed behaviour: Upgrading Lucid->Precise when bind9 is installed - does not use >100% CPU + uses >100% CPU Root cause: On an upgraded machine: root@dev1-kvm-cluster:~# ls -la /var/cache/bind total 8 drwxr-xr-x 2 root bind 4096 Jun 5 2012 . drwxr-xr-x 14 root root 4096 Dec 5 10:18 .. On a clean install of Precise: amb@adamant:~$ ls -la /var/cache/bind total 16 drwxrwxr-x 2 root bind 4096 Dec 4 21:00 . drwxr-xr-x 8 root root 4096 Dec 3 20:54 .. -rw-r--r-- 1 bind bind 698 Dec 4 21:00 managed-keys.bind -rw-r--r-- 1 bind bind 512 Dec 4 21:00 managed-keys.bind.jnl Workaround: # chmod 775 /var/cache/bind # service bind9 restart Logs from the upgraded machine (see 'working directory not writeable' and 'permission denied') 05-Dec-2012 12:23:35.719 found 2 CPUs, using 2 worker threads 05-Dec-2012 12:23:35.720 using up to 4096 sockets 05-Dec-2012 12:23:35.726 loading configuration from '/etc/bind/named.conf' 05-Dec-2012 12:23:35.727 reading built-in trusted keys from file '/etc/bind/bind.keys' 05-Dec-2012 12:23:35.727 using default UDP/IPv4 port range: [1024, 65535] 05-Dec-2012 12:23:35.728 using default UDP/IPv6 port range: [1024, 65535] 05-Dec-2012 12:23:35.729 listening on IPv6 interfaces, port 53 05-Dec-2012 12:23:35.731 listening on IPv4 interface lo, 127.0.0.1#53 05-Dec-2012 12:23:35.732 listening on IPv4 interface eth0, 10.40.0.5#53 05-Dec-2012 12:23:35.734 listening on IPv4 interface eth1, 10.157.128.1#53 05-Dec-2012 12:23:35.735 listening on IPv4 interface eth1, 10.161.208.1#53 05-Dec-2012 12:23:35.736 listening on IPv4 interface eth0.60, 10.157.16.12#53 05-Dec-2012 12:23:35.738 generating session key for dynamic DNS 05-Dec-2012 12:23:35.738 sizing zone task pool based on 7 zones 05-Dec-2012 12:23:35.744 using built-in root key for view _default 05-Dec-2012 12:23:35.744 set up managed keys zone for view _default, file 'managed-keys.bind' 05-Dec-2012 12:23:35.744 Warning: 'empty-zones-enable/disable-empty-zone' not set: disabling RFC 1918 empty zones 05-Dec-2012 12:23:35.744 automatic empty zone: 254.169.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 2.0.192.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 100.51.198.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 113.0.203.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 255.255.255.255.IN-ADDR.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: D.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 8.E.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 9.E.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: A.E.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: B.E.F.IP6.ARPA 05-Dec-2012 12:23:35.744 automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA 05-Dec-2012 12:23:35.749 command channel listening on 127.0.0.1#953 05-Dec-2012 12:23:35.749 command channel listening on ::1#953 05-Dec-2012 12:23:35.749 the working directory is not writable 05-Dec-2012 12:23:35.749 ignoring config file logging statement due to -g option 05-Dec-2012 12:23:35.750 zone 0.in-addr.arpa/IN: loaded serial 1 05-Dec-2012 12:23:35.750 zone 157.10.in-addr.arpa/IN: loaded
[Bug 1066834] Re: LevelForFileTypesDetection=0 produces unexpected results
A solution to the problem is to change the following in awstats.pl:
if ($LevelForFileTypesDetection){
$datatoload{$filemime} = 1;
to:
# if ($LevelForFileTypesDetection)
{ $datatoload{$filemime} = 1;
This still won't handle the .cur extension. You could handle it by
adding it to MimeHashLib at lib/mime.pm or you could simply change (
$LevelForFileTypesDetection >= 2 || $MimeHashLib{$1} ) to (
$LevelForFileTypesDetection >= 0 || $MimeHashLib{$1} )
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to awstats in Ubuntu.
https://bugs.launchpad.net/bugs/1066834
Title:
LevelForFileTypesDetection=0 produces unexpected results
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1066834/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
Thank you for taking the time to report this bug and helping to make Ubuntu better. I've not been able to reproduce this when upgrading from Lucid to Precise (1:9.7.0.dfsg.P1-1ubuntu0.8 to 1:9.8.1.dfsg.P1-4ubuntu0.4). /var/cache/bind had the correct (775) permissions. If I remove its contents and change the permissions to 755, then I do see the 100% CPU usage and the error in the log file that you've reported. But what I don't see is how to get the permissions to the erroneous 755 in the first place - simply installing bind9 in Lucid and upgrading to Precise doesn't seem to do it. Are you sure that the permissions weren't already wrong due to a local misconfiguration before you upgraded? Marking as Incomplete for now. If you manage to figure out how to reproduce this problem, please comment and change the bug status back to New. ** Changed in: bind9 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 1086833] [NEW] All nova upstart configuration use 'su' instead of 'start-stop-daemon'
Public bug reported: The way the nova upstart configurations chuid/chgid is by using su; using start-stop-daemon is a much cleaner way and avoids creating user sessions on the installed system. See quantum for reference. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: nova-compute (not installed) ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Wed Dec 5 15:08:12 2012 MarkForUpload: True SourcePackage: nova UpgradeStatus: Upgraded to quantal on 2012-12-04 (0 days ago) ** Affects: nova (Ubuntu) Importance: Undecided Assignee: Yolanda Robla (yolanda.robla) Status: New ** Affects: nova (Ubuntu Raring) Importance: Undecided Assignee: Yolanda Robla (yolanda.robla) Status: New ** Tags: amd64 apport-bug quantal running-unity ** Also affects: nova (Ubuntu Raring) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1086833 Title: All nova upstart configuration use 'su' instead of 'start-stop-daemon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1086833/+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 1086833] Re: All nova upstart configuration use 'su' instead of 'start-stop-daemon'
** Changed in: nova (Ubuntu Raring) Assignee: (unassigned) => Yolanda Robla (yolanda.robla) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1086833 Title: All nova upstart configuration use 'su' instead of 'start-stop-daemon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1086833/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
The server concerns was automatically installed from a CD-ROM built from Ubuntu sources and (in respect of bind) it has only had automatic updates run on it. I am very confident it was not operator error. It was upgraded with 'do-release-upgrade'. I can tell you I am not the only person experiencing this. See for instance: http://ubuntuforums.org/showthread.php?t=1971471 https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1038199 (same root cause I'm guessing) I would have thought that given >1 people are seeing this, a chmod in the postinst file would do no harm. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 1086833] Re: All nova upstart configuration use 'su' instead of 'start-stop-daemon'
** Changed in: nova (Ubuntu Raring) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1086833 Title: All nova upstart configuration use 'su' instead of 'start-stop-daemon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1086833/+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 1066834] Re: LevelForFileTypesDetection=0 produces unexpected results
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: awstats (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1066834 Title: LevelForFileTypesDetection=0 produces unexpected results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1066834/+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 1086466] Re: asterisk 1.8 ringall strategy in queues causes non-answering agents to exit out of Dial() even with 'g' option
Sounds like a bug to me. Some thoughts for workarounds. Could
${EXTENSION_STATE(...)}) (when using hints) or ${SIPPEER(...,curcalls)}
(if using SIP and call-limit) help you here? 1.6 brought in lots of new
shiny stuff like this which eliminated the need for various similar
hacks I had to use in previous versions.
** Changed in: asterisk (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1086466
Title:
asterisk 1.8 ringall strategy in queues causes non-answering agents to
exit out of Dial() even with 'g' option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1086466/+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 994887] Re: Nodes listing does not support sorting
** Changed in: maas (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/994887 Title: Nodes listing does not support sorting To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994887/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
With as many users as we have, a common misconfiguration can lead to a number of reports. I'd have expected dozens of reports or more by now if this were a systemic upgrade problem. Also note that one of the reports you linked to has root group ownership too, which is inconsistent with a single root cause. I've looked at the ways the bind9 maintainer scripts call chmod, and don't see how a group write permission could get lost: $ grep chmod /var/lib/dpkg/info/*bind* /var/lib/dpkg/info/bind9.postinst: chmod 775 /var/lib/bind /var/lib/dpkg/info/bind9.postinst: chmod g+s /etc/bind /var/lib/dpkg/info/bind9.postinst: chmod g+r /etc/bind/rndc.key /etc/bind/named.conf* || true /var/lib/dpkg/info/bind9.postinst: chmod g+rwx /var/run/named /var/cache/bind I've checked the maintainer scripts this way across Hardy, Lucid and Precise. It looks to me that the existing postinst intentionally avoids doing the chmod except in a particular circumstance which I presume is for upgrading from a specific previous version (presumably prior to Hardy). I'd like to understand the root cause before I'm comfortable pushing to change this, and there is a trivial workaround for those affected. So steps to reproduce the problem would really help! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 1065883] Re: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder
** Changed in: cinder Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065883 Title: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065883/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
Well I'm pretty sure the problem is this. I've just gone to another (unconnected) Lucid box, and: root@extility-developers:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 10.04.4 LTS Release:10.04 Codename: lucid root@extility-developers:~# ls -ln /etc/bind/rndc.key -rw-r- 1 103 108 77 2012-06-14 14:23 /etc/bind/rndc.key See rndc.key is owned by UID 103, which is not equal to 0. So the Precise postinst script does not do the chmod. You may not have received reports because bind actually works, just uses high CPU. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 1086833] Re: All nova upstart configuration use 'su' instead of 'start-stop-daemon'
** Branch linked: lp:~yolanda.robla/nova/grizzly-upstart -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1086833 Title: All nova upstart configuration use 'su' instead of 'start-stop-daemon' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1086833/+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
Re: [Bug 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
On Wed, Dec 05, 2012 at 05:48:18PM -, Alex Bligh wrote: > See rndc.key is owned by UID 103, which is not equal to 0. So the > Precise postinst script does not do the chmod. This is what I would expect, because the permissions on /var/cache/bind should already be correct, and maintainer scripts generally try not to interfere with anything the administrator might have done. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 495418] Re: Enable GSSAPI support (for likewise-open)
This should be backed out. Use cyrus-sasl for SASL/GSSAPI binds with OpenLDAP. It would be nice if folks would actually clear stuff with upstream instead of cluelessly hacking on the OpenLDAP source. There have been enough issues caused by this already with the debian and ubuntu folks over the years. At least the Debian developers finally got things cleaned up and work with upstream now. It'd be nice to see ubuntu do the same. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/495418 Title: Enable GSSAPI support (for likewise-open) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/495418/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
OK so my working hypothesis is this. On Lucid /var/cache/bind is created simply by virtue of it being a directory within the package (see the bind9.list file). The group write permission is added by the postinst. If the Lucid package was installed, then removed, then installed again, the following happens: 1. the first install would create /var/cache/bind with whatever ownership is in the package, and also /etc/bind/rndc.key with root ownership. The postinst thens runs and fixes the group write permission on /var/cache/bind. 2. the removal would delete /var/cache/bind as it is not a conffile, but not /etc/bind/rndc.key 3. the second install would create /var/cache/bind again with (possibly) the wrong permissions, and the postinst script would not fix it. This probably doesn't go wrong in Lucid because nothing writes to the cache directory and/or bind survives without the cache. It's certainly empty here on our Lucid boxes pre upgrade to Precise. But the Precise upgrade requires to write there, and then dies. The above would happen (AFAICT) if *ANY* version ever released of the Lucid bind9.deb had broken permissions, as subsequent upgrades would not fix it. The problem with only fixing permissions if some rather random file in /etc/ is owned by root is it is inherently fragile. Is there any reason why the bind cache directory should ever not be writeable by the group that owns it? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 1082050] Re: man pages installed with keystone are outdated
** Branch linked: lp:~gandelman-a/keystone/manpage-fix -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1082050 Title: man pages installed with keystone are outdated To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1082050/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
To follow this up, the .deb at least on Lucid does NOT have the write permission set. amb@nimrod-ubuntu:~/bind-test$ dpkg -c bind9_9.7.0.dfsg.P1-1ubuntu0.8_amd64.deb | fgrep cache drwxr-xr-x root/root 0 2012-10-09 14:13 ./var/cache/ drwxr-xr-x root/root 0 2012-10-09 14:13 ./var/cache/bind/ I've tried this on a pristine Precise box and it doesn't go wrong because Precise does not remove /var/cache/bind as it is populated (unlike on at least some Lucid installs). However, if I manually remove the cache directory, it does go wrong: root@adamant:~# dpkg --list bind9 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii bind9 1:9.8.1.dfsg.P Internet Domain Name Server root@adamant:~# ls -lnd /var/cache/bind /etc/bind/rndc.key -rw-r- 1 103 108 77 Dec 3 20:56 /etc/bind/rndc.key drwxrwxr-x 2 0 108 4096 Dec 4 21:00 /var/cache/bind root@adamant:~# aptitude remove bind9 The following packages will be REMOVED: bind9 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 963 kB will be freed. (Reading database ... 47095 files and directories currently installed.) Removing bind9 ... * Stopping domain name service... bind9 waiting for pid 859 to die ...done. Processing triggers for ufw ... Processing triggers for ureadahead ... ureadahead will be reprofiled on next reboot Processing triggers for man-db ... root@adamant:~# ls -lnd /var/cache/bind /etc/bind/rndc.key -rw-r- 1 103 108 77 Dec 3 20:56 /etc/bind/rndc.key drwxrwxr-x 2 0 108 4096 Dec 5 19:13 /var/cache/bind root@adamant:~# ls -la /var/cache/bind total 16 drwxrwxr-x 2 root bind 4096 Dec 5 19:13 . drwxr-xr-x 8 root root 4096 Dec 3 20:54 .. -rw-r--r-- 1 bind bind 698 Dec 4 21:00 managed-keys.bind -rw-r--r-- 1 bind bind 512 Dec 4 21:00 managed-keys.bind.jnl root@adamant:~# rm -rf /var/cache/bind root@adamant:~# aptitude install bind9 The following NEW packages will be installed: bind9 0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 343 kB of archives. After unpacking 963 kB will be used. Get: 1 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main bind9 amd64 1:9.8.1.dfsg.P1-4ubuntu0.4 [343 kB] Fetched 343 kB in 0s (621 kB/s) Preconfiguring packages ... Selecting previously unselected package bind9. (Reading database ... 47062 files and directories currently installed.) Unpacking bind9 (from .../bind9_1%3a9.8.1.dfsg.P1-4ubuntu0.4_amd64.deb) ... Processing triggers for man-db ... Processing triggers for ureadahead ... Processing triggers for ufw ... Setting up bind9 (1:9.8.1.dfsg.P1-4ubuntu0.4) ... * Starting domain name service... bind9 ...done. root@adamant:~# ls -lnd /var/cache/bind /etc/bind/rndc.key -rw-r- 1 103 108 77 Dec 3 20:56 /etc/bind/rndc.key drwxr-xr-x 2 0 0 4096 Oct 9 14:06 /var/cache/bind -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 1086646] Re: text/x-shellscript doesn't run if text/cloud-boothook present
Hi, Thanks for taking the time to open a bug and help in making Ubuntu better. I'm not able to recreate the issue you're seeing. Working off the doc at https://help.ubuntu.com/community/CloudInit . I've attached the user-data that was created by write-mime-multipart, but here is what I did to try to reproduce: # ami-9c78c0f5 = us-east-1 ubuntu-precise-12.04-amd64-server-20121026.1 $ cat my-boothook #!/bin/sh echo "=== $(date): running $0 $* ===" | tee -a /root/boothook.log echo myhostname > /etc/hostname $ cat my-userscript #!/bin/sh echo "=== $(date): running $0 $* ===" | tee -a /root/userscript.log $ write-mime-multipart --output=userdata.txt \ my-boothook:text/cloud-boothook my-userscript:text/x-shellscript $ euca-run-instances --key=brickies --instance-type=t1.micro \ --user-data-file=userdata.txt ami-9c78c0f5 Then, inside the instance I did: $ sudo sh -c 'for f in /root/*.log; do echo "#$f"; cat $f; done' #/root/boothook.log === Wed Dec 5 19:09:36 UTC 2012: running /var/lib/cloud/instances/i-06d52c78/boothooks/my-boothook === #/root/userscript.log === Wed Dec 5 19:09:49 UTC 2012: running /var/lib/cloud/instance/scripts/my-userscript === That shows that the scripts ran 13 seconds apart (one early in boot and one later). And by their names, its clear that one ran as a boothook and one as a user-script. ** Attachment added: "user-data created with write-mime-multipart" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1086646/+attachment/3452431/+files/userdata.txt ** Changed in: cloud-init (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1086646 Title: text/x-shellscript doesn't run if text/cloud-boothook present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1086646/+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 1086646] Re: text/x-shellscript doesn't run if text/cloud-boothook present
Could you give me an example that fails? Also, just fyi, a.) you dont have to change /etc/cloud/cloud.cfg's value of preserve_hostname. cloud-config input setting that will do the same thing as you were attempting. b.) you can set the hostname by cloud-config input with 'hostname'. #cloud-config hostname: myhostname.my.fully.qualified.domain.com -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1086646 Title: text/x-shellscript doesn't run if text/cloud-boothook present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1086646/+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 1086959] [NEW] squid crashed with SIGSEGV
Public bug reported: because of low disk space?? ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: squid 2.7.STABLE9-4ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-28.45-generic 3.0.51 Uname: Linux 3.0.0-28-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Wed Dec 5 10:00:32 2012 Disassembly: => 0x54f4e9: Cannot access memory at address 0x54f4e9 ExecutablePath: /usr/sbin/squid InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcCmdline: /usr/sbin/squid -N -D ProcEnviron: PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x54f4e9:Cannot access memory at address 0x54f4e9 PC (0x0054f4e9) ok Stack memory exhausted (SP below stack segment) SP (0xbf31bf4c) not located in a known VMA region (needed readable region)! SegvReason: reading unknown VMA Signal: 11 SourcePackage: squid Stacktrace: #0 0x0054f4e9 in ?? () No symbol table info available. Cannot access memory at address 0xbf31bf4c StacktraceTop: ?? () ThreadStacktrace: . Thread 1 (LWP 25546): #0 0x0054f4e9 in ?? () No symbol table info available. Cannot access memory at address 0xbf31bf4c Title: squid crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: winbindd_priv ** Affects: squid (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace oneiric ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1086959 Title: squid crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1086959/+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 1082050] Re: man pages installed with keystone are outdated
** Branch linked: lp:~openstack-ubuntu-testing/keystone/grizzly -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1082050 Title: man pages installed with keystone are outdated To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1082050/+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 1086959]
Stacktrace: #0 0x0054f4e9 in ?? () No symbol table info available. Cannot access memory at address 0xbf31bf4c StacktraceSource: #0 0x0054f4e9 in ?? () StacktraceTop: ?? () ThreadStacktrace: . Thread 1 (LWP 25546): #0 0x0054f4e9 in ?? () No symbol table info available. Cannot access memory at address 0xbf31bf4c ** Changed in: squid (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1086959 Title: squid crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1086959/+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 1086959] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: outdated debug symbol package for ncurses-bin: package version 5.9-1ubuntu5.1 dbgsym version 5.9-1ubuntu5 libdrm-intel1 version 2.4.33+git20120403.43704256-0ubuntu0ricotz~oneiric required, but 2.4.26-1ubuntu1 is available outdated debug symbol package for libdbus-1-3: package version 1.4.14-1ubuntu1.3 dbgsym version 1.4.14-1ubuntu1 libpciaccess0 version 0.13-1~oneiric1 required, but 0.12.1-2 is available libffi6 version 3.0.11~rc1-5~oneiric1 required, but 3.0.11~rc1-2 is available libdrm-radeon1 version 2.4.33+git20120403.43704256-0ubuntu0ricotz~oneiric required, but 2.4.26-1ubuntu1 is available libdrm-nouveau1a version 2.4.33+git20120403.43704256-0ubuntu0ricotz~oneiric required, but 2.4.26-1ubuntu1 is available libdrm2 version 2.4.33+git20120403.43704256-0ubuntu0ricotz~oneiric required, but 2.4.26-1ubuntu1 is available Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1086959/+attachment/3452432/+files/CoreDump.gz ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/1086959 Title: squid crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1086959/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
Thanks for your insight Alex. I've managed to reproduce this now, with the following steps: On Lucid: 1. sudo apt-get install bind9 2. sudo apt-get remove bind9 # this removes /var/cache/bind but leaves /etc/bind9/rndc.key 3. sudo apt-get install bind9 # Now the postinst doesn't fix /var/cache/bind, but on Lucid nobody will notice this problem 4. sudo do-release-upgrade # bind now uses /var/cache/bind/managed-keys.bind and the problem occurs After the upgrade to Precise, bind9 is in the situation you described (permissions on /var/cache/bind wrong), with 100% CPU consumption. I couldn't reproduce the problem directly on Precise because on package removal /var/cache/bind/managed-keys.bind is left behind and so /var/cache/bind never gets removed (I think this is a separate bug in itself). It seems likely to me that this issue will affect Debian also, so next I will test this and file a bug report in Debian as needed, so that we can coordinate a fix. ** Changed in: bind9 (Ubuntu) Status: Incomplete => Triaged ** Changed in: bind9 (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 1086775] Re: bind9 uses high CPU after lucid->precise upgrade
Robie, No problem - I'm just glad I wasn't imagining it. I agree the 100% CPU problem can't be reproduced on precise. To be honest I don't quite understand why /var/cache/bind isn't in /var/run (given it's a cache) but I may be wrong about that. Alex -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/1086775 Title: bind9 uses high CPU after lucid->precise upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1086775/+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 943502] Re: whois doesn't properly query .hr/.sx/.pe TLDs and incorrect format for whois.arin.net
Ok instead of going the Ubuntu backports route, I just created a patch that enabled these feature in Oneiric. I've linked a branch with these changes. I've also built/tested on my end and it does in fact pass the test case. ** Description changed: - Summary (one line): - Please backport whois 5.0.19 (main) from quantal - - Description: - Please backport whois 5.0.19 (main) from quantal to precise. - - Reason for the backport: - - This backport is needed in order to provide a backport to Oneiric. - - Testing: - - Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing. - - You can test-build the backport in your PPA with backportpackage: - $ backportpackage -u ppa:/ -s quantal -d precise whois - - * precise: - [X] Package builds without modification - [X] whois installs cleanly and runs - - Reverse dependencies: - = - The following reverse-dependencies need to be tested against the new version of whois. For reverse-build-dependencies (-Indep), please test that the package still builds against the new whois. For reverse-dependencies, please test that the version of the package currently in the release still works with the new whois installed. Reverse- Recommends, Suggests, and Enhances don't need to be tested, and are listed for completeness-sake. - - whois - - - * xbmc-live - [ ] precise (Reverse-Depends) * Could not install due to pad.lv/990183 - * bdii - [ ] precise (Reverse-Depends) - * dancer-ircd - [ ] precise (Reverse-Recommends) - * subnetcalc - [ ] precise (Reverse-Recommends) - * greenwich - [X] precise (Reverse-Depends) - * ircd-hybrid - [ ] precise (Reverse-Recommends) - * gnome-nettool - [X] precise (Reverse-Depends) - * fail2ban - [ ] precise (Reverse-Recommends) - * bsdmainutils - [ ] precise (Reverse-Suggests) - * psad - [X] precise (Reverse-Depends) - * bastille - [ ] precise (Reverse-Recommends) - * nagios-plugins-standard - [ ] precise (Reverse-Recommends) - ~ - - -- - - Please backport whois 5.0.19 (main) from quantal - - Description: - Please backport whois 5.0.19 (main) from quantal to oneiric. - - Reason for the backport: - - This provides some needed updates to users who need to query .hr/.sx/.pe TLDs, and fixes an incorrect format for whois.arin.net, plus some additional updates. - - Testing: - - Mark off items in the checklist [X] as you test them, but please leave the checklist so that backporters can quickly evaluate the state of testing. - - You can test-build the backport in your PPA with backportpackage: - $ backportpackage -u ppa:/ -s quantal -d oneiric whois - - * oneiric: - [X] Package builds without modification - [X] whois installs cleanly and runs - - Reverse dependencies: - = - The following reverse-dependencies need to be tested against the new version of whois. For reverse-build-dependencies (-Indep), please test that the package still builds against the new whois. For reverse-dependencies, please test that the version of the package currently in the release still works with the new whois installed. Reverse- Recommends, Suggests, and Enhances don't need to be tested, and are listed for completeness-sake. - - whois - - - * bdii - [ ] oneiric (Reverse-Depends) Can't do this because of http://pad.lv/1045295 - * dancer-ircd - [ ] oneiric (Reverse-Recommends) - * subnetcalc - [ ] oneiric (Reverse-Recommends) - * greenwich - [X] oneiric (Reverse-Depends) - * ircd-hybrid - [ ] oneiric (Reverse-Recommends) - * gnome-nettool - [X] oneiric (Reverse-Depends) - * fail2ban - [ ] oneiric (Reverse-Recommends) - * bsdmainutils - [ ] oneiric (Reverse-Suggests) - * psad - [X] oneiric (Reverse-Depends) - * bastille - [ ] oneiric (Reverse-Recommends) - * nagios-plugins-standard - [ ] oneiric (Reverse-Recommends) - - -- [Impact] Fixes issues using whois with .hr/.sx/.pe TLDs. In addition updates query format for IPs when accessing ARIN. [Development Fix] These issues were fixed in 5.0.14 of whois. [Stable Fix] Since most of the fixes are covered in updating from 5.0.11 to 5.0.14, a backport of these version provides all fixes. [Test Case] 1) whois google.hr (works on precise, not on oneiric) 2) whois registry.sx google.com.pe 3) whois 74.125.113.102 if we use this command in precise we see that whois adds "n +" to the query, while in oneiric it doesn't add that. [Regression Potential] Most of the changes are fairly minimal, although any changes to mkpasswd should be investigated. Problem Description: whois in oneiric can't query .hr/.sx/.pe TLDs. In addition the query format for ARIN is different than in precise. Version affected: Current Oneiric Version: 5.0.11ubuntu2 ** Changed in: whois (Ubuntu
[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting
In response to #131 and #134 by Thomas: I would argue that "will it conflict with anything that exists?" is the wrong question, here. Certainly it will conflict in the future, and removing the users ability to run a DNS service on the wildcard address is suboptimal at best, even if they don't *need* to. To directly answer the question about something that conflicts: the internal resolver of the samba4 packages. They're beta right now, but the scheduled release date is December, and there's no parameter (yet) for altering the port or interfaces. This is actually the one that bit me originally. To answer "what does it give us?", currently NM invokes a single dnsmasq instance that must be shared between all users. This isn't ideal, because NM connections can be per-user, and this could lead information disclosure at worst and oddly-rearranged DNS resolve orders at best. With an NSS module, you could spin up one dnsmasq instance for the system on a possibly priviliged port (but not 53) and one per user (above 1024), and link them together as forwarders so that only the user owning the connection will use the resolution they've specified in the GUI. It would require som tracking of which user's instance is on which port,and auto-invoking them when necessary, and shutting it down when the user logs out, but would allow for much more flexible and clean separation of user settings. For the record, I am happy to write the NSS plugin myself, but it would require some changes in NM core itself, so I would have to work with someone on the NM team to implement it. If you're interested, and know who that would be, please do let me know. I will also create a new bug report as requested. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/959037 Title: NM-controlled dnsmasq prevents other DNS servers from starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+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 943502] Re: whois doesn't properly query .hr/.sx/.pe TLDs and incorrect format for whois.arin.net
You can't enable features in an SRU. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to whois in Ubuntu. https://bugs.launchpad.net/bugs/943502 Title: whois doesn't properly query .hr/.sx/.pe TLDs and incorrect format for whois.arin.net To manage notifications about this bug go to: https://bugs.launchpad.net/oneiric-backports/+bug/943502/+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 901180] Re: cannot apt-get remove vsftp after installing it
Edit the file /var/lib/dpkg/info/vsftp.postrm and comment out the lines which remove the user 'ftp' and group 'ftp'. Edit them as sudo, like this: sudo nano /var/lib/dpkg/info/vsftpd.postrm The run apt-get (or your favorite uninstaller) to remove vsftpd: sudo apt-get remove vsftpd -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/901180 Title: cannot apt-get remove vsftp after installing it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/901180/+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 1061665] Re: Filter scheduler not respecting the force_hosts hint
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1061665 Title: Filter scheduler not respecting the force_hosts hint To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-manuals/+bug/1061665/+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
