** 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
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 recei
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.n
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 *ne
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.
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 beca
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/cach
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 sym
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 memor
** 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 man
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
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
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-conf
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/ca
** 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 notif
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
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
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
** 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-da
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:
** 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
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 roo
** 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 notificat
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 pre
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/10
** 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
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 experienc
** 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 configur
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 ins
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
A solution to the problem is to change the following in awstats.pl:
if ($LevelForFileTypesDetection){
$datatoload{$filemime} = 1;
to:
# if ($LevelForFileTypesDetection)
{ $datatoload{$filemi
** 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:
roo
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
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 apologiz
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,
an
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 a
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
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-cluste
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
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 abou
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/10
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
42 matches
Mail list logo
