and, `strace ./rjsuuplicant -n eth0 -u USER -p PASS -d 1 -s internet` is
attached as strace_native.log
** Attachment added: strace_native.log
https://bugs.launchpad.net/qemu/+bug/1246990/+attachment/3897370/+files/strace_native.log
** Also affects: qemu (Ubuntu)
Importance: Undecided
Public bug reported:
When an error occurs from mod_python on Saucy (which uses Apache 2.4)
there is nothing logged. I have tracked this issue down to the value of
APLOG_NOERRNO being incorrect. This value is defined to be
(APLOG_LEVELMASK + 1); on Apache 2.2, APLOG_LEVELMASK was 7, but on
Apache
This is still affecting users of the 1.4+bzr1693+dfsg-0ubuntu2 pacakge
in Saucy.
Steps to reproduce:
- Install maas using the saucy server install CD.
- Edit /etc/maas/import_pxe_files - set ARCHES to i.e. ARCHES=amd64/generic
- Configure the rest of MaaS, click the import boot images in the UI
Further information:
Relevant stacktrace: https://pastebin.canonical.com/99705/
--
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/1240215
Title:
changing the default arches in
@tribaal: I think what you're seeing here is bug 1181334 (note the fact
that the error you see mentions i386).
Can you try changing /etc/maas/import_pxe_files to set ARCHES to
i386/generic amd64/generic, re-run the import script and try again?
--
You received this bug notification because you
Sorry, I used a private pastebin, here's the public equivalent:
http://pastebin.ubuntu.com/6340916/
@rvb: Yeah that looks like what I'm seeing indeed. I'll give it a try
and report back!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The attachment patch to fix this issue against 3.3.1 seems to be a
patch. If it isn't, please remove the patch flag from the attachment,
remove the patch tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user
I'v copied your testcase with copy and paste to
/etc/puppet/manifests/test.pp and run:
# puppet apply /etc/puppet/manifests/test.pp
Could not retrieve zpool_version: undefined method `captures' for nil:NilClass
Warning: Could not retrieve fact fqdn
Error: Puppet::Parser::AST::Resource failed with
And, btw., ruby-hiera was installed on the first, but not on the second
machine. Both behave identically.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1246229
Title:
Error:
Public bug reported:
Looks like a runaway irqbalance process is consuming massive amount of
Memory and CPU. This is running on a calxeda arm server used as a build
server. Was unable to find any mention of irqbalance in /var/logs.
Hopefully apport recorded the right data.
PID USER PR NI
@rvb: Yes, adding back the i386 architecture made the boot up work. I'll
subscribe to bug 1181334 instead! Thanks for your help.
--
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/1240215
Can confirm, it would save us (the landscape team, but also other users
I wager) a lot of time and disk space if we could only download amd64
images and use that successfully.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
** Tags added: landscape
--
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/1181334
Title:
i386 required to install amd64
To manage notifications about this bug go to:
This was fixed by smoser and pushed to trunk.
Here is a diff if you're interested: https://pastebin.canonical.com/99718/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1159818
Title:
Public bug reported:
OS: Ubuntu 12.04,
Bind package:
ii bind91:9.8.1.dfsg.P1-4ubuntu0.7
Internet Domain Name Server
Bind folder:
drwxr-s--- 3 bind bind 4096 Nov 1 20:46 /etc/bind
* Steps to reproduce the issue
rndc -s localhost
Ah, my bad, Stephane. I tested Ubuntu 13.10 saucy.
** Tags added: verification-done-saucy
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242913
Title:
/dev/pts being created with
ubuntu@ip-10-164-72-103:~$ cat /etc/issue
Ubuntu 13.04 \n \l
ubuntu@ip-10-164-72-103:~$ dpkg -l | grep lxc
ii liblxc00.9.0-0ubuntu3.7
amd64Linux Containers userspace tools (library)
ii lxc0.9.0-0ubuntu3.7
ubuntu@ip-10-185-176-79:~$ cat /etc/issue
Ubuntu 12.10 \n \l
ubuntu@ip-10-185-176-79:~$ dpkg -l | grep lxc
ii liblxc00.8.0~rc1-4ubuntu39.12.10.5
amd64Linux Containers userspace tools (library)
ii lxc
Strike Comment #19. Precise is good too.
** Tags added: verification-done-precise
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242913
Title:
Hang on, wrong paste there for precise...
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1242913
Title:
/dev/pts being created with mode=600 by Lxc
To manage notifications about this
ubuntu@ip-10-166-49-90:~$ cat /etc/issue
Ubuntu 12.04.3 LTS \n \l
ubuntu@ip-10-166-49-90:~$ dpkg -l | grep lxc
ii lxc 0.7.5-3ubuntu69 Linux
containers userspace tools
ii lxc-docker 0.6.5
A temporary workaround is to create a symbolic link in the /etc/apache2
/conf-enabled directory to the existing configuration file in
/etc/apache2/conf.d directory:
sudo ln -s /etc/apache2/conf.d/backuppc.conf /etc/apache2/conf-
enabled/backuppc.conf
restarting the apache2 webserver should
same problem with package openssh-server of Ubuntu 13.10 (Saucy)
error messages in /var/log/auth.log after boot process:
Nov 1 17:31:46 pc sshd[1209]: error: Bind to port xxx on yyy.yyy.y.y failed:
Cannot assign requested address.
Nov 1 17:31:46 pc sshd[1209]: fatal: Cannot bind any address.
Public bug reported:
error: Invalid argument setting key net.ipv4.tcp_mem
found in /etc/sysctl.d/30-iscsitarget.conf
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: iscsitarget (not installed)
ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
Uname: Linux 3.2.0-34-generic x86_64
Workaround did not work for me on a freshly installed system. Getting
the following error on restart of apache2:
* Restarting web server apache2
...fail!
* The apache2 configtest failed.
Output of config test was:
apache2: Syntax error on line 216 of /etc/apache2/apache2.conf: Could not open
Instead this workaround worked (like MDill described in the original Bug
Description):
ln -s /etc/backuppc/apache.conf /etc/apache2/conf-enabled/backuppc.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to backuppc in Ubuntu.
** Changed in: byobu (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1243017
Title:
upstart commands break inside byobu-tmux after a session
Committed revision 2230.
** Changed in: byobu (Ubuntu)
Status: New = In Progress
** Changed in: byobu (Ubuntu)
Importance: Undecided = Low
** Changed in: byobu (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: byobu (Ubuntu)
Status: In
Committed revision 2231.
** Changed in: byobu (Ubuntu)
Status: New = In Progress
** Changed in: byobu (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: byobu (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification
** Branch linked: lp:byobu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1243017
Title:
upstart commands break inside byobu-tmux after a session restart
To manage notifications
** Branch linked: lp:byobu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1244509
Title:
.screenrc bindings overrides .byobu/keybindings
To manage notifications about this bug go
Committed revision 2232.
** Changed in: byobu (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1237071
Title:
Incompatible with
** Branch linked: lp:ubuntu/precise-proposed/cloud-init
--
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/1231490
Title:
[SRU] cloud-init should handle formating the azure disks
** Branch linked: lp:byobu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to byobu in Ubuntu.
https://bugs.launchpad.net/bugs/1237071
Title:
Incompatible with virtualenv
To manage notifications about this bug go to:
Any news on this? Why is it marked as invalid?
** Changed in: vm-builder (Ubuntu)
Status: Invalid = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/1245486
This bug was fixed in the package byobu - 5.62-0ubuntu1
---
byobu (5.62-0ubuntu1) trusty; urgency=low
* usr/share/byobu/keybindings/f-keys.tmux:
- as it turns out, showing the current window name when renaming
is really annoying
* usr/bin/byobu-janitor,
This bug was fixed in the package byobu - 5.62-0ubuntu1
---
byobu (5.62-0ubuntu1) trusty; urgency=low
* usr/share/byobu/keybindings/f-keys.tmux:
- as it turns out, showing the current window name when renaming
is really annoying
* usr/bin/byobu-janitor,
This bug was fixed in the package byobu - 5.62-0ubuntu1
---
byobu (5.62-0ubuntu1) trusty; urgency=low
* usr/share/byobu/keybindings/f-keys.tmux:
- as it turns out, showing the current window name when renaming
is really annoying
* usr/bin/byobu-janitor,
This bug was fixed in the package byobu - 5.62-0ubuntu1
---
byobu (5.62-0ubuntu1) trusty; urgency=low
* usr/share/byobu/keybindings/f-keys.tmux:
- as it turns out, showing the current window name when renaming
is really annoying
* usr/bin/byobu-janitor,
You have been subscribed to a public bug:
[Impact]: The cloud-init version Precise uses the wrong is_true test
from util instead of futil for the SmartOS datasource. If a user sends
over a user-script or user-data, the instance will be unaccessable due
to a stack trace. This means that user-data
** Package changed: ubuntu = cloud-init (Ubuntu)
--
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/1247262
Title:
[SRU] datasource for smartos uses util.is_true instead of
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
--
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/1247262
Title:
[SRU] datasource for
** Description changed:
[Impact]: The cloud-init version Precise uses the wrong is_true test
from util instead of futil for the SmartOS datasource. If a user sends
over a user-script or user-data, the instance will be unaccessable due
to a stack trace. This means that user-data or
Hello Ben, or anyone else affected,
Accepted cloud-init into precise-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/cloud-
init/0.6.3-0ubuntu1.9 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
44 matches
Mail list logo
