[Bug 1739631] Re: Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739631 Title: Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1739631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769013] Re: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)
I've successfully verified the proposed fix, as documented at issue #1739631 https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1739631/comments/13 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769013 Title: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/josm/+bug/1769013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739631] Re: Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739631 Title: Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1739631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739631] Re: Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file
Tested the proposed fix version 20180516ubuntu1~18.04.1 in a Docker container, and it DID fix the issue, both as an upgrade to a previously installed package version 20170930ubuntu1, and as a first install. Verification steps: Ran the TestHttps program from https://git.mikael.io/mikaelhg/broken-docker-jdk9-cacerts. It successfully completed without throwing an exception, after the upgrade to 20180516ubuntu1~18.04.1. Verified package version: root@89353b964227:/app# apt-cache show ca-certificates-java Package: ca-certificates-java Architecture: all Version: 20180516ubuntu1~18.04.1 Multi-Arch: foreign Priority: optional Section: misc Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian Java Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 42 Depends: ca-certificates (>= 20121114), openjdk-11-jre-headless | java8-runtime-headless, libnss3 (>= 3.12.9+ckbi-1.82-0ubuntu3~) Filename: pool/main/c/ca-certificates-java/ca-certificates-java_20180516ubuntu1~18.04.1_all.deb Size: 12156 MD5sum: fed1dbe07d960d581a8870b6e103eb69 SHA1: c0305a200fb55296a077014af3fd3ad7a4de756d SHA256: 2c312d1c8a14781fc9a074569c9d591e17e00419ab9597a148223d0ac4065bb2 Description: Common CA certificates (JKS keystore) Description-md5: 304cd3554728e5d076f8ecbb3b5057d8 Task: kubuntu-desktop, kubuntu-full Supported: 5y -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739631 Title: Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1739631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739631] Re: Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file
Another workaround, used pyjks to generate a minimal JKS file with an empty password, and relying on the certificate file compatibility mode: echo "storepass=''" >> /etc/default/cacerts echo -e "\xfe\xed\xfe\xed\x00\x00\x00\x02\x00\x00\x00\x00\x57\xbe\xbc\x27\x62\xa2\x1d\x70\xff\xf2\x18\xdd\x59\x68\x01\x1f\xfe\x42\x3a\x69" > /etc/ssl/certs/java/cacerts /var/lib/dpkg/info/ca-certificates-java.postinst configure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739631 Title: Fresh install with JDK 9 can't use the generated PKCS12 cacerts keystore file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1739631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667796] Re: kernel only recognizes 32G of memory
[0.00] Linux version 2.6.35-22-virtual (bui...@yellow) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #35-Ubuntu SMP Sat Oct 16 23:19:29 UTC 2010 (Ubuntu 2.6.35-22.35-virtual 2.6.35.4) [8343235.991081] Memory: 32797532k/33554432k available (5816k kernel code, 448k absent, 756452k reserved, 5366k data, 828k init) Partial boot dmesg from an EC2 m2.4xlarge instance with 65GB of available memory. -- kernel only recognizes 32G of memory https://bugs.launchpad.net/bugs/667796 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
John Johansen's suggested -23.36 kernel booted, but still exhibited bug 667796. Linux ip-10-230-9-131 2.6.35-23-virtual #36~ec2 SMP Thu Oct 28 15:07:00 UTC 2010 x86_64 GNU/Linux [0.00] PERCPU: Embedded 30 pages/cpu @88000e8c7000 s91520 r8192 d23168 u122880 [0.00] pcpu-alloc: s91520 r8192 d23168 u122880 alloc=30*4096 [0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 [8698363.527286] trying to map vcpu_info 0 at 88000e8d2020, mfn 10569b2, offset 32 [8698363.527290] cpu 0 using vcpu_info at 88000e8d2020 [8698363.527292] trying to map vcpu_info 1 at 88000e8f0020, mfn 1056994, offset 32 [8698363.527294] cpu 1 using vcpu_info at 88000e8f0020 ... ubu...@ip-10-230-9-131:~$ free total used free sharedbuffers cached Mem: 32810684 669128 32141556 0 7016 32268 -/+ buffers/cache: 629844 32180840 Swap:0 0 0 -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667796] Re: kernel only recognizes 32G of memory
I was wondering why that kernel version would exhibit this bug, since that's what I've downgraded my Maverick instances to get them to show the correct amount of memory. Once we get a Maverick weekly EC2 image which reliably boots up without hitting bug 651370, I will post the kernel logs from it here. -- kernel only recognizes 32G of memory https://bugs.launchpad.net/bugs/667796 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
Brandon's and Scott's workaround works for me partly, but the kernel on an instance started in such a way seems to detect only 32 GB of memory even for a m2.4xlarge instance which should have 68.4 GB available, according to the EC2 instances page. Is this a side-effect of the workaround, or a completely separate bug? Maveric results: ubu...@ip-10-230-9-87:~$ uname -a Linux ip-10-230-9-87 2.6.35-22-virtual #35-Ubuntu SMP Sat Oct 16 23:19:29 UTC 2010 x86_64 GNU/Linux ubu...@ip-10-230-9-87:~$ ec2metadata --instance-type m2.4xlarge ubu...@ip-10-230-9-87:~$ free total used free sharedbuffers cached Mem: 32810684 667628 32143056 0 6444 32152 -/+ buffers/cache: 629032 32181652 Swap:0 0 0 Expected results (from a SUSE 11 guest): ip-10-230-45-187:~ # uname -a Linux ip-10-230-45-187 2.6.32.19-0.3-ec2 #1 SMP 2010-09-17 20:28:21 +0200 x86_64 x86_64 x86_64 GNU/Linux ip-10-230-45-187:~ # curl http://169.254.169.254/latest/meta-data/instance-type m2.4xlarge ip-10-230-45-187:~ # free total used free sharedbuffers cached Mem: 717051162361584 69343532 0 10972 126424 -/+ buffers/cache:2224188 69480928 Swap:0 0 0 -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 651370] Re: ec2 kernel crash invalid opcode 0000 [#1]
I just tried to launch 16 * m2.4xlarge instances with ami-e43e0b90 in the eu-west-1b area, and not a single one would boot up successfully, because of this bug. Any workaround yet? -- ec2 kernel crash invalid opcode [#1] https://bugs.launchpad.net/bugs/651370 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
