[Bug 1928842] [NEW] External monitor connected via USB-C not running at native resolution
Public bug reported: I am using a Dell SP2309W connected via HDMI to a Plugable UD-CA1A docking station. The docking station is connected to my System76 Lemur pro (lemp9) via USB-C. The highest resolution the external monitor can run on is 1920x1080i and its native resolution of 2048x1152 is not detected. The system journal contains backtraces indicating a failure in the i915 kernel module: May 14 18:17:13 rubberducky kernel: [ cut here ] May 14 18:17:13 rubberducky kernel: i915 :00:02.0: drm_WARN_ON(!intel_dp->num_source_rates || !intel_dp->num_sink_rates) May 14 18:17:13 rubberducky kernel: WARNING: CPU: 2 PID: 126 at drivers/gpu/drm/i915/display/intel_dp.c:417 intel_dp_set_common_rates+0x4f/0xe0 [i915] May 14 18:17:13 rubberducky kernel: Modules linked in: uas usb_storage hid_generic i915 i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme cec crct10dif_pclmul crc32_pclmul rc_core ghash_clmulni_intel i2c_i801 intel_lpss_pci intel_lpss aesni_intel idma64 xhci_pci crypto_simd i2c_hid cryptd glue_helper psmouse drm nvme_core i2c_smbus rtsx_pci virt_dma xhci_pci_renesas hid pinctrl_cannonlake video system76_acpi(OE) May 14 18:17:13 rubberducky kernel: CPU: 2 PID: 126 Comm: kworker/u16:1 Tainted: G OE 5.11.0-16-generic #17-Ubuntu May 14 18:17:13 rubberducky kernel: Hardware name: System76 Lemur Pro/Lemur Pro, BIOS 2021-03-11_50eedc2 03/11/2021 May 14 18:17:13 rubberducky kernel: Workqueue: events_unbound async_run_entry_fn May 14 18:17:13 rubberducky kernel: RIP: 0010:intel_dp_set_common_rates+0x4f/0xe0 [i915] May 14 18:17:13 rubberducky kernel: Code: 8b 6f 50 4d 85 ed 0f 84 9d 00 00 00 e8 3a 25 f2 db 48 c7 c1 30 70 95 c0 4c 89 ea 48 c7 c7 9a 0c 97 c0 48 89 c6 e8 6e 52 33 dc <0f> 0b 8b 4b 78 8b 73 68 48 8b 7b 70 48 8d 53 7c 4c 8d 83 a4 00 00 May 14 18:17:13 rubberducky kernel: RSP: 0018:b4a84029bba0 EFLAGS: 00010286 May 14 18:17:13 rubberducky kernel: RAX: RBX: 964dc3527140 RCX: 9dd234c8 May 14 18:17:13 rubberducky kernel: RDX: c000dfff RSI: RDI: 0247 May 14 18:17:13 rubberducky kernel: RBP: b4a84029bbb8 R08: R09: b4a84029b980 May 14 18:17:13 rubberducky kernel: R10: b4a84029b978 R11: 9dd53508 R12: 964dd7b6 May 14 18:17:13 rubberducky kernel: R13: 964dc182da40 R14: 964dc3527140 R15: 0001 May 14 18:17:13 rubberducky kernel: FS: () GS:9656f648() knlGS: May 14 18:17:13 rubberducky kernel: CS: 0010 DS: ES: CR0: 80050033 May 14 18:17:13 rubberducky kernel: CR2: 5629c4c4d0e0 CR3: 000115a34006 CR4: 003706e0 May 14 18:17:13 rubberducky kernel: Call Trace: May 14 18:17:13 rubberducky kernel: intel_dp_get_dpcd+0xb5/0xd0 [i915] May 14 18:17:13 rubberducky kernel: intel_dp_detect_dpcd+0x37/0x150 [i915] May 14 18:17:13 rubberducky kernel: intel_dp_detect+0x339/0x440 [i915] May 14 18:17:13 rubberducky kernel: ? ww_mutex_lock+0x83/0x90 May 14 18:17:13 rubberducky kernel: drm_helper_probe_detect+0x4e/0xb0 [drm_kms_helper] May 14 18:17:13 rubberducky kernel: drm_helper_probe_single_connector_modes+0x43d/0x5c0 [drm_kms_helper] May 14 18:17:13 rubberducky kernel: ? _cond_resched+0x1a/0x50 May 14 18:17:13 rubberducky kernel: drm_client_modeset_probe+0x1d6/0x4d0 [drm] May 14 18:17:13 rubberducky kernel: __drm_fb_helper_initial_config_and_unlock+0x36/0xd0 [drm_kms_helper] May 14 18:17:13 rubberducky kernel: drm_fb_helper_initial_config+0x36/0x40 [drm_kms_helper] May 14 18:17:13 rubberducky kernel: intel_fbdev_initial_config+0x18/0x40 [i915] May 14 18:17:13 rubberducky kernel: async_run_entry_fn+0x3c/0x150 May 14 18:17:13 rubberducky kernel: process_one_work+0x220/0x3c0 May 14 18:17:13 rubberducky kernel: worker_thread+0x50/0x370 May 14 18:17:13 rubberducky kernel: kthread+0x12f/0x150 May 14 18:17:13 rubberducky kernel: ? process_one_work+0x3c0/0x3c0 May 14 18:17:13 rubberducky kernel: ? __kthread_bind_mask+0x70/0x70 May 14 18:17:13 rubberducky kernel: ret_from_fork+0x1f/0x30 May 14 18:17:13 rubberducky kernel: ---[ end trace 0a58b4d9a80e1b0f ]--- May 14 18:17:13 rubberducky kernel: [ cut here ] and May 14 18:17:13 rubberducky kernel: [ cut here ] May 14 18:17:13 rubberducky kernel: i915 :00:02.0: drm_WARN_ON(intel_dp->num_common_rates == 0) May 14 18:17:13 rubberducky kernel: WARNING: CPU: 2 PID: 126 at drivers/gpu/drm/i915/display/intel_dp.c:427 intel_dp_set_common_rates+0xb4/0xe0 [i915] May 14 18:17:13 rubberducky kernel: Modules linked in: uas usb_storage hid_generic i915 i2c_algo_bit rtsx_pci_sdmmc drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme cec crct10dif_pclmul crc32_pclmul rc_core ghash_clmulni_intel i2c_i801 intel_lpss_pci intel_lpss aesni_intel idma64 xhci_pci crypto_simd i2c_hid cryptd glue_helper
[Bug 1934147] [NEW] systemd leaks abandoned session scopes
Public bug reported:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
for i in {1..100}; do ssh localhost sudo systemctl daemon-reload & ssh
localhost sleep 1 & done
jobs -p | xargs --verbose --no-run-if-empty kill -KILL
systemctl status --all 2> /dev/null | grep --before-context 3 abandoned
will produce something similar to
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
The system in question is running Bionic, systemd-237-3ubuntu10.48
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Dan Streetman (ddstreet)
Status: New
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934147
Title:
systemd leaks abandoned session scopes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934147/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934147] Re: systemd leaks abandoned session scopes
** Description changed:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
- for i in {1..100}; do ssh localhost sudo systemctl daemon-reload & ssh
localhost sleep 1 & done
- jobs -p | xargs --verbose --no-run-if-empty kill -KILL
- systemctl status --all 2> /dev/null | grep --before-context 3 abandoned
+ $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl daemon-
+ reload & ssh localhost sleep 1 & done
+
+ $ systemctl status --all 2> /dev/null | grep --before-context 3
+ abandoned
will produce something similar to
-│ ├─ 175 su - ubuntu
-│ ├─ 178 -su
-│ ├─62375 systemctl status --all
-│ └─62376 grep --color=auto --before-context 3 abandoned
+ │ ├─ 175 su - ubuntu
+ │ ├─ 178 -su
+ │ ├─62375 systemctl status --all
+ │ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
-Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
+ Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
-Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
+ Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
-Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
+ Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
-Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
+ Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
-Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
+ Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
-Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
+ Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
-Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
+ Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
-Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
+ Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
-│ ├─ 175 su - ubuntu
-│ ├─ 178 -su
-│ ├─62375 systemctl status --all
-│ └─62376 grep --color=auto --before-context 3 abandoned
+ │ ├─ 175 su - ubuntu
+ │ ├─ 178 -su
+ │ ├─62375 systemctl status --all
+ │ └─62376 grep --color=auto --before-context 3 abandoned
The system in question is running Bionic, systemd-237-3ubuntu10.48
** Description changed:
On a system that is monitored via telegraf I found many abandoned
systemd session which I believe are created by a potential race where
systemd is reloading unit files and at the same time a user is
connecting to the system via ssh or is executing the su command.
The simple reproducer
$ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl daemon-
reload & ssh localhost sleep 1 & done
+
+ Wait > 1 second
+
+ $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL
+
+ To clean out STOPPED jobs and
$ systemctl status --all 2> /dev/null | grep --before-context 3
abandoned
will produce something similar to
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 grep --color=auto --before-context 3 abandoned
--
● session-273.scope - Session 273 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-274.scope - Session 274 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
--
● session-30.scope - Session 30 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
--
● session-302.scope - Session 302 of user ubuntu
Loaded: loaded (/run/systemd/transient/session-302.scope; transient)
Transient: yes
Active: active (abandoned) since Wed 2021-06-30 13:32:04 UTC; 4min 6s ago
--
│ ├─ 175 su - ubuntu
│ ├─ 178 -su
│ ├─62375 systemctl status --all
│ └─62376 gre
[Bug 1934218] [NEW] Ticklabels in graphs in dark theme are not visible
Public bug reported: The tickmarks in graphs, e.g. Laptop Battery/History/Charge, are not visible while using the dark theme. The tickmarks are visible using the standard and light theme. ** Affects: gnome-power-manager (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/1934218 Title: Ticklabels in graphs in dark theme are not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1934218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871332] Re: Many records created at the same time may lead to a race condition
Thanks Corey! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871332 Title: Many records created at the same time may lead to a race condition To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1871332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871332] Re: Many records created at the same time may lead to a race condition
Hi Chris, I verified that the package from stein-proposed fixes the issue. ** Tags removed: verification-stein-needed ** Tags added: verification-stein-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871332 Title: Many records created at the same time may lead to a race condition To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1871332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871332] Re: Many records created at the same time may lead to a race condition
Hi Chris, I also verified train-proposed. ** Tags removed: verification-train-needed ** Tags added: verification-train-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871332 Title: Many records created at the same time may lead to a race condition To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1871332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896102] Re: gnome-shell crashes
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896102 Title: gnome-shell crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I had seen this issue on a Precision 5510. I am running the 5.0.x kernel series for a while now and haven't had any issues so far. Currently on 5.0.6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870619] [NEW] rabbitmq-server startup does not wait long enough
Public bug reported: [Impact] * Rabbitmq-server has 2 configuration settings that affect how long it will wait for the mnesia database to become available * The default is 30 seconds x 10 retries = 300 seconds * The startup wrapper rabbitmq-server-wait will wait only 10 seconds * If the database does not come online within 10 seconds the startup script will fail despite the fact that rabbitmq-server is still waiting for another 290 seconds. * This behavior leads to falsely identified failures in OpenStack for example when a Rabbitmq cluster is restarted out of order (LP: #1828988) [Test Case] * Create Rabbitmq cluster and create a queue with "ha-mode: all" policy * Shut down nodes one by one * Restart the node that was shut down first * This node will fail to start because it was not the master of the queue * Note that the startup script (SysV or systemd) will fail after 10 seconds while the rabbitmq-server process is still waiting for the database to come online [Regression Potential] * I am not aware of any potential regressions ** Affects: charm-rabbitmq-server Importance: Undecided Assignee: Nicolas Bock (nicolasbock) Status: New ** Affects: rabbitmq-server (Ubuntu) Importance: Undecided Status: New ** Affects: rabbitmq-server (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: rabbitmq-server (Ubuntu Disco) Importance: Undecided Status: New ** Affects: rabbitmq-server (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: rabbitmq-server (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: charm-rabbitmq-server Assignee: (unassigned) => Nicolas Bock (nicolasbock) ** Also affects: rabbitmq-server (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/1870619 Title: rabbitmq-server startup does not wait long enough To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1870619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890846] Re: [plugin][rabbitmq] add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
Verified on Focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890846 Title: [plugin][rabbitmq] add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1890846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890846] Re: [plugin][rabbitmq] add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
- installed sosreport-4.0-1~ubuntu0.20.04.2 in daily focal container - installed rabbitmq-server-3.8.2-0ubuntu1.1 - ran sosreport --only-plugins rabbitmq - verfied that sos_commands/rabbitmq/rabbitmqctl│All snaps up to date. _eval_rabbit_diagnostics_maybe_stuck exists and contains correct information ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890846 Title: [plugin][rabbitmq] add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1890846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899964] Re: Failover of loadbalancer fails when Amphora master is missing
Verified with the following steps: 1. Create Train deployment with Octavia ./generate-bundle.sh --defaults --use-stable-charms --release train --octavia --num-compute 2 2. Configure Octavia juju config octavia loadbalancer-topology=ACTIVE_STANDBY juju config octavia spare-pool-size=2 2. Create Cirros VMs ./tools/instance_launch.sh 2 cirros 3. Create fake webserver on VMs (See https://code.launchpad.net/~nicolasbock/stsstack-bundles/+git/stsstack- bundles/+merge/392344) ./tools/run_fake_webserver.sh 4. Create load balancer ./tools/create_octavia_lb.sh 5. Test load balancer with curl LB_FIP 6. Shut down a nova-compute that is hosting one of the amphorae. This will break the load balancer due to https://storyboard.openstack.org/#!/story/2003084 7. Install SRU in octavia unit 8. Check load balancer with openstack loadbalancer list 9. Verify operation with step 5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899964 Title: Failover of loadbalancer fails when Amphora master is missing To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1899964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896102] Re: gnome-shell crashes together with emacs-gtk regularly
I made bug 1896273 public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896102 Title: gnome-shell crashes together with emacs-gtk regularly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On systemd-246.4-1ubuntu1 the setting PathChangedGlob leads to an error. But I tried the following which seems to work correctly: [Path] # PathExistsGlob=/var/crash/*.crash PathChanged=/var/crash Thanks @rockrequin for the hint! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
@balint I was wondering why we don't use `PathChanged` in the systemd path file. This checks for any changes in the path and will pick up new crash files... But after reading the systemd docs again I guess the reason is that we want the service to activate if the crash directory already contains a crash file on startup. Am I understanding this correctly? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Fri, Sep 25 2020, Brian Murray wrote: > The issue with PathChanged is that /var/crash is used for writing three > types of files. The .crash file, the .upload file (which signifies the > crash is ready to be uploaded), and the .uploaded file (which contains > the UUID of the crash in the error tracker and indicates the crash has > been uploaded). So if PathChanged is used then whoopsie-upload-all will > be called for .upload and .uploaded files. Additionally, there is no > PathChangedGlob so that we could watch for just .crash files. Thanks, that makes sense. Although re-reading the systemd.path manpage over again I still don't understand how this ever worked. It says: "PathExists= may be used to watch the mere existence of a file or directory. If the file specified exists, the configured unit is activated." I read this as saying that the current behavior on Groovy is actually correct. Or am I missing something? > To help with the issue I'm working on a change to whoopsie-upload-all to > remove the .crash file after a .uploaded file exists. Thanks! I think this certainly should help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
Still failing for me. I see now: Sep 29 06:32:27 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 29 06:32:27 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 29 06:32:27 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 29 06:32:27 rubberducky systemd[1]: apport-autoreport.path: Failed with result 'unit-start-limit-hit'. I have 2 crash files in /var/crash. Note that those two files were in /var/crash already on boot, I didn't add anything to this directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
On Tue, Sep 29 2020, Brian Murray wrote: > On Tue, Sep 29, 2020 at 12:38:38PM -0000, Nicolas Bock wrote: > Could you please run 'systemctl status whoopsie' and > include the output of the command here? $ sudo systemctl status whoopsie ● whoopsie.service - crash report submission daemon Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2020-09-29 06:27:06 MDT; 10h ago Main PID: 2686 (whoopsie) Tasks: 3 (limit: 47889) Memory: 5.0M CGroup: /system.slice/whoopsie.service └─2686 /usr/bin/whoopsie -f Sep 29 08:18:55 rubberducky whoopsie[2686]: [08:18:55] offline Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:18:56 rubberducky whoopsie[2686]: [08:18:56] online Sep 29 08:59:15 rubberducky whoopsie[2686]: [08:59:15] offline Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4 Sep 29 08:59:16 rubberducky whoopsie[2686]: [08:59:16] online -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890846] Re: add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
** Changed in: sosreport (Ubuntu) Assignee: (unassigned) => Nicolas Bock (nicolasbock) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890846 Title: add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1890846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890846] Re: add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
Pushed: https://github.com/sosreport/sos/pull/2189 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890846 Title: add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1890846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871332] Re: Many records created at the same time may lead to a race condition
** Also affects: designate (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/1871332 Title: Many records created at the same time may lead to a race condition To manage notifications about this bug go to: https://bugs.launchpad.net/designate/+bug/1871332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871332] Re: Many records created at the same time may lead to a race condition
** Package changed: designate (Ubuntu) => cloud-archive ** Also affects: cloud-archive/stein 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/1871332 Title: Many records created at the same time may lead to a race condition To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1871332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870619] Re: rabbitmq-server startup does not wait long enough
** Patch added: "rabbitmq-server.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1870619/+attachment/5348305/+files/rabbitmq-server.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870619 Title: rabbitmq-server startup does not wait long enough To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1870619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870619] Re: rabbitmq-server startup does not wait long enough
** Description changed: [Impact] - * Rabbitmq-server has 2 configuration settings that affect how long it will wait for the mnesia database to become available - * The default is 30 seconds x 10 retries = 300 seconds - * The startup wrapper rabbitmq-server-wait will wait only 10 seconds - * If the database does not come online within 10 seconds the startup script will fail despite the fact that rabbitmq-server is still waiting for another 290 seconds. - * This behavior leads to falsely identified failures in OpenStack for example when a Rabbitmq cluster is restarted out of order (LP: #1828988) + * Rabbitmq-server has 2 configuration settings that affect how long it will wait for the mnesia database to become available + * The default is 30 seconds x 10 retries = 300 seconds + * The startup wrapper rabbitmq-server-wait will wait only 10 seconds + * If the database does not come online within 10 seconds the startup script will fail despite the fact that rabbitmq-server is still waiting for another 290 seconds. + * This behavior leads to falsely identified failures in OpenStack for example when a Rabbitmq cluster is restarted out of order (LP: #1828988) [Test Case] - * Create Rabbitmq cluster and create a queue with "ha-mode: all" policy - * Shut down nodes one by one - * Restart the node that was shut down first - * This node will fail to start because it was not the master of the queue - * Note that the startup script (SysV or systemd) will fail after 10 seconds while the rabbitmq-server process is still waiting for the database to come online + * Create Rabbitmq cluster and create a queue with "ha-mode: all" policy + * Shut down nodes one by one + * Restart the node that was shut down first + * This node will fail to start because it was not the master of the queue + * Note that the startup script (SysV or systemd) will fail after 10 seconds while the rabbitmq-server process is still waiting for the database to come online [Regression Potential] - * I am not aware of any potential regressions + * This change potentially increases the time the rabbitmq-server service takes to start up which might lead to failures down the dependency chain of startup services. + * This change potentially changes the result of starting the rabbitmq-server service in case the mnesia database takes more than 10 seconds to come online. Without this change, the service will incorrectly fail while it will succeed with this change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870619 Title: rabbitmq-server startup does not wait long enough To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1870619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
@mruffell thanks! Only a few comments below: > > Note because of this bug, groovy and upstream has now been changed > > to 10 min timeout, down from 1hr. > > We should decide if this is really what we want to do. And if it > should revert to the longer 1hr timeout, propose that upstream. > > I don't really know, is either default timeout better, 10 minutes or > 1 hour? @nicolasbock did you have specific reasoning for the > upstream reduction to 10 minutes? The 10 minutes were a compromise between the default of 5 minutes (for rabbitmq-server) and what upstream thought was a very long wait of 1 hour. > If 10 minutes is what we want, then we should be ok upstream and in > Groovy, and in Focal with the current code in -proposed. In the context of the issues we are seeing with charms the 10 minute timeout should be sufficient. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840844] Re: user with admin role gets logged out when trying to list images
Notes on verification: 1. Create domain/project/user: openstack domain create sru openstack project create --domain sru sru openstack user create --domain sru --password pass --project sru --project-domain sru sru openstack role add --project sru --user sru --user-domain sru member 2. Modify the Glance policies --- /etc/glance/policy.json 2020-06-26 15:38:09.616136115 + +++ /etc/glance/policy.json.original2020-06-26 15:37:58.176276003 + @@ -5,7 +5,7 @@ "add_image": "", "delete_image": "", "get_image": "", -"get_images": "role:admin", +"get_images": "", "modify_image": "", "publicize_image": "role:admin", "communitize_image": "", This will lead to a 403 response from Glance for any non-admin user trying to openstack image list 3. Log into the dashboard as the sru user 4. Got to Project/Compute/Images The UI will throw an error message but then log the user out. The dashboard will go back to the login screen. 5. Install the SRU in the openstack-dashboard unit 5.a. enable proposed repository 5.b. upgrade python-django-horizon package 6. Repeat steps 3 and 4. This time however, the user will not be logged out and only get an error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840844 Title: user with admin role gets logged out when trying to list images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
> I guess this all means that 1) the version in focal-proposed is > correct, and 2) the xenial and bionic versions need the addition of > TimeoutStartSec=600 and Restart=on-failure to their service file, > right? Is that all that's needed? I agree with your assessment regarding Focal and Groovy. However, I would like to verify this thesis for Bionic and Xenial to make sure that rabbitmq-server and systemd behave that way there as well. Note that the systemd service file on Bionic has an ExecStartPost calling a wrapper script in addtion to the ExecStart which wouldn't be necessary if the rabbitmq-server behaved the same way it does in Focal and Groovy. In addition I am uncertain why the service doesn't use `Type=notify` as in the later versions. Rabbitmq-server-3.6.10 understands what `sd_notify` is and I would have thought that this implies that we should be able to use `Type=notify` on Bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
On bionic the rabbitmq-server process returns with exit code 0 regardless of whether it managed to start the server or not. Presumably this behavior is the reason for the ExecStartPost. If I change the service to type notify then systemd notices that the ExecStart command fails to start and the ExecStartPost is not necessary (it is never executed then). However the end result seems to be the same --> Let's leave the type as simple. When I add Restart=on-failure the call to `systemctl start rabbitmq-server` returns with an error message, but the rabbitmq-server service is restarted every 10 seconds anyway. I don't know whether the non-blocking of `systemctl start` will cause issues, but the cluster now recovers as soon as the other broker is started. The relevant changes to the service file are: [Service] TimeoutStartSec=600 Restart=on-failure RestartSec=10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
@mruffel, I can confirm that the bionic package from your PPA is working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
@mruffel, I can also confirm that the xenial package is working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
Brian, I created https://github.com/nicolasbock/rabbitmq-test with some scripts you can use to test rabbitmq. Please let me know if you have any question on how to use those. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
I'll try to verify the SRU. The steps are the same as in the Test Case from the description. The original package will fail fairly quickly. The SRU should fail after 10 minutes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
I have a test env already set up Mauricio. I'll test it there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "bionic-6.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5380685/+files/bionic-6.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
I tested the bionic proposed and found that it was still missing a few things. I have updated and tested the package. The new debdiff is attached. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
Hi @ddstreet. By default rabbitmq-server will wait for 300 seconds before it gives up. Raising the timeout in the systemd service file is not sufficient to guarantee that rabbitmq-server will wait for 10 minutes. We can either add the new configuration file or add a retry to the systemd service file. However, the retry will only affect systemd and not sysv, the new configuration file will affect both. I have added another debdiff (based on proposed) that does both. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "bionic-7.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5382013/+files/bionic-7.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "focal-5.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5382022/+files/focal-5.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "bionic-8.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5382044/+files/bionic-8.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
Verified focal and groovy ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840844] Re: user with admin role gets logged out when trying to list images
I can verify the queens package. ** Tags removed: verification-queens-needed ** Tags added: verification-queens-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840844 Title: user with admin role gets logged out when trying to list images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840844] Re: user with admin role gets logged out when trying to list images
Verified bionic ** 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/1840844 Title: user with admin role gets logged out when trying to list images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] [NEW] rabbitmq-server startup timeouts differ between SysV and systemd
Public bug reported: The startup timeouts were recently adjusted and synchronized between the SysV and systemd startup files. https://github.com/rabbitmq/rabbitmq-server-release/pull/129 ** Affects: rabbitmq-server (Ubuntu) Importance: Low Assignee: Nicolas Bock (nicolasbock) Status: New ** Affects: rabbitmq-server (Ubuntu Xenial) Importance: Undecided Assignee: Nicolas Bock (nicolasbock) Status: New ** Affects: rabbitmq-server (Ubuntu Bionic) Importance: Undecided Assignee: Nicolas Bock (nicolasbock) Status: New ** Affects: rabbitmq-server (Ubuntu Eoan) Importance: Undecided Assignee: Nicolas Bock (nicolasbock) Status: New ** Affects: rabbitmq-server (Ubuntu Focal) Importance: Low Assignee: Nicolas Bock (nicolasbock) Status: New ** Changed in: rabbitmq-server (Ubuntu) Assignee: (unassigned) => Nicolas Bock (nicolasbock) ** Changed in: rabbitmq-server (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "timeout.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5357562/+files/timeout.debdiff ** Also affects: rabbitmq-server (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: rabbitmq-server (Ubuntu Focal) Importance: Low Assignee: Nicolas Bock (nicolasbock) Status: New ** Also affects: rabbitmq-server (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: rabbitmq-server (Ubuntu Eoan) Assignee: (unassigned) => Nicolas Bock (nicolasbock) ** Also affects: rabbitmq-server (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: rabbitmq-server (Ubuntu Bionic) Assignee: (unassigned) => Nicolas Bock (nicolasbock) ** Changed in: rabbitmq-server (Ubuntu Xenial) Assignee: (unassigned) => Nicolas Bock (nicolasbock) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
I have updated the description Eric. Please have another look ** Description changed: - ## DRAFT SRU TMPL ## - [Impact] + The startup timeouts were recently adjusted and synchronized between the + SysV and systemd startup files. - * An explanation of the effects of the bug on users and + https://github.com/rabbitmq/rabbitmq-server-release/pull/129 - * justification for backporting the fix to the stable release. + The new startup files should be included in this package. - * In addition, it is helpful, but not required, to include an -explanation of how the upload fixes this bug. + [Impact] + + After starting the RabbitMQ server process, the startup script will wait + for the server to start by calling `rabbitmqctl wait` and will time out + after 10 s. + + The startup time of the server depends on how quickly the Mnesia + database becomes available and the server will time out after + `mnesia_table_loading_retry_timeout` ms times + `mnesia_table_loading_retry_limit` retries. By default this wait is + 30,000 ms times 10 retries, i.e. 300 s. + + The mismatch between these two timeout values might lead to the startup + script failing prematurely while the server is still waiting for the + Mnesia tables. + + This change introduces variable `RABBITMQ_STARTUP_TIMEOUT` and the + `--timeout` option into the startup script. The default value for this + timeout is set to 10 minutes (600 seconds). + + This change also updates the systemd service file to match the timeout + values between the two service management methods. [Test Case] - * detailed instructions how to reproduce the bug + In a clustered setup with two nodes, A and B. - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. + 1. create queue on A + 2. shut down B + 3. shut down A + 4. boot B + + The broker on B will wait for A. The systemd service will wait for 10 + seconds and then fail. Boot A and the rabbitmq-server process on B will + complete startup. [Regression Potential] - * discussion of how regressions are most likely to manifest as a result - of this change. - - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. - - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. - - [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance - ## DRAFT SRU TMPL ## - - [Original Description] - The startup timeouts were recently adjusted and synchronized between the SysV and systemd startup files. - - https://github.com/rabbitmq/rabbitmq-server-release/pull/129 + This change alters the behavior of the startup scripts when the Mnesia + database takes long to become available. This might lead to failures + further down the service dependency chain. ** Changed in: rabbitmq-server (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: rabbitmq-server (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: rabbitmq-server (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870619] Re: rabbitmq-server startup does not wait long enough
I created another bug LP: #1874075 that tracks changes to the rabbitmq- server package. ** No longer affects: rabbitmq-server (Ubuntu) ** No longer affects: rabbitmq-server (Ubuntu Bionic) ** No longer affects: rabbitmq-server (Ubuntu Eoan) ** No longer affects: rabbitmq-server (Ubuntu Focal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870619 Title: rabbitmq-server startup does not wait long enough To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1870619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358045/+files/eoan.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828988] Re: rabbitmq server fails to start after cluster reboot
** No longer affects: rabbitmq-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828988 Title: rabbitmq server fails to start after cluster reboot To manage notifications about this bug go to: https://bugs.launchpad.net/charm-rabbitmq-server/+bug/1828988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch removed: "focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5357562/+files/timeout.debdiff ** Patch added: "focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358143/+files/focal.debdiff ** Patch removed: "eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358045/+files/eoan.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358144/+files/eoan.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358158/+files/bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358162/+files/xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358453/+files/focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358461/+files/eoan.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358462/+files/bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
Thanks Eric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358546/+files/xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch removed: "focal.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358143/+files/focal.debdiff ** Patch removed: "eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358144/+files/eoan.debdiff ** Patch removed: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358158/+files/bionic.debdiff ** Patch removed: "xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5358162/+files/xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840844] Re: user with admin role gets logged out when trying to list images
** Patch added: "bionic.debdiff" https://bugs.launchpad.net/horizon/+bug/1840844/+attachment/5361828/+files/bionic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840844 Title: user with admin role gets logged out when trying to list images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840844] Re: user with admin role gets logged out when trying to list images
[Impact] Before this change when a 403 error was encountered, such as failure to have the permission to perform an operation, the user would get logged out from UI pages written in the AngularJS framework. For example, if an admin user lacks the get_project permission and tries to access the images page, project->compute->images, the 403 will forcibly log out the user. This change keeps the user logged in when a 403 error is encountered and displays an error message. The change only affects AngularJS pages. [Test Case] * Create a new user without the get_project permission * In the dashboard, access project->compute->images * The user will get logged out [Regression Potential] * The patch changes the behavior of the Horizon code in response to a 403 error. The 403 in the original bug report was caused by a missing get_project permission. While unlikely it is possible that this change is incorrect under different error scenarios. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840844 Title: user with admin role gets logged out when trying to list images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840844] Re: user with admin role gets logged out when trying to list images
** Tags added: sts-sponsor ** Tags added: sts-sru-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840844 Title: user with admin role gets logged out when trying to list images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1840844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "groovy.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5362032/+files/groovy.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840844] Re: user with admin role gets logged out when trying to list images
Copied SRU info to bug description
** Description changed:
+ [Impact]
+
When admin user tries to access project-> compute -> images, if the user
failed on the identity: get_project policy, user will get logged out.
code that failed is in
openstack_dashboard/static/app/core/images/images.module.js
.tableColumns
.append(
{ id: 'owner', priority: 1, filters:
[$memoize(keystone.getProjectName)], policies: [
{rules: [['identity', 'identity:get_project']]}
]
})
it didn't happen in default Horizon. In our production cloud
environment, keystone policy is "identity:get_project":
"rule:cloud_admin or rule:admin_and_matching_target_project_domain_id or
project_id:%(target.project.id)s". If user is not a cloud_admin, the
admin user of a project, need to be member of the domain to satisfies
the rule.
The problem here is the admin user should not get logged out.
It is probably caused by horizon/static/framework/framework.module.js
if (error.status === 403) {
var msg2 = gettext('Forbidden. Redirecting to login');
handleRedirectMessage(msg2, $rootScope, $window, frameworkEvents,
toastService);
}
some log info from keystone
19389 (oslo_policy._cache_handler): 2019-08-20 02:07:25,856 DEBUG
_cache_handler read_cached_file Reloading cached file /etc/keystone/policy.json
19389 (oslo_policy.policy): 2019-08-20 02:07:26,010 DEBUG policy
_load_policy_file Reloaded policy file: /etc/keystone/policy.json
19389 (keystone.common.wsgi): 2019-08-20 02:07:26,019 WARNING wsgi _call_ You
are not authorized to perform the requested action: identity:get_project.
+
+ [Upstream fix description]
+
+ Before this change when a 403 error was encountered, such as failure to have
the permission to perform an operation, the user would get logged out from UI
pages written in the AngularJS framework. For example, if an admin user lacks
the get_project permission and tries to access the
+ images page, project->compute->images, the 403 will forcibly log out the user.
+
+ This change keeps the user logged in when a 403 error is encountered and
+ displays an error message. The change only affects AngularJS pages.
+
+ [Test Case]
+
+ * Create a new user without the get_project permission
+ * In the dashboard, access project->compute->images
+ * The user will get logged out
+
+ [Regression Potential]
+
+ * The patch changes the behavior of the Horizon code in response to a
+ 403 error. The 403 in the original bug report was caused by a missing
+ get_project permission. While unlikely it is possible that this change
+ is incorrect under different error scenarios.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840844
Title:
user with admin role gets logged out when trying to list images
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1840844/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Bug watch added: Debian Bug tracker #958468 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958468 ** Also affects: rabbitmq-server (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958468 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Description changed: The startup timeouts were recently adjusted and synchronized between the SysV and systemd startup files. https://github.com/rabbitmq/rabbitmq-server-release/pull/129 The new startup files should be included in this package. [Impact] After starting the RabbitMQ server process, the startup script will wait for the server to start by calling `rabbitmqctl wait` and will time out after 10 s. The startup time of the server depends on how quickly the Mnesia database becomes available and the server will time out after `mnesia_table_loading_retry_timeout` ms times `mnesia_table_loading_retry_limit` retries. By default this wait is 30,000 ms times 10 retries, i.e. 300 s. The mismatch between these two timeout values might lead to the startup script failing prematurely while the server is still waiting for the Mnesia tables. This change introduces variable `RABBITMQ_STARTUP_TIMEOUT` and the `--timeout` option into the startup script. The default value for this timeout is set to 10 minutes (600 seconds). This change also updates the systemd service file to match the timeout values between the two service management methods. + [Scope] + + Upstream patch: https://github.com/rabbitmq/rabbitmq-server- + release/pull/129 + + * Fix is not included in the Debian package + * Fix is not included in any Ubuntu series + + * Groovy and Focal can apply the upstream patch as is + * Bionic and Xenial need an additional fix in the systemd service file + to set the `RABBITMQ_STARTUP_TIMEOUT` variable for the + `rabbitmq-server-wait` helper script. + [Test Case] In a clustered setup with two nodes, A and B. 1. create queue on A 2. shut down B 3. shut down A 4. boot B The broker on B will wait for A. The systemd service will wait for 10 seconds and then fail. Boot A and the rabbitmq-server process on B will complete startup. [Regression Potential] This change alters the behavior of the startup scripts when the Mnesia database takes long to become available. This might lead to failures further down the service dependency chain. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "focal-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5363534/+files/focal-2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "groovy-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5363533/+files/groovy-2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "xenial-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5363538/+files/xenial-2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "bionic-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+attachment/5363537/+files/bionic-2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "groovy-3.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/rabbitmq-server/+bug/1874075/+attachment/5363738/+files/groovy-3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "focal-3.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/rabbitmq-server/+bug/1874075/+attachment/5363740/+files/focal-3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "bionic-3.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/rabbitmq-server/+bug/1874075/+attachment/5363754/+files/bionic-3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "xenial-3.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/rabbitmq-server/+bug/1874075/+attachment/5363773/+files/xenial-3.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "xenial-6.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/rabbitmq-server/+bug/1874075/+attachment/5364176/+files/xenial-6.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "bionic-5.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/rabbitmq-server/+bug/1874075/+attachment/5364177/+files/bionic-5.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874075] Re: rabbitmq-server startup timeouts differ between SysV and systemd
** Patch added: "focal-4.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/rabbitmq-server/+bug/1874075/+attachment/5364178/+files/focal-4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874075 Title: rabbitmq-server startup timeouts differ between SysV and systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1874075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878049] Re: Update debian/watch file to download from GitHub
** Patch added: "groovy-5.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1878049/+attachment/5369943/+files/groovy-5.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878049 Title: Update debian/watch file to download from GitHub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1878049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878049] Re: Update debian/watch file to download from GitHub
Updated author email in debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878049 Title: Update debian/watch file to download from GitHub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1878049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878049] [NEW] Update debian/watch file to download from GitHub
Public bug reported: The current debian/watch file downloads from an outdated location. Update the watch file so it gets the sources directly from GitHub. ** Affects: rabbitmq-server (Ubuntu) Importance: Undecided Assignee: Nicolas Bock (nicolasbock) Status: New ** Changed in: rabbitmq-server (Ubuntu) Assignee: (unassigned) => Nicolas Bock (nicolasbock) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878049 Title: Update debian/watch file to download from GitHub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1878049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878049] Re: Update debian/watch file to download from GitHub
** Patch added: "groovy-4.debdiff" https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1878049/+attachment/5369942/+files/groovy-4.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878049 Title: Update debian/watch file to download from GitHub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1878049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878049] Re: Update debian/watch file to download from GitHub
I pushed the package to https://launchpad.net/~nicolasbock/+archive/ubuntu/rabbitmq-server. However, it's not building because (I think) the makefile is trying to download a ton of dependencies from GitHub. How is that normally fixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878049 Title: Update debian/watch file to download from GitHub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1878049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 632839] [NEW] package blcr-dkms 0.8.2-13 failed to install/upgrade: blcr kernel module failed to build
Public bug reported: To be honest, I don't know what this package is good for or why it failed. I got this crash report and figured that it might be helpful to you guys. ProblemType: Package DistroRelease: Ubuntu 10.10 Package: blcr-dkms 0.8.2-13 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Tue Sep 7 17:36:26 2010 ErrorMessage: blcr kernel module failed to build PackageArchitecture: all PackageVersion: 0.8.2-13 SourcePackage: blcr Title: package blcr-dkms 0.8.2-13 failed to install/upgrade: blcr kernel module failed to build ** Affects: blcr (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 maverick -- package blcr-dkms 0.8.2-13 failed to install/upgrade: blcr kernel module failed to build https://bugs.launchpad.net/bugs/632839 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 632839] Re: package blcr-dkms 0.8.2-13 failed to install/upgrade: blcr kernel module failed to build
** Attachment added: "DKMSBuildLog.txt" https://bugs.launchpad.net/bugs/632839/+attachment/1555687/+files/DKMSBuildLog.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/632839/+attachment/1555688/+files/Dependencies.txt -- package blcr-dkms 0.8.2-13 failed to install/upgrade: blcr kernel module failed to build https://bugs.launchpad.net/bugs/632839 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 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
$ journalctl -b -u apport-autoreport Sep 14 13:01:52 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Collecting info for /var/crash/_usr_bin_gnome-shell.1000.crash... Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: Marking /var/crash/_usr_bin_gnome-shell.1000.crash for whoopsie upload Sep 14 13:02:07 rubberducky whoopsie-upload-all[145261]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147307]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147307]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147310]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147310]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147313]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147313]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147315]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147315]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: Starting Process error reports when automatic reporting is enabled... Sep 14 13:02:07 rubberducky whoopsie-upload-all[147317]: /var/crash/_usr_bin_gnome-shell.1000.crash already marked for upload, skipping Sep 14 13:02:07 rubberducky whoopsie-upload-all[147317]: All reports processed Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Succeeded. Sep 14 13:02:07 rubberducky systemd[1]: Finished Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 14 13:02:07 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Start request repeated too quickly. Sep 14 13:02:07 rubberducky systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Sep 14 13:02:07 rubberducky systemd[1]: Failed to start Process error reports when automatic reporting is enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
The error message (the last 3 lines) keep repeating ad infinitum until I manually remove the crash files in /var/crash as Rocky notes in https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/comments/13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896102] [NEW] gnome-shell crashes together with emacs-gtk regularly
Public bug reported: Regularly emacs-gtk crashes (reported separately in LP: #1896100) and with it gnome-shell crashes as well. Since those two crashes happen at the same time I am assuming that those two events are related. I don't know what the causal relation is though. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.37.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4 Uname: Linux 5.8.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 12:54:15 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-17 (153 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=screen XDG_RUNTIME_DIR= PATH=(custom, user) RelatedPackageVersions: mutter-common 3.37.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896102 Title: gnome-shell crashes together with emacs-gtk regularly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896100] Re: emacs-gtk crashes regularly
Reported gnome-shell crash separately at LP: #1896102 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896100 Title: emacs-gtk crashes regularly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1896100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896100] [NEW] emacs-gtk crashes regularly
Public bug reported: Every few days emacs crashes together with gnome-shell. At crash the application is idle. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: emacs-gtk 1:26.3+1-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-lowlatency 5.8.4 Uname: Linux 5.8.0-18-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 12:50:48 2020 InstallationDate: Installed on 2020-04-17 (153 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=screen XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: emacs UpgradeStatus: Upgraded to groovy on 2020-07-19 (59 days ago) ** Affects: emacs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896100 Title: emacs-gtk crashes regularly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1896100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896102] Re: gnome-shell crashes together with emacs-gtk regularly
I uploaded another crash report at LP: #1896273. Hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896102 Title: gnome-shell crashes together with emacs-gtk regularly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890846] Re: [plugin][rabbitmq] add output of: rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
** Description changed:
[Impact]
+
+ We have seen customer cases where the output of
+ `rabbit_diagnostics:maybe_stuck()` provided helpful information in
+ debugging the root cause. Automatically collecting this information
+ will potentially expedite the debugging of rabbitmq-server related
+ issues.
[Test Case]
+ Run the rabbitmq plugin on a machine running a rabbitmq broker. On a
+ fresh Focal install, the output will look like the following:
+
+ 2020-09-18 12:55:47 There are 257 processes.
+ 2020-09-18 12:55:47 Investigated 1 processes this round, 5000ms to go.
+ 2020-09-18 12:55:47 Investigated 1 processes this round, 4500ms to go.
+ 2020-09-18 12:55:48 Investigated 1 processes this round, 4000ms to go.
+ 2020-09-18 12:55:48 Investigated 1 processes this round, 3500ms to go.
+ 2020-09-18 12:55:49 Investigated 1 processes this round, 3000ms to go.
+ 2020-09-18 12:55:49 Investigated 1 processes this round, 2500ms to go.
+ 2020-09-18 12:55:50 Investigated 1 processes this round, 2000ms to go.
+ 2020-09-18 12:55:50 Investigated 1 processes this round, 1500ms to go.
+ 2020-09-18 12:55:51 Investigated 1 processes this round, 1000ms to go.
+ 2020-09-18 12:55:51 Investigated 1 processes this round, 500ms to go.
+ 2020-09-18 12:55:52 Found 1 suspicious processes.
+ 2020-09-18 12:55:52 [{pid,<10643.1.0>},
+ {registered_name,erts_code_purger},
+ {current_stacktrace,
+ [{erts_code_purger,wait_for_request,0,[]}]},
+ {initial_call,{erts_code_purger,start,0}},
+ {message_queue_len,0},
+ {links,[]},
+ {monitors,[]},
+ {monitored_by,[]},
+ {heap_size,1598}]
+ ok
+
+ In case some Erlang runtime threads are stuck they will show in the
+ above list.
+
[Regression Potential]
+
+ This function was introduced with rabbitmq-server-3.3.4 which covers
+ Xenial upwards. The command would not work on earlier versions of
+ rabbitmq-server.
[Other Info]
* Upstream commit:
https://github.com/sosreport/sos/commit/af5891786ff8c4e33c341fe9cca690fc77ac768f
[Original Description]
Extend the rabbitmq plugin to include the output of:
- sudo rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
+ sudo rabbitmqctl eval 'rabbit_diagnostics:maybe_stuck().'
This information is useful to get insights of the state of the erlang
virtual machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890846
Title:
[plugin][rabbitmq] add output of: rabbitmqctl eval
'rabbit_diagnostics:maybe_stuck().'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1890846/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
When I run the whoopsie upload script I get: $ sudo /usr/share/apport/whoopsie-upload-all /var/crash/_usr_bin_emacs-gtk.1000.crash already marked for upload, skipping All reports processed Why is it skipping the crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
After deleting the files *.upload{,ed} I can run
$ sudo /usr/share/apport/whoopsie-upload-all
/var/crash/_usr_bin_emacs-gtk.1000.crash already has info collected
Marking /var/crash/_usr_bin_emacs-gtk.1000.crash for whoopsie upload
All reports processed
And get the two files back. The content of the uploaded file is
$ sudo cat _usr_bin_emacs-gtk.1000.uploaded
1c9b8196-f9f4-11ea-b6f1-fa163ee63de6
Is this procedure supposed to delete the crash file at some point?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891657
Title:
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896273] Re: emacs-gtk crashed with SIGABRT in raise()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896273 Title: emacs-gtk crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs/+bug/1896273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058286] Re: Requesting SRU for Octavia 10.1.1
I ran the tox test-suite on jammy on octavia-10.1.1-0ubuntu1: ERROR: docs: commands failed py3: commands succeeded functional-py3: commands succeeded pep8: commands succeeded specs: commands succeeded pip-missing-reqs: commands succeeded pip-extra-reqs: commands succeeded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058286 Title: Requesting SRU for Octavia 10.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2058286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058286] Re: Requesting SRU for Octavia 10.1.1
Verified on Jammy / Yoga with octavia 10.1.1-0ubuntu1. Both amphora and ovn providers work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058286 Title: Requesting SRU for Octavia 10.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/2058286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771740] Re: Expose link offload options
** Patch added: "Updated focal debdiff" https://bugs.launchpad.net/netplan/+bug/1771740/+attachment/5534966/+files/focal.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771740 Title: Expose link offload options To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1771740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771740] Re: Expose link offload options
** Patch added: "Updated hirsute debdiff" https://bugs.launchpad.net/netplan/+bug/1771740/+attachment/5534967/+files/hirsute.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771740 Title: Expose link offload options To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1771740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771740] Re: Expose link offload options
** Patch added: "Updated impish debdiff" https://bugs.launchpad.net/netplan/+bug/1771740/+attachment/5534968/+files/impish.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771740 Title: Expose link offload options To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1771740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
