[Bug 1078242] Re: juju cannot connect to zookeeper - too many connections (max 10)
Sure, the cluster is still up at canonistack if you want to poke at them: I've used two charms: jenkins x1 and jenkins-slave x2, vanilla on precise. My envirionments.yaml looks like this: environments: canonistack: type: ec2 ec2-uri: http://91.189.93.65:8773/services/Cloud s3-uri: http://91.189.93.65: access-key: secret-key: default-image-id: ami-00bf #64-bit precise, or see euca-describe-images and pick one. default-series: precise control-bucket: admin-secret: authorized-keys-path: ~/.ssh/authorized_keys ** Changed in: juju (Ubuntu) Status: Incomplete => New ** Changed in: juju (Ubuntu) Assignee: (unassigned) => Serge Hallyn (serge-hallyn) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078242 Title: juju cannot connect to zookeeper - too many connections (max 10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078242/+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 1078242] [NEW] juju cannot connect to zookeeper - too many connections (max 10)
Public bug reported: My juju cluster running on precise had severe connection issues to zookeeper. Looking at zookeeper logs I can see that my juju nodes cannot connect as they already have pending connections. Zookeeper log is full of lines like (quick count gives me around 30,000) 2012-11-08 06:46:48,777 - WARN [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:NIOServerCnxn$Factory@247] - Too many connections from /10.55.60.51 - max is 10 There are also session expiration messages (around 1000) 2012-11-08 06:46:58,000 - INFO [SessionTracker:ZooKeeperServer@316] - Expiring session 0x13ad043e9460400, timeout of 1ms exceeded And exceptions (about 4000) 2012-11-08 06:47:05,663 - ERROR [SyncThread:0:NIOServerCnxn@445] - Unexpected Exception: java.nio.channels.CancelledKeyException at sun.nio.ch.SelectionKeyImpl.ensureValid(SelectionKeyImpl.java:73) at sun.nio.ch.SelectionKeyImpl.interestOps(SelectionKeyImpl.java:77) at org.apache.zookeeper.server.NIOServerCnxn.sendBuffer(NIOServerCnxn.java:418) at org.apache.zookeeper.server.NIOServerCnxn.sendResponse(NIOServerCnxn.java:1509) at org.apache.zookeeper.server.FinalRequestProcessor.processRequest(FinalRequestProcessor.java:162) at org.apache.zookeeper.server.SyncRequestProcessor.run(SyncRequestProcessor.java:135) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 11:11:30 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078242 Title: juju cannot connect to zookeeper - too many connections (max 10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078242/+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 1078216] [NEW] exceptions.AttributeError: 'UnitAgent' object has no attribute 'lifecycle'
Public bug reported: I was analyzing why my juju cluster was down. The particular instance I was analyzing had the jenkins-slave charm deployed. Reading /var/lib/juju/units/jenkins-slave-*/charm.log I found the following unhandled exception: 2012-11-13 09:04:23,261: twisted@ERROR: Unhandled error in Deferred: 2012-11-13 09:04:23,262: twisted@ERROR: Unhandled Error Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1181, in unwindGenerator return _inlineCallbacks(None, gen, Deferred()) File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1039, in _inlineCallbacks result = g.send(result) File "/usr/lib/python2.7/dist-packages/juju/agents/base.py", line 250, in stopService yield self.stop() File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1181, in unwindGenerator return _inlineCallbacks(None, gen, Deferred()) --- --- File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1039, in _inlineCallbacks result = g.send(result) File "/usr/lib/python2.7/dist-packages/juju/agents/unit.py", line 127, in stop if self.lifecycle.running: exceptions.AttributeError: 'UnitAgent' object has no attribute 'lifecycle' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:23:43 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078216 Title: exceptions.AttributeError: 'UnitAgent' object has no attribute 'lifecycle' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078216/+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 1078217] [NEW] zookeeper connection is not using exponential backoff
Public bug reported: My juju cluster had some connection issues to zookeeper. While I was reading the charm.log of my jenkins-slave unit I noticed that juju had logged many thousands of exceptions such as this one: 2012-11-09 06:51:07,514: twisted@ERROR: Traceback (most recent call last): 2012-11-09 06:51:07,514: twisted@ERROR: File "/usr/lib/python2.7/dist-packages/txzookeeper/managed.py", line 319, in _cb_created 2012-11-09 06:51:07,514: twisted@ERROR: if self._check_result(result_code, d): 2012-11-09 06:51:07,514: twisted@ERROR: File "/usr/lib/python2.7/dist-packages/txzookeeper/client.py", line 219, in _check_result 2012-11-09 06:51:07,514: twisted@ERROR: self, error) 2012-11-09 06:51:07,515: twisted@ERROR: File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 134, in maybeDeferred 2012-11-09 06:51:07,515: twisted@ERROR: result = f(*args, **kw) 2012-11-09 06:51:07,515: twisted@ERROR: File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1181, in unwindGenerator 2012-11-09 06:51:07,515: twisted@ERROR: return _inlineCallbacks(None, gen, Deferred()) 2012-11-09 06:51:07,516: twisted@ERROR: --- --- 2012-11-09 06:51:07,516: twisted@ERROR: File "/usr/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1039, in _inlineCallbacks 2012-11-09 06:51:07,516: twisted@ERROR: result = g.send(result) 2012-11-09 06:51:07,516: twisted@ERROR: File "/usr/lib/python2.7/dist-packages/txzookeeper/managed.py", line 257, in _cb_connection_error 2012-11-09 06:51:07,517: twisted@ERROR: raise error 2012-11-09 06:51:07,517: twisted@ERROR: zookeeper.ConnectionLossException: connection loss I can see about 300 such exceptions _every second_. This is very bad on two levels: 1) It quickly fills the log with pointless exceptions, using disk space, saturating slow virtual IO 2) It is against proven network practice of using exponential backoff when retrying failed communication ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:26:31 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078217 Title: zookeeper connection is not using exponential backoff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078217/+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 1078214] [NEW] /var/lib/juju/units/*/charm.log is not logrotated
Public bug reported: I've deployed jenkins and jenkins-slave units in my juju cluster. On one of the jenkins-slave instances the /var/lib/juju/units/jenkins- slave-*/charm.log was over 700M in size (uncompressed) before I spotted the issue. This instance is very lightly used and it was running for a few days at most (having been added later in the week) With the size of disk instances this is a major issue. I think this file must be automatically logrotated out of the box. It should be also, perhaps, moved to /var/log/juju for consistency. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:15:34 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078214 Title: /var/lib/juju/units/*/charm.log is not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078214/+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 1078213] [NEW] juju-machine-agent.log is not logrotated
Public bug reported: I've been running a small juju cluster for a week now. There were some connection issues in the data center I'm using and juju had issues connecting to zookeeper. As a result /var/log/juju/juju- machine-agent.log quickly grew to 200M Overall on the four machines that make up my installation all of juju logs, combined, were over 2GB in size. With the size of the instances this is quickly becoming an issue. I don't imagine how I would manage a large juju cluster without scripting around this issue. I think that juju must support logrotate automatically out of the box. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:09:01 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: TERM=xterm-256color LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images precise ** Description changed: - I'm running a small juju cluster for a week now. + I've been running a small juju cluster for a week now. There were some connection issues in the data center I'm using and juju had issues connecting to zookeeper. As a result /var/log/juju/juju- machine-agent.log quickly grew to 200M Overall on the four machines that make up my installation all of juju logs, combined, were over 2GB in size. With the size of the instances this is quickly becoming an issue. I don't imagine how I would manage a large juju cluster without scripting around this issue. I think that juju must support logrotate automatically out of the box. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr531-0ubuntu1.3 ProcVersionSignature: User Name 3.2.0-32.51-virtual 3.2.30 Uname: Linux 3.2.0-32-virtual x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Nov 13 09:09:01 2012 Ec2AMI: ami-00bf Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1078213 Title: juju-machine-agent.log is not logrotated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1078213/+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 1066938] [NEW] maas-dns changes default bind rndc key and breaks initscripts
Public bug reported:
The default install of maas-dns creates the following file
/etc/bind/maas/rndc.conf.maas
Among it are the following two bind9 configuration sections:
key "rndc-maas-key" {
algorithm hmac-md5;
secret "(edited away)";
};
options {
default-key "rndc-maas-key";
default-server 127.0.0.1;
default-port 954;
};
This breaks init scripts (sudo service bind9 restart) as they use the
key called "rndc-key". I would suggest that maas explicitly provide the
key that it wishes to use whenever it interacts with bind9 so that
defaults don't have to change
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: maas-dns 0.1+bzr1264+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
Date: Mon Oct 15 17:15:31 2012
InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release i386
(20121014)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 quantal
--
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/1066938
Title:
maas-dns changes default bind rndc key and breaks initscripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066938/+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 1066929] [NEW] duplicate entry added to named.conf.local on each package reconfigure
Public bug reported: Running dpkg-reconfigure maas-dns breaks the current dns config Observation seems to indicate that each reconfigure appends the following line to /etc/bind/named.conf.local include "/etc/bind/maas/named.conf.maas"; This causes bind to choke and output confusing messages about multiple definitions of the master zone ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: maas-dns 0.1+bzr1264+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Mon Oct 15 17:04:52 2012 InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release i386 (20121014) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- 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/1066929 Title: duplicate entry added to named.conf.local on each package reconfigure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066929/+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 1066935] [NEW] named.conf.rndc.maas is insecure by default
Public bug reported: After default installation the following permissions are applied: -rw-r--r-- 1 maas root 193 Oct 15 14:37 /etc/bind/maas/named.conf.rndc.maas This makes the bind communication key readable to all users of the system ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: maas-dns 0.1+bzr1264+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Mon Oct 15 17:10:58 2012 InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release i386 (20121014) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- 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/1066935 Title: named.conf.rndc.maas is insecure by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066935/+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 955110] [NEW] juju should tell me that I'm not in libvirtd group when running juju bootstrap
Public bug reported: This causes spurious errors errors such as: 2012-03-14 15:37:06,981 ERROR Command '['virsh', 'net-start', 'default']' returned non-zero exit status 1 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: juju 0.5+bzr457-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Wed Mar 14 15:33:55 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120218) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: juju UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: juju (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/955110 Title: juju should tell me that I'm not in libvirtd group when running juju bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/955110/+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 955110] Re: juju should tell me that I'm not in libvirtd group when running juju bootstrap
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/955110 Title: juju should tell me that I'm not in libvirtd group when running juju bootstrap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/955110/+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 644961] Re: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log)
This occurred while configuring the same package using linaro headless 20110208 with identical error messages: qemu: Unsupported syscall: 250 plymouth: ply-event-loop.c:466: ply_event_loop_new: Assertion `loop->epoll_fd >= 0' failed. qemu: uncaught target signal 6 (Aborted) - core dumped Aborted ** Changed in: qemu-kvm (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/644961 Title: qemu crash in rootstock second step during "Setting up console-setup (1.34ubuntu15)" (log reported in bootstrap.log) -- 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 532733] Re: apt/dpkg in qemu-system-arm hangs if a big task is installed
Soren pointed out that is more useful than plain backtrace:
>From the qemu-kvm -O0:
(gdb) thread apply all bt full
Thread 1 (Thread 0x77fc7760 (LWP 31739)):
#0 0xcde9719c in ?? ()
No symbol table info available.
#1 0x7fffe090 in ?? ()
No symbol table info available.
#2 0x005986a4 in tb_find_slow (pc=Cannot access memory at address
0xffbe
) at
/home/zyga/Canonical/ubuntu-qa/qemu-try-2/qemu-kvm-0.12.3+noroms/cpu-exec.c:172
tb = Cannot access memory at address 0xffd2
>From the qemu-kvm -O2 (stock lucid):
(gdb) thread apply all bt full
Thread 1 (Thread 0x77fc7760 (LWP 30205)):
#0 0xcdc546ec in ?? ()
No symbol table info available.
#1 0x00eb in ?? ()
No symbol table info available.
#2 0x00567064 in tlb_set_page (env=0x4, address=13491680,
access_type=3584, mmu_idx=0, is_softmmu=13476464)
at /build/buildd/qemu-kvm-0.12.3+noroms/exec-all.h:98
No locals.
#3 cpu_arm_handle_mmu_fault (env=0x4, address=13491680, access_type=3584,
mmu_idx=0, is_softmmu=13476464)
at /build/buildd/qemu-kvm-0.12.3+noroms/target-arm/helper.c:1178
phys_addr = 102251520
prot = 1
ret =
is_user =
#4 0x00562151 in tlb_fill (addr=3930382336, is_write=, mmu_idx=, retaddr=0x0)
at /build/buildd/qemu-kvm-0.12.3+noroms/target-arm/op_helper.c:98
tb =
saved_env = 0x1
ret =
#5 0x00514aa9 in __ldb_cmmu (addr=240640, mmu_idx=1) at
/build/buildd/qemu-kvm-0.12.3+noroms/softmmu_template.h:131
res =
index = 55297
tlb_addr =
addend =
#6 0x00515a78 in cpu_arm_exec (env1=) at
/build/buildd/qemu-kvm-0.12.3+noroms/cpu-exec.c:630
reg_AREG0 =
saved_AREG0 = 0xcda270
reg_AREG1 =
saved_AREG1 = 0x0
reg_AREG2 =
saved_AREG2 = 0x431bde82d7b634db
ret =
interrupt_request =
tb =
next_tb = 3584
#7 0x0040dfd3 in qemu_cpu_exec (argc=,
argv=, envp=)
at /build/buildd/qemu-kvm-0.12.3+noroms/vl.c:4073
No locals.
#8 tcg_cpu_exec (argc=, argv=,
envp=) at /build/buildd/qemu-kvm-0.12.3+noroms/vl.c:4102
---Type to continue, or q to quit---
ret = -364584960
#9 main_loop (argc=, argv=,
envp=) at /build/buildd/qemu-kvm-0.12.3+noroms/vl.c:4226
r =
#10 main (argc=, argv=, envp=) at /build/buildd/qemu-kvm-0.12.3+noroms/vl.c:6238
gdbstub_dev = 0x0
boot_devices_bitmap = 0
i =
snapshot = 0
initrd_filename = 0x7fffe9f8 "initrd.gz"
kernel_filename = 0x7fffe9e8 "vmlinuz"
kernel_cmdline = 0x7fffea19 "mem=256M"
boot_devices = "cad", '\000'
dcl =
cyls = 0
heads = 0
secs = 0
translation = 0
hda_opts = 0xc9b380
opts =
optind =
r =
optarg =
loadvm = 0x0
machine =
cpu_model = 0x7fffe9d6 "cortex-a8"
fds = {-10656, 32767}
tb_size = 0
pid_file = 0x0
incoming = 0x0
fd =
pwd =
chroot_dir = 0x0
run_as = 0x0
env =
--
apt/dpkg in qemu-system-arm hangs if a big task is installed
https://bugs.launchpad.net/bugs/532733
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
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 532733] Re: apt/dpkg in qemu-system-arm hangs if a big task is installed
I built qemu-kvm with DEB_BUILD_OPTIONS=noopt that replaces -O2 with -O0 and (after _long_ session) ran into this crasher: Program received signal SIGSEGV, Segmentation fault. 0xcde9719c in ?? () (gdb) bt #0 0xcde9719c in ?? () #1 0x7fffe090 in ?? () #2 0x005986a4 in tb_find_slow (pc=Cannot access memory at address 0xffbe ) at /home/zyga/Canonical/ubuntu-qa/qemu-try-2/qemu-kvm-0.12.3+noroms/cpu-exec.c:172 Backtrace stopped: previous frame inner to this frame (corrupt stack?) -- apt/dpkg in qemu-system-arm hangs if a big task is installed https://bugs.launchpad.net/bugs/532733 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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 532733] Re: apt/dpkg in qemu-system-arm hangs if a big task is installed
Ogra proposed change (echo 3 > /proc/cpu/alignement in the guest vm) did not work for me. Ogra is running on i386, I'm on amd64. -- apt/dpkg in qemu-system-arm hangs if a big task is installed https://bugs.launchpad.net/bugs/532733 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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 532733] Re: apt/dpkg in qemu-system-arm hangs if a big task is installed
Hi I can reproduce this each time by running netboot installer using the versatile kernel: #!/bin/sh qemu-img create -f qcow2 sda.qcow2 16G gdb --args qemu-system-arm -M versatilepb -m 256 -cpu cortex-a8 -kernel vmlinuz -initrd initrd.gz -hda sda.qcow2 -append "mem=256M" Here is the backtrace: (gdb) bt #0 0xcdc546ec in ?? () #1 0x00eb in ?? () #2 0x00567064 in tlb_set_page (env=0x4, address=13491680, access_type=3584, mmu_idx=0, is_softmmu=13476464) at /build/buildd/qemu-kvm-0.12.3+noroms/exec-all.h:98 #3 cpu_arm_handle_mmu_fault (env=0x4, address=13491680, access_type=3584, mmu_idx=0, is_softmmu=13476464) at /build/buildd/qemu-kvm-0.12.3+noroms/target-arm/helper.c:1178 #4 0x00562151 in tlb_fill (addr=3930382336, is_write=, mmu_idx=, retaddr=0x0) at /build/buildd/qemu-kvm-0.12.3+noroms/target-arm/op_helper.c:98 #5 0x00514aa9 in __ldb_cmmu (addr=240640, mmu_idx=1) at /build/buildd/qemu-kvm-0.12.3+noroms/softmmu_template.h:131 #6 0x00515a78 in cpu_arm_exec (env1=) at /build/buildd/qemu-kvm-0.12.3+noroms/cpu-exec.c:630 #7 0x0040dfd3 in qemu_cpu_exec (argc=, argv=, envp=) at /build/buildd/qemu-kvm-0.12.3+noroms/vl.c:4073 #8 tcg_cpu_exec (argc=, argv=, envp=) at /build/buildd/qemu-kvm-0.12.3+noroms/vl.c:4102 #9 main_loop (argc=, argv=, envp=) at /build/buildd/qemu-kvm-0.12.3+noroms/vl.c:4226 #10 main (argc=, argv=, envp=) at /build/buildd/qemu-kvm-0.12.3+noroms/vl.c:6238 -- apt/dpkg in qemu-system-arm hangs if a big task is installed https://bugs.launchpad.net/bugs/532733 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- 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
