[Bug 1879692] Re: [SRU] Strongswan pki creates CA certificates with invalid Key Usage flags
Another +1 for what it's worth, this fixes things nicely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879692 Title: [SRU] Strongswan pki creates CA certificates with invalid Key Usage flags To manage notifications about this bug go to: https://bugs.launchpad.net/strongswan/+bug/1879692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808951] Re: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object
I can confirm the python3-nova and associated dependencies from cloud- archive:stein-proposed have stopped the errors like these ones form the original report: 2018-12-18 07:41:55.364 26870 ERROR nova.api.openstack [Previous line repeated 280 more times] 2018-12-18 07:41:55.364 26870 ERROR nova.api.openstack RecursionError: maximum recursion depth exceeded while calling a Python object I tested on bionic using the PPA and whereas nova was not accepting any requests before, now it works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808951 Title: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1808951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827867] Re: [stein] maximum recursion depth exceeded while calling a Python object (File "/usr/lib/python3.6/ssl.py", line 465, in options)
*** This bug is a duplicate of bug 1808951 *** https://bugs.launchpad.net/bugs/1808951 I hit this as well. It looks like it is fixed over in https://bugs.launchpad.net/nova/+bug/1808951 I've tested, and at least for bionic-stein, the problem is resolved with those proposed packages. ** This bug has been marked a duplicate of bug 1808951 python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827867 Title: [stein] maximum recursion depth exceeded while calling a Python object (File "/usr/lib/python3.6/ssl.py", line 465, in options) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1827867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827264] Re: ovs-vswitchd thread consuming 100% CPU
A bit of follow up on this:
strace on the thread in question shows the following:
13:35:47 poll([{fd=23, events=POLLIN}], 1, 0) = 0 (Timeout) <0.18>
13:35:47 epoll_wait(42, [{EPOLLIN, {u32=3, u64=3}}], 9, 0) = 1 <0.18>
13:35:47 recvmsg(417, {msg_namelen=0}, MSG_DONTWAIT) = -1 EAGAIN
(Resource temporarily unavailable) <0.18>
13:35:47 poll([{fd=11, events=POLLIN}, {fd=42, events=POLLIN}, {fd=23,
events=POLLIN}], 3, 2147483647) = 1 ([{fd=42, revents=POLLIN}]) <0.19>
13:35:47 getrusage(RUSAGE_THREAD, {ru_utime={tv_sec=490842,
tv_usec=749026}, ru_stime={tv_sec=710657, tv_usec=442946}, ...}) = 0
<0.18>
13:35:47 poll([{fd=23, events=POLLIN}], 1, 0) = 0 (Timeout) <0.18>
13:35:47 epoll_wait(42, [{EPOLLIN, {u32=3, u64=3}}], 9, 0) = 1 <0.19>
13:35:47 recvmsg(417, {msg_namelen=0}, MSG_DONTWAIT) = -1 EAGAIN
(Resource temporarily unavailable) <0.18>
13:35:47 poll([{fd=11, events=POLLIN}, {fd=42, events=POLLIN}, {fd=23,
events=POLLIN}], 3, 2147483647) = 1 ([{fd=42, revents=POLLIN}]) <0.19>
13:35:47 getrusage(RUSAGE_THREAD, {ru_utime={tv_sec=490842,
tv_usec=749108}, ru_stime={tv_sec=710657, tv_usec=442946}, ...}) = 0
<0.17>
And if I strace with -c to collect a summary, after 4-5 seconds it shows
the following:
sudo strace -c -p 1658344
strace: Process 1658344 attached
^Cstrace: Process 1658344 detached
% time seconds usecs/call callserrors syscall
-- --- --- - -
0.000.00 0 9 write
0.000.00 0 56397 poll
0.000.00 0 28198 28198 recvmsg
0.000.00 0 28199 getrusage
0.000.00 0 14856 futex
0.000.00 0 28199 epoll_wait
-- --- --- - -
100.000.00141150 28254 total
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827264
Title:
ovs-vswitchd thread consuming 100% CPU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1827264/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827264] [NEW] ovs-vswitchd thread consuming 100% CPU
Public bug reported:
I have an ovs-vswitchd process consuming 100% CPU in a very lightly used
Openstack Rocky cloud running on Bionic. The version in question is
openvswitch-switch 2.10.0-0ubuntu2~cloud0
ovs-vswitchd is running alongside various neutron processes
(lbaasv2-agent, metadata-agent, l3-agent, dhcp-agent, openvswitch-agent)
inside an LXC container on a physical host. There is a single neutron
router, and the entire environment including br-tun, br-ex, and br-int
traffic barely goes over 200KiB/s TX/RX combined.
The issue appears to have arisen on its own after the host was hard
rebooted. On restart ovs-vswitchd came up with high load and it has not
diminished since then.
The thread that is consuming CPU looks like this in ps and shows up with the
name 'handler89':
UID PIDSPIDPPID C STIME TTY TIME CMD
root72677454 1 99 Apr23 ?8-03:38:14 ovs-vswitchd
unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info
--mlockall --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log
--pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach
Logs in /var/log/openvswitch/ovs-vswitchd.log show ~14000 entries like this per
day - roughly one per second:
2019-05-01T18:34:30.110Z|237220|poll_loop(handler89)|INFO|Dropped
1092844 log messages in last 6 seconds (most recently, 0 seconds ago)
due to excessive rate
2019-05-01T18:34:30.110Z|237221|poll_loop(handler89)|INFO|wakeup due to
[POLLIN] on fd 42 (unknown anon_inode:[eventpoll]) at ../lib/dpif-
netlink.c:2786 (99% CPU usage)
Logs in /var/log/neutron/neutron-openvswitch-agent.log show entries like
this, again one set per second for ~14000 per day:
2019-05-01 18:35:31.174 13621 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-
7e354ade-55a3-46ba-adf4-db49a51e5218 - - - - -] Agent rpc_loop -
iteration:355070 started rpc_loop /usr/lib/python3/dist-
packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:2086
2019-05-01 18:35:31.177 13621 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.openflow.native.ofswitch
[req-7e354ade-55a3-46ba-adf4-db49a51e5218 - - - - -] ofctl request
version=0x4,msg_type=0x12,msg_len=0x38,xid=0x81826d95,OFPFlowStatsRequest(cookie=0,cookie_mask=0,flags=0,match=OFPMatch(oxm_fields={}),out_group=4294967295,out_port=4294967295,table_id=23,type=1)
result
[OFPFlowStatsReply(body=[OFPFlowStats(byte_count=0,cookie=13408676230369642694,duration_nsec=72400,duration_sec=710697,flags=0,hard_timeout=0,idle_timeout=0,instructions=[],length=56,match=OFPMatch(oxm_fields={}),packet_count=0,priority=0,table_id=23)],flags=0,type=1)]
_send_msg /usr/lib/python3/dist-
packages/neutron/plugins/ml2/drivers/openvswitch/agent/openflow/native/ofswitch.py:114
2019-05-01 18:35:31.179 13621 DEBUG
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [req-
7e354ade-55a3-46ba-adf4-db49a51e5218 - - - - -] Agent rpc_loop -
iteration:355070 completed. Processed ports statistics: {'regular':
{'added': 0, 'updated': 0, 'removed': 0}}. Elapsed:0.005
loop_count_and_wait /usr/lib/python3/dist-
packages/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py:1875
I'm not sure what else information to add here but am happy to gather more
diagnostic data to try to pin this down. I did come across
https://mail.openvswitch.org/pipermail/ovs-discuss/2018-October/047558.html
which is the same version as mine and the symptoms appear to be the same.
Below are various ovs-dpctl/ofctl show reports:
root@juju-df624b-4-lxd-10:~# ovs-dpctl show
system@ovs-system:
lookups: hit:223561120 missed:5768546 lost:798
flows: 131
masks: hit:2284286371 total:15 hit/pkt:9.96
port 0: ovs-system (internal)
port 1: br-ex (internal)
port 2: eth1
port 3: gre_sys (gre: packet_type=ptap)
port 4: br-tun (internal)
port 5: br-int (internal)
port 6: tapa062d6f1-40
port 7: tapf90e3ab6-13
port 8: tap45ba891c-4c
root@juju-df624b-4-lxd-10:~# ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:3643edb09542
n_tables:254, n_buffers:0
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src
mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
1(int-br-ex): addr:4a:b4:cc:dd:aa:ac
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
2(patch-tun): addr:7a:36:76:1f:47:6e
config: 0
state: 0
speed: 0 Mbps now, 0 Mbps max
3(tapa062d6f1-40): addr:92:d4:6c:26:55:0a
config: 0
state: 0
current:10GB-FD COPPER
speed: 1 Mbps now, 0 Mbps max
4(tapf90e3ab6-13): addr:9e:8b:4f:ae:8f:ba
config: 0
state: 0
current:10GB-FD COPPER
speed: 1 Mbps now, 0 Mbps max
5(tap45ba891c-4c): addr:76:45:39:c8:d7:e0
config: 0
state: 0
current:10GB-FD COPPER
speed: 1 Mbps now, 0 Mbps max
LOCAL(b
[Bug 1825872] [NEW] python3-neutron dependency on python3-oslo.privsep dependency needs to run update-alternatives
Public bug reported: I'm not clear on how to trigger the set of installed packages that leads to this bug, but in any case, I ran into an issue where neutron-dhcp- agent would refuse to work. Logs looked like this: Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 CRITICAL privsep [-] Unhandled error: ImportError: No module named neutron.privileged Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 ERROR privsep Traceback (most recent call last): Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 ERROR privsep File "/usr/bin/privsep-helper", line 10, in Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 ERROR privsep sys.exit(helper_main()) Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 ERROR privsep File "/usr/lib/python2.7/dist-packages/oslo_privsep/daemon.py", line 480, in helper_main Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 ERROR privsep context = importutils.import_class(cfg.CONF.privsep_context) Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 ERROR privsep File "/usr/lib/python2.7/dist-packages/oslo_utils/importutils.py", line 30, in import_class Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 ERROR privsep __import__(mod_str) Apr 22 14:51:48 juju-df624b-4-lxd-10 neutron-dhcp-agent[1999891]: 2019-04-22 14:51:48.176 2000527 ERROR privsep ImportError: No module named neutron.privileged Looking at the neutron-dhcp-agent process, it was invoked using python3.6, whereas the traceback shows errors with python2.7. With python3-neutron installed and an older python-oslo.privsep and newner python3-oslo.privsep set of packages, the wrapper defaults to the 2.7 version, which stops the agent from working. Again, I'm not sure what the process was that led up to the new python3-oslo.privsep being installed, but the cloud has been upgraded through various releases, so at some point neutron switched over to python3-neutron. The issue appears to be the upgrade did not run update-alternatives, which results in the following: sudo update-alternatives --config privsep-helper There are 2 choices for the alternative privsep-helper (providing /usr/bin/privsep-helper). SelectionPath Priority Status * 0/usr/bin/python2-privsep-helper 300 auto mode 1/usr/bin/python2-privsep-helper 300 manual mode 2/usr/bin/python3-privsep-helper 200 manual mode Switching the privsep-helper to python3-privsep-helper gets the neutron- dhcp-agent running again. ** Affects: neutron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825872 Title: python3-neutron dependency on python3-oslo.privsep dependency needs to run update-alternatives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1825872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759684] [NEW] squid3 upstream bug 4477 - Linear search through in-memory nodes leads to 100% CPU usage
Public bug reported: This is to track the upstream Squid 3.x bug in https://bugs.squid- cache.org/show_bug.cgi?id=4477 Briefly, squid will consume all available CPU when it is used to request large files using memory or disk caches. If/when that bug is fixed, the fix should be backported to squid3 in the Ubuntu repositories. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759684 Title: squid3 upstream bug 4477 - Linear search through in-memory nodes leads to 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1759684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679322] Re: maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server
Sure, here's term.log: Log started: 2018-01-08 14:59:40 Log ended: 2018-01-08 15:00:02 Log started: 2018-01-10 14:53:41 Log ended: 2018-01-10 14:53:52 Log started: 2018-01-17 18:01:43 Log ended: 2018-01-17 18:01:59 And here's history.log from the same host: Start-Date: 2018-01-17 18:01:43 Upgrade: python-maas-provisioningserver:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), maas-common:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), maas-cli:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), maas-dhcp:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), maas-cluster-controller:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3), python-maas-client:amd64 (1.9.5+bzr4599-0ubuntu1~14.04.2, 1.9.5+bzr4599-0ubuntu1~14.04.3) End-Date: 2018-01-17 18:01:59 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679322 Title: maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1679322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702785] Re: High memory and "can't fork" on heavy long-lived cron daemon
I ran into this as well, with the same host's cron daemon reaching ~8GB RSS memory after a month. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702785 Title: High memory and "can't fork" on heavy long-lived cron daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679322] [NEW] maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server
Public bug reported: An automatic update of maas-dhcp via landscape triggered alerts that DHCP was down on all controller nodes. The update appeared to stop any running dhcpd process, and failed to start the installed isc-dhcp-server dhcp. Logs show messages like this: Apr 3 13:40:18 kernel: [17717361.075006] init: isc-dhcp-server main process (15092) killed by TERM signal Apr 3 13:40:28 maas.dhcp: [ERROR] DHCPv4 server failed to stop: 'maas-dhcpd' is unknown to upstart. Apr 3 13:40:28 maas.dhcp: [ERROR] DHCPv4 server failed to stop: 'maas-dhcpd' is unknown to upstart. ** Affects: maas (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679322 Title: maas-dhcp upgrade to 1.9.5+bzr4599-0ubuntu1~14.04.1 fails to start installed isc-dhcp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1679322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616214] Re: Macbook Air resumes immediately after suspend
I've had a go with linux- image-4.8.0-040800rc3-generic_4.8.0-040800rc3.201608212032_amd64 and the behaviour is the same, suspend immediately wakes up. I also tried last week with linux- image-4.7.0-040700-generic_4.7.0-040700.201608021801_amd64 and it was present there. Marked as confirmed and tagged as requested. Please let me know if there is any more information that I can gather. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616214 Title: Macbook Air resumes immediately after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311724] Re: Macbook Air resumes immidiately after suspend
I opened a new bug about those over in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616214 It is still affecting me using 16.04 on a Macbook Air 6.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311724 Title: Macbook Air resumes immidiately after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616214] [NEW] Macbook Air resumes immediately after suspend
Public bug reported: Based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311724 I am opening this bug to tackle the issue of a Macbook Air that resumes immediately after suspending. I have the exact same symptoms as those described in the first bug. The first suspend on battery power works without any issues. After that, even trying the 2x pm-suspend method doesn't work. Here's an excerpt from dmesg showing the suspend: [11363.316508] PM: Syncing filesystems ... done. [11363.683228] PM: Preparing system for sleep (mem) [11363.683388] Freezing user space processes ... (elapsed 0.002 seconds) done. [11363.685415] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [11363.686602] PM: Suspending system (mem) [11363.686629] Suspending console(s) (use no_console_suspend to debug) [11363.686839] sd 1:0:0:0: [sda] Synchronizing SCSI cache [11363.686890] sd 1:0:0:0: [sda] Stopping disk [11363.689056] R8188EU: INFO indicate disassoc [11364.057112] PM: suspend of devices complete after 370.364 msecs [11364.079232] PM: late suspend of devices complete after 22.117 msecs [11364.079400] thunderbolt :07:00.0: suspending... [11364.079620] thunderbolt :07:00.0: stopping RX ring 0 [11364.079623] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1) [11364.079628] thunderbolt :07:00.0: stopping TX ring 0 [11364.079631] thunderbolt :07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0) [11364.079633] thunderbolt :07:00.0: control channel stopped [11364.079634] thunderbolt :07:00.0: suspend finished [11364.080060] xhci_hcd :00:14.0: System wakeup enabled by ACPI [11364.095334] pcieport :05:00.0: quirk: cutting power to thunderbolt controller... [11364.506336] mba6x_bl: Invalid response at reg: 0x1 (len: 24) [11364.733532] mba6x_bl: failed to set brightness [11364.733583] PM: noirq suspend of devices complete after 654.350 msecs [11364.733853] ACPI: Preparing to enter system sleep state S3 [11364.763238] ACPI : EC: EC stopped [11364.763238] PM: Saving platform NVS memory [11364.763240] Disabling non-boot CPUs ... [11364.763530] Broke affinity for irq 49 [11364.764553] smpboot: CPU 1 is now offline [11364.776286] Broke affinity for irq 18 [11364.776293] Broke affinity for irq 44 [11364.776299] Broke affinity for irq 46 [11364.776305] Broke affinity for irq 48 [11364.776309] Broke affinity for irq 49 [11364.777347] smpboot: CPU 2 is now offline [11364.787918] Broke affinity for irq 8 [11364.787921] Broke affinity for irq 9 [11364.787924] Broke affinity for irq 16 [11364.787927] Broke affinity for irq 18 [11364.787930] Broke affinity for irq 44 [11364.787933] Broke affinity for irq 45 [11364.787935] Broke affinity for irq 46 [11364.787937] Broke affinity for irq 47 [11364.787940] Broke affinity for irq 48 [11364.787942] Broke affinity for irq 49 [11364.787945] Broke affinity for irq 54 [11364.788969] smpboot: CPU 3 is now offline [11364.805918] ACPI: Low-level resume complete [11364.806002] ACPI : EC: EC started [11364.806004] PM: Restoring platform NVS memory [11364.806415] Enabling non-boot CPUs ... [11364.826307] x86: Booting SMP configuration: [11364.826309] smpboot: Booting Node 0 Processor 1 APIC 0x2 [11364.837869] cache: parent cpu1 should not be sleeping [11364.838662] CPU1 is up [11365.018821] smpboot: Booting Node 0 Processor 2 APIC 0x1 [11365.074966] cache: parent cpu2 should not be sleeping [11365.075057] CPU2 is up [11365.273364] smpboot: Booting Node 0 Processor 3 APIC 0x3 [11365.325736] cache: parent cpu3 should not be sleeping [11365.350542] CPU3 is up [11365.354192] ACPI: Waking up from system sleep state S3 [11365.430255] xhci_hcd :00:14.0: System wakeup disabled by ACPI [11365.431123] pcieport :06:03.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [11365.431125] pcieport :06:04.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [11365.431219] pcieport :06:05.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [11365.431309] pcieport :06:06.0: quirk: waiting for thunderbolt to reestablish PCI tunnels... [11365.446161] thunderbolt :07:00.0: resuming... [11365.446162] thunderbolt :07:00.0: control channel starting... [11365.446165] thunderbolt :07:00.0: starting TX ring 0 [11365.446171] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1) [11365.446172] thunderbolt :07:00.0: starting RX ring 0 [11365.446177] thunderbolt :07:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001) [11365.446181] thunderbolt :07:00.0: resetting switch at 0 [11365.447441] thunderbolt :07:00.0: 0: resuming switch [11365.452967] thunderbolt :07:00.0: resume finished [11365.453101] PM: noirq resume of devices complete after 23.052 msecs [11365.457463] PM: early resume of devices complete after 4.341 msecs [11365.457833] pciehp :06:05.0:pcie24: Timeout on hotplug command 0x1038
[Bug 1616095] [NEW] charm build does not expose default config options from intermediate layers
Public bug reported: When using an intermediate layer (nodejs) to install an extra apt repository, I've run into an issue where the default config.yaml options from the intermediate layer are not being rendered into the final built charm. Specifically, I'm using the nodejs charm here: https://github.com/battlemidget/juju-layer-node I'd like to *not* specify the 'install_sources' and 'install_keys' options in my top level config.yaml, since the layer has those values set to sane defaults. However, if I leave those unset, the built charm ends up using the nodejs' underlying apt layer's config.yaml defaults. My charm is available here: https://code.launchpad.net/~jamon/+junk/hubot When I do a git checkout and charm build of the nodejs charm on its own, I get a rendered config.yaml that looks like this, which is what I would expect. Note hose the install_sources and keys are set properly. "options": "extra_packages": "description": "Space separated list of extra deb packages to install.\n" "type": "string" "default": "" "package_status": "default": "install" "type": "string" "description": "The status of service-affecting packages will be set to this value\ \ in the dpkg database. Valid values are \"install\" and \"hold\".\n" "install_sources": "description": "List of extra apt sources, per charm-helpers standard format (a\ \ yaml list of strings encoded as a string). Each source may be either a line\ \ that can be added directly to sources.list(5), or in the form ppa:/\ \ for adding Personal Package Archives, or a distribution component to enable.\n" "type": "string" "default": | - "https://deb.nodesource.com/node_4.x main" "install_keys": "description": "List of signing keys for install_sources package sources, per\ \ charmhelpers standard format (a yaml list of strings encoded as a string).\ \ The keys should be the full ASCII armoured GPG public keys. While GPG key\ \ ids are also supported and looked up on a keyserver, operators should be aware\ \ that this mechanism is insecure. null can be used if a standard package signing\ \ key is used that will already be installed on the machine, and for PPA sources\ \ where the package signing key is securely retrieved from Launchpad.\n" "type": "string" "default": | - '68576280' Is this behaviour to be expected, and I'll just have to live with setting options for n intermediate layers in my top-level config.yaml? Or is there something I'm missing, or is there a bug in one of the relevant charms? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: charm 2.1.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 23 14:57:46 2016 SourcePackage: charm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: charm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616095 Title: charm build does not expose default config options from intermediate layers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/charm/+bug/1616095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1126890] Re: nrpe removes its PID when scanned by nmap
This bug breaks monitoring for me on over 30 production 12.04 servers. The patch should be reviewed for SRU inclusion since nagios3 (in main) and icinga (universe) are both affected by it. It requires manual intervention to bring the service back on each individual host, so this patch is fairly important to have back ported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1126890 Title: nrpe removes its PID when scanned by nmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1126890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1109051] [NEW] Incorrect package.path in ejabberd2prosody tool
Public bug reported: The /usr/bin/ejabberd2prosody migration tool does not run with a default install on 12.04.1. The package.path needs to read: package.path = package.path .."/usr/lib/prosody/util/?.lua;/usr/lib/prosody/?.lua"; Otherwise it will throw an error like the following: ejabberd2prosody mnesia.dump lua: /usr/bin/ejabberd2prosody:14: module 'util.erlparse' not found: no field package.preload['util.erlparse'] no file './util/erlparse.lua' no file '/usr/local/share/lua/5.1/util/erlparse.lua' no file '/usr/local/share/lua/5.1/util/erlparse/init.lua' no file '/usr/local/lib/lua/5.1/util/erlparse.lua' no file '/usr/local/lib/lua/5.1/util/erlparse/init.lua' no file '/usr/share/lua/5.1/util/erlparse.lua' no file '/usr/share/lua/5.1/util/erlparse/init.lua/usr/lib/prosody/util/util/erlparse.lua' no file './util/erlparse.so' no file '/usr/local/lib/lua/5.1/util/erlparse.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.1/util/erlparse.so' no file '/usr/lib/lua/5.1/util/erlparse.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './util.so' no file '/usr/local/lib/lua/5.1/util.so' no file '/usr/lib/x86_64-linux-gnu/lua/5.1/util.so' no file '/usr/lib/lua/5.1/util.so' no file '/usr/local/lib/lua/5.1/loadall.so' stack traceback: [C]: in function 'require' /usr/bin/ejabberd2prosody:14: in main chunk [C]: ? ** Affects: prosody (Ubuntu) Importance: Undecided Status: New ** Patch added: "update package.path to find utils.erlparse" https://bugs.launchpad.net/bugs/1109051/+attachment/3506101/+files/ejabberd2prosody.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1109051 Title: Incorrect package.path in ejabberd2prosody tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prosody/+bug/1109051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 960757] Re: whoopsie crashed with SIGSEGV in g_object_newv()
Affecting me when run as a Virtualbox guest here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/960757 Title: whoopsie crashed with SIGSEGV in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/960757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 953797] Re: unity-2d-shell crashed with SIGSEGV in geis_filter_delete()
This is occuring in VirtualBox as well, so while the initial report shows NonfreeKernelModules: nvidia, it isn't specific to the video card in use, or proprietary driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/953797 Title: unity-2d-shell crashed with SIGSEGV in geis_filter_delete() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/953797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 685988] Re: Searches including a period (".") return HTTP Status 500 from SolR
This also applies to solr-jetty on 10.04. It is not just searches
containing '.' either - we were seeing it with searches containing '/',
so I'm guessing it can be triggered using a variety of non alpha numeric
characters.
It was fixed upstream in Debian, and Natty according to
https://bugs.launchpad.net/ubuntu/+source/solr/+bug/684756
If using 1.4.1+dfsg1-1ubuntu1 package is an option, that should fix the
issue. Or the manual symlink option works on all distros from what I can
tell. Want to close this?
** Changed in: solr (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685988
Title:
Searches including a period (".") return HTTP Status 500 from SolR
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/solr/+bug/685988/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680817] Re: Personal information is not saved between sessions
Here's a capture of Empathy's debug output when changing an Alias To reproduce: Edit->Personal Information Clear Debug log Change Alias Click 'Close' Edit->Personal Information Click 'Close' The attached output corresponds to those steps. ** Attachment added: "empathy.txt" https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/680817/+attachment/2032582/+files/empathy.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680817 Title: Personal information is not saved between sessions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680817] Re: Personal information is not saved between sessions
@colan, I've run into this problem as well. I have only logged in using one computer (ever) and am seeing the same problem as you, where the alias changes back after clicking the 'Close' button. What is even more troubling is that editing ~/.mission- control/accounts/accounts.cfg to use a different alias/nickname has no effect. When Empathy is restarted, the original alias is back, and is written to that file again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680817 Title: Personal information is not saved between sessions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
