I collected some more loglines, produced by unproductive member of a haproxy failoversystem with usually zero load. over the weekend there are affected several servers. I think this is serious.
Sep 8 17:01:06 myhost kernel: [115882.039808] CIFS: Attempting to mount \\host123\folder Sep 8 17:01:06 myhost systemd[1]: mnt-win_share.mount: Deactivated successfully. Sep 8 17:01:06 myhost kernel: [115882.497413] BUG: kernel NULL pointer dereference, address: 0000000000000040 Sep 8 17:01:06 myhost kernel: [115882.497460] #PF: supervisor read access in kernel mode Sep 8 17:01:06 myhost kernel: [115882.497485] #PF: error_code(0x0000) - not-present page Sep 8 17:01:06 myhost kernel: [115882.497502] PGD 0 P4D 0 Sep 8 17:01:06 myhost kernel: [115882.497515] Oops: 0000 [#1] SMP PTI Sep 8 17:01:06 myhost kernel: [115882.497530] CPU: 1 PID: 1046703 Comm: kworker/1:2 Not tainted 5.15.0-83-generic #92-Ubuntu Sep 8 17:01:06 myhost kernel: [115882.497560] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020 Sep 8 17:01:06 myhost kernel: [115882.497598] Workqueue: cifsoplockd cifs_oplock_break [cifs] Sep 8 17:01:06 myhost kernel: [115882.497691] RIP: 0010:cifs_oplock_break+0x202/0x5c0 [cifs] Sep 8 17:01:06 myhost kernel: [115882.497738] Code: 89 45 b8 c0 eb 02 83 e3 01 e8 aa f6 ff ff 84 db 75 34 49 8b 47 48 4c 89 e2 0f b7 4d b8 4d 89 f0 4c 89 ee 4c 89 ff 48 8b 40 48 <48> 8b 40 40 48 8b 80 28 02 00 00 ff d0 0f 1f 00 41 89 c4 f6 05 30 Sep 8 17:01:06 myhost kernel: [115882.497794] RSP: 0018:ffffa74603d87e10 EFLAGS: 00010246 Sep 8 17:01:06 myhost kernel: [115882.497812] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Sep 8 17:01:06 myhost kernel: [115882.497834] RDX: 000000000000000b RSI: 236fcc211deddb5a RDI: ffff94088f58e000 Sep 8 17:01:06 myhost kernel: [115882.497856] RBP: ffffa74603d87e70 R08: ffff9408a1cd6a40 R09: 0000000000000000 Sep 8 17:01:06 myhost kernel: [115882.497879] R10: ffff9408a2da3000 R11: ffffffffffffff00 R12: 000000000000000b Sep 8 17:01:06 myhost kernel: [115882.497902] R13: 236fcc211deddb5a R14: ffff9408a1cd6a40 R15: ffff94088f58e000 Sep 8 17:01:06 myhost kernel: [115882.497925] FS: 0000000000000000(0000) GS:ffff940bafc80000(0000) knlGS:0000000000000000 Sep 8 17:01:06 myhost kernel: [115882.497951] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 8 17:01:06 myhost kernel: [115882.497971] CR2: 0000000000000040 CR3: 00000001008dc005 CR4: 00000000007706e0 Sep 8 17:01:06 myhost kernel: [115882.498018] PKRU: 55555554 Sep 8 17:01:06 myhost kernel: [115882.498029] Call Trace: Sep 8 17:01:06 myhost kernel: [115882.498040] <TASK> Sep 8 17:01:06 myhost kernel: [115882.498051] ? show_trace_log_lvl+0x1d6/0x2ea Sep 8 17:01:06 myhost kernel: [115882.498071] ? show_trace_log_lvl+0x1d6/0x2ea Sep 8 17:01:06 myhost kernel: [115882.498098] ? process_one_work+0x228/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.498662] ? show_regs.part.0+0x23/0x29 Sep 8 17:01:06 myhost kernel: [115882.499192] ? __die_body.cold+0x8/0xd Sep 8 17:01:06 myhost kernel: [115882.499703] ? __die+0x2b/0x37 Sep 8 17:01:06 myhost kernel: [115882.500219] ? page_fault_oops+0x13b/0x170 Sep 8 17:01:06 myhost kernel: [115882.500699] ? kfree+0x1f7/0x250 Sep 8 17:01:06 myhost kernel: [115882.501195] ? do_user_addr_fault+0x321/0x670 Sep 8 17:01:06 myhost kernel: [115882.501657] ? exc_page_fault+0x77/0x170 Sep 8 17:01:06 myhost kernel: [115882.502125] ? asm_exc_page_fault+0x27/0x30 Sep 8 17:01:06 myhost kernel: [115882.502964] ? cifs_oplock_break+0x202/0x5c0 [cifs] Sep 8 17:01:06 myhost kernel: [115882.503767] process_one_work+0x228/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.504498] worker_thread+0x53/0x420 Sep 8 17:01:06 myhost kernel: [115882.505222] ? process_one_work+0x3d0/0x3d0 Sep 8 17:01:06 myhost kernel: [115882.505959] kthread+0x127/0x150 Sep 8 17:01:06 myhost kernel: [115882.506719] ? set_kthread_struct+0x50/0x50 Sep 8 17:01:06 myhost kernel: [115882.507426] ret_from_fork+0x1f/0x30 Sep 8 17:01:06 myhost kernel: [115882.508112] </TASK> Sep 8 17:01:06 myhost kernel: [115882.508760] Modules linked in: cmac nls_utf8 cifs cifs_arc4 cifs_md4 fscache netfs tls intel_rapl_msr vmw_balloon intel_rapl_common isst_if_mbox_msr isst_if_common nfit rapl joydev input_leds serio_raw vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vsock vmw_vmci mac_hid binfmt_misc sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua pstore_blk ramoops pstore_zone reed_solomon efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear vmwgfx ttm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_kms_helper aesni_intel crypto_simd cryptd syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core ahci mptspi drm i2c_piix4 libahci mptscsih psmouse mptbase vmxnet3 scsi_transport_spi pata_acpi Sep 8 17:01:06 myhost kernel: [115882.515323] CR2: 0000000000000040 Sep 8 17:01:06 myhost kernel: [115882.516096] ---[ end trace c7fc73de58cb1e2f ]--- Sep 8 17:01:06 myhost kernel: [115882.516864] RIP: 0010:cifs_oplock_break+0x202/0x5c0 [cifs] Sep 8 17:01:06 myhost kernel: [115882.517698] Code: 89 45 b8 c0 eb 02 83 e3 01 e8 aa f6 ff ff 84 db 75 34 49 8b 47 48 4c 89 e2 0f b7 4d b8 4d 89 f0 4c 89 ee 4c 89 ff 48 8b 40 48 <48> 8b 40 40 48 8b 80 28 02 00 00 ff d0 0f 1f 00 41 89 c4 f6 05 30 Sep 8 17:01:06 myhost kernel: [115882.520055] RSP: 0018:ffffa74603d87e10 EFLAGS: 00010246 Sep 8 17:01:06 myhost kernel: [115882.520870] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 Sep 8 17:01:06 myhost kernel: [115882.521720] RDX: 000000000000000b RSI: 236fcc211deddb5a RDI: ffff94088f58e000 Sep 8 17:01:06 myhost kernel: [115882.522564] RBP: ffffa74603d87e70 R08: ffff9408a1cd6a40 R09: 0000000000000000 Sep 8 17:01:06 myhost kernel: [115882.523430] R10: ffff9408a2da3000 R11: ffffffffffffff00 R12: 000000000000000b Sep 8 17:01:06 myhost kernel: [115882.524303] R13: 236fcc211deddb5a R14: ffff9408a1cd6a40 R15: ffff94088f58e000 Sep 8 17:01:06 myhost kernel: [115882.525182] FS: 0000000000000000(0000) GS:ffff940bafc80000(0000) knlGS:0000000000000000 Sep 8 17:01:06 myhost kernel: [115882.526076] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Sep 8 17:01:06 myhost kernel: [115882.526984] CR2: 0000000000000040 CR3: 00000001008dc005 CR4: 00000000007706e0 Sep 8 17:01:06 myhost kernel: [115882.527877] PKRU: 55555554 Sep 8 17:17:02 myhost systemd[1]: Created slice User Slice of UID 1002. Sep 8 17:17:02 myhost systemd[1]: Starting User Runtime Directory /run/user/1002... Sep 8 17:17:02 myhost systemd[1]: Finished User Runtime Directory /run/user/1002. Sep 8 17:17:02 myhost systemd[1]: Starting User Manager for UID 1002... Sep 8 17:18:32 myhost systemd[1]: user@1002.service: start operation timed out. Terminating. Sep 8 17:18:37 myhost systemd[1]: user@1002.service: State 'stop-sigterm' timed out. Killing. Sep 8 17:18:37 myhost systemd[1]: user@1002.service: Killing process 1085783 (systemd) with signal SIGKILL. Sep 8 17:18:42 myhost systemd[1]: user@1002.service: Processes still around after SIGKILL. Ignoring. Sep 8 17:18:47 myhost systemd[1]: user@1002.service: State 'final-sigterm' timed out. Killing. Sep 8 17:18:47 myhost systemd[1]: user@1002.service: Killing process 1085783 (systemd) with signal SIGKILL. Sep 8 17:18:53 myhost systemd[1]: user@1002.service: Processes still around after final SIGKILL. Entering failed mode. Sep 8 17:18:53 myhost systemd[1]: user@1002.service: Failed with result 'timeout'. Sep 8 17:18:53 myhost systemd[1]: user@1002.service: Unit process 1085783 (systemd) remains running after unit stopped. Sep 8 17:18:53 myhost systemd[1]: Failed to start User Manager for UID 1002. Sep 8 17:18:53 myhost systemd[1]: Started Session 558 of User proxysync. Sep 8 17:18:53 myhost systemd[1]: user@1002.service: Found left-over process 1085783 (systemd) in control group while starting unit. Ignoring. Sep 8 17:18:53 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 8 17:18:53 myhost systemd[1]: Starting User Manager for UID 1002... Sep 8 17:20:23 myhost systemd[1]: user@1002.service: start operation timed out. Terminating. Sep 8 17:20:29 myhost systemd[1]: user@1002.service: State 'stop-sigterm' timed out. Killing. Sep 8 17:20:29 myhost systemd[1]: user@1002.service: Killing process 1086845 (systemd) with signal SIGKILL. Sep 8 17:20:29 myhost systemd[1]: user@1002.service: Killing process 1085783 (systemd) with signal SIGKILL. Sep 8 17:20:34 myhost systemd[1]: user@1002.service: Processes still around after SIGKILL. Ignoring. Sep 8 17:20:39 myhost systemd[1]: user@1002.service: State 'final-sigterm' timed out. Killing. Sep 8 17:20:39 myhost systemd[1]: user@1002.service: Killing process 1086845 (systemd) with signal SIGKILL. Sep 8 17:20:39 myhost systemd[1]: user@1002.service: Killing process 1085783 (systemd) with signal SIGKILL. Sep 8 17:20:44 myhost systemd[1]: user@1002.service: Processes still around after final SIGKILL. Entering failed mode. Sep 8 17:20:44 myhost systemd[1]: user@1002.service: Failed with result 'timeout'. Sep 8 17:20:44 myhost systemd[1]: user@1002.service: Unit process 1085783 (systemd) remains running after unit stopped. Sep 8 17:20:44 myhost systemd[1]: user@1002.service: Unit process 1086845 (systemd) remains running after unit stopped. Sep 8 17:20:44 myhost systemd[1]: Failed to start User Manager for UID 1002. Sep 8 17:20:44 myhost systemd[1]: Started Session 560 of User proxysync. Sep 8 17:47:33 myhost pacemaker-controld[989]: notice: High CPU load detected: 6.520000 Sep 8 17:48:03 myhost pacemaker-controld[989]: notice: High CPU load detected: 6.710000 Sep 8 17:48:32 myhost systemd[1]: user@1002.service: start operation timed out. Terminating. Sep 8 17:48:33 myhost pacemaker-controld[989]: notice: High CPU load detected: 6.830000 Sep 8 17:48:37 myhost systemd[1]: user@1002.service: State 'stop-sigterm' timed out. Killing. Sep 8 17:48:37 myhost systemd[1]: user@1002.service: Killing process 1102229 (systemd) with signal SIGKILL. Sep 8 17:48:37 myhost systemd[1]: user@1002.service: Killing process 1085783 (systemd) with signal SIGKILL. Sep 8 17:48:37 myhost systemd[1]: user@1002.service: Killing process 1086845 (systemd) with signal SIGKILL. Sep 8 17:48:37 myhost systemd[1]: user@1002.service: Killing process 1094006 (systemd) with signal SIGKILL. Sep 8 17:48:37 myhost systemd[1]: user@1002.service: Killing process 1095044 (systemd) with signal SIGKILL. Sep 8 17:48:42 myhost systemd[1]: user@1002.service: Processes still around after SIGKILL. Ignoring. Sep 8 17:48:47 myhost systemd[1]: user@1002.service: State 'final-sigterm' timed out. Killing. Sep 8 17:48:47 myhost systemd[1]: user@1002.service: Killing process 1102229 (systemd) with signal SIGKILL. Sep 8 17:48:47 myhost systemd[1]: user@1002.service: Killing process 1085783 (systemd) with signal SIGKILL. Sep 8 17:48:47 myhost systemd[1]: user@1002.service: Killing process 1086845 (systemd) with signal SIGKILL. Sep 8 17:48:47 myhost systemd[1]: user@1002.service: Killing process 1094006 (systemd) with signal SIGKILL. Sep 8 17:48:47 myhost systemd[1]: user@1002.service: Killing process 1095044 (systemd) with signal SIGKILL. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Processes still around after final SIGKILL. Entering failed mode. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Failed with result 'timeout'. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Unit process 1085783 (systemd) remains running after unit stopped. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Unit process 1086845 (systemd) remains running after unit stopped. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Unit process 1094006 (systemd) remains running after unit stopped. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Unit process 1095044 (systemd) remains running after unit stopped. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Unit process 1102229 (systemd) remains running after unit stopped. Sep 8 17:48:53 myhost systemd[1]: Failed to start User Manager for UID 1002. Sep 8 17:48:53 myhost systemd[1]: Started Session 568 of User proxysync. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Found left-over process 1085783 (systemd) in control group while starting unit. Ignoring. Sep 8 17:48:53 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Found left-over process 1086845 (systemd) in control group while starting unit. Ignoring. Sep 8 17:48:53 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Found left-over process 1094006 (systemd) in control group while starting unit. Ignoring. Sep 8 17:48:53 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Found left-over process 1095044 (systemd) in control group while starting unit. Ignoring. Sep 8 17:48:53 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 8 17:48:53 myhost systemd[1]: user@1002.service: Found left-over process 1102229 (systemd) in control group while starting unit. Ignoring. Sep 8 17:48:53 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 8 17:48:53 myhost systemd[1]: Starting User Manager for UID 1002... Sep 8 17:49:03 myhost pacemaker-controld[989]: notice: High CPU load detected: 7.120000 Sep 8 17:49:33 myhost pacemaker-controld[989]: notice: High CPU load detected: 7.470000 Sep 8 17:49:46 myhost systemd[1]: Starting Message of the Day... Sep 8 17:50:03 myhost pacemaker-controld[989]: notice: High CPU load detected: 7.680000 Sep 8 17:50:23 myhost systemd[1]: user@1002.service: start operation timed out. Terminating. Sep 8 17:50:28 myhost systemd[1]: user@1002.service: State 'stop-sigterm' timed out. Killing. Sep 8 17:50:28 myhost systemd[1]: user@1002.service: Killing process 1103347 (systemd) with signal SIGKILL. Sep 8 17:50:28 myhost systemd[1]: user@1002.service: Killing process 1085783 (systemd) with signal SIGKILL. Sep 8 17:50:28 myhost systemd[1]: user@1002.service: Killing process 1086845 (systemd) with signal SIGKILL. Sep 8 17:50:28 myhost systemd[1]: user@1002.service: Killing process 1094006 (systemd) with signal SIGKILL. Sep 8 17:50:28 myhost systemd[1]: user@1002.service: Killing process 1095044 (systemd) with signal SIGKILL. Sep 8 17:50:28 myhost systemd[1]: user@1002.service: Killing process 1102229 (systemd) with signal SIGKILL. Sep 8 17:50:33 myhost pacemaker-controld[989]: notice: High CPU load detected: 7.810000 Sep 8 17:50:34 myhost systemd[1]: user@1002.service: Processes still around after SIGKILL. Ignoring. Sep 8 17:50:39 myhost systemd[1]: user@1002.service: State 'final-sigterm' timed out. Killing. Sep 8 17:50:39 myhost systemd[1]: user@1002.service: Killing process 1103347 (systemd) with signal SIGKILL. Sep 8 17:50:39 myhost systemd[1]: user@1002.service: Killing process 1085783 (systemd) with signal SIGKILL. Sep 8 17:50:39 myhost systemd[1]: user@1002.service: Killing process 1086845 (systemd) with signal SIGKILL. Sep 8 17:50:39 myhost systemd[1]: user@1002.service: Killing process 1094006 (systemd) with signal SIGKILL. Sep 8 17:50:39 myhost systemd[1]: user@1002.service: Killing process 1095044 (systemd) with signal SIGKILL. Sep 8 17:50:39 myhost systemd[1]: user@1002.service: Killing process 1102229 (systemd) with signal SIGKILL. Sep 8 17:50:44 myhost systemd[1]: user@1002.service: Processes still around after final SIGKILL. Entering failed mode. Sep 8 17:50:44 myhost systemd[1]: user@1002.service: Failed with result 'timeout'. Sep 8 17:50:44 myhost systemd[1]: user@1002.service: Unit process 1085783 (systemd) remains running after unit stopped. Sep 8 17:50:44 myhost systemd[1]: user@1002.service: Unit process 1086845 (systemd) remains running after unit stopped. Sep 8 17:50:44 myhost systemd[1]: user@1002.service: Unit process 1094006 (systemd) remains running after unit stopped. Sep 8 17:50:44 myhost systemd[1]: user@1002.service: Unit process 1095044 (systemd) remains running after unit stopped. Sep 8 17:50:44 myhost systemd[1]: user@1002.service: Unit process 1102229 (systemd) remains running after unit stopped. Sep 8 17:50:44 myhost systemd[1]: user@1002.service: Unit process 1103347 (systemd) remains running after unit stopped. Sep 8 17:50:44 myhost systemd[1]: Failed to start User Manager for UID 1002. Sep 8 17:50:44 myhost systemd[1]: Started Session 570 of User proxysync. Sep 9 01:50:44 myhost systemd[1]: user@1002.service: Unit process 1227716 (systemd) remains running after unit stopped. Sep 9 01:50:44 myhost systemd[1]: user@1002.service: Unit process 1234897 (systemd) remains running after unit stopped. Sep 9 01:50:44 myhost systemd[1]: user@1002.service: Unit process 1236043 (systemd) remains running after unit stopped. Sep 9 01:50:44 myhost systemd[1]: user@1002.service: Unit process 1243283 (systemd) remains running after unit stopped. Sep 9 01:50:44 myhost systemd[1]: user@1002.service: Unit process 1244323 (systemd) remains running after unit stopped. Sep 9 01:50:44 myhost systemd[1]: user@1002.service: Unit process 1251461 (systemd) remains running after unit stopped. Sep 9 01:50:44 myhost systemd[1]: user@1002.service: Unit process 1252502 (systemd) remains running after unit stopped. Sep 9 01:50:44 myhost systemd[1]: user@1002.service: Unit process 1259776 (systemd) remains running after unit stopped. Sep 9 01:50:44 myhost systemd[1]: Failed to start User Manager for UID 1002. Sep 9 01:50:44 myhost systemd[1]: Started Session 738 of User proxysync. Sep 9 01:51:04 myhost pacemaker-controld[989]: notice: High CPU load detected: 73.870003 Sep 9 01:51:34 myhost pacemaker-controld[989]: notice: High CPU load detected: 73.919998 Sep 9 01:52:00 myhost pacemaker-controld[989]: notice: State transition S_IDLE -> S_POLICY_ENGINE Sep 9 01:52:00 myhost pacemaker-schedulerd[988]: notice: On loss of quorum: Ignore Sep 9 01:52:00 myhost pacemaker-schedulerd[988]: notice: Calculated transition 167, saving inputs in /var/lib/pacemaker/pengine/pe-input-159.bz2 Sep 9 01:52:00 myhost pacemaker-controld[989]: notice: Transition 167 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-159.bz2): Complete Sep 9 01:52:00 myhost pacemaker-controld[989]: notice: State transition S_TRANSITION_ENGINE -> S_IDLE Sep 9 01:52:04 myhost pacemaker-controld[989]: notice: High CPU load detected: 73.949997 Sep 9 01:52:34 myhost pacemaker-controld[989]: notice: High CPU load detected: 73.970001 Sep 9 01:53:04 myhost pacemaker-controld[989]: notice: High CPU load detected: 73.980003 Sep 9 01:53:34 myhost pacemaker-controld[989]: notice: High CPU load detected: 73.989998 Sep 9 01:54:04 myhost pacemaker-controld[989]: notice: High CPU load detected: 74.000000 Sep 9 01:56:34 myhost pacemaker-controld[989]: message repeated 5 times: [ notice: High CPU load detected: 74.000000] Sep 9 01:57:01 myhost sssd_pam[1367521]: Shutting down (status = 0) Sep 9 01:57:01 myhost systemd[1]: sssd-pam.service: Deactivated successfully. Sep 9 01:57:04 myhost pacemaker-controld[989]: notice: High CPU load detected: 74.000000 Sep 9 01:57:31 myhost sssd_nss[1366437]: Shutting down (status = 0) Sep 9 01:57:31 myhost systemd[1]: sssd-nss.service: Deactivated successfully. Sep 9 01:57:34 myhost pacemaker-controld[989]: notice: High CPU load detected: 74.000000 Sep 9 01:59:34 myhost pacemaker-controld[989]: message repeated 4 times: [ notice: High CPU load detected: 74.000000] Sep 9 02:00:01 myhost systemd[1]: Started SSSD NSS Service responder. Sep 9 02:00:01 myhost sssd_nss[1374791]: Starting up Sep 9 02:00:01 myhost CRON[1374792]: (root) CMD (/root/scripts/copyproxylisten.sh) Sep 9 02:00:01 myhost /root/scripts/copyproxylisten.sh: Kopiere /etc/haproxy/liste_intern Sep 9 02:00:01 myhost /root/scripts/copyproxylisten.sh: Kopiere /etc/haproxy/liste_internextern Sep 9 02:00:04 myhost pacemaker-controld[989]: notice: High CPU load detected: 74.000000 Sep 9 02:00:34 myhost pacemaker-controld[989]: notice: High CPU load detected: 74.000000 Sep 9 02:01:04 myhost pacemaker-controld[989]: notice: High CPU load detected: 74.080002 Sep 9 02:01:34 myhost pacemaker-controld[989]: notice: High CPU load detected: 74.050003 Sep 9 02:02:01 myhost systemd[1]: Starting SSSD PAM Service responder... Sep 9 02:02:01 myhost systemd[1]: Started SSSD PAM Service responder. Sep 9 02:02:02 myhost sssd_pam[1375874]: Starting up Sep 9 02:02:02 myhost systemd[1]: user@1002.service: Found left-over process 1260824 (systemd) in control group while starting unit. Ignoring. Sep 9 02:02:02 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 9 02:02:02 myhost systemd[1]: user@1002.service: Found left-over process 1267998 (systemd) in control group while starting unit. Ignoring. Sep 9 02:02:02 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 9 02:02:02 myhost systemd[1]: user@1002.service: Found left-over process 1269039 (systemd) in control group while starting unit. Ignoring. Sep 9 02:02:02 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 9 02:02:02 myhost systemd[1]: user@1002.service: Found left-over process 1276378 (systemd) in control group while starting unit. Ignoring. Sep 9 02:02:02 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 9 02:02:02 myhost systemd[1]: user@1002.service: Found left-over process 1277423 (systemd) in control group while starting unit. Ignoring. Sep 9 02:02:02 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 9 02:02:02 myhost systemd[1]: user@1002.service: Found left-over process 1284689 (systemd) in control group while starting unit. Ignoring. Sep 9 02:02:02 myhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 9 02:02:02 myhost systemd[1]: user@1002.service: Found left-over process 1285732 (systemd) in control group while starting unit. Ignoring. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1218362 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1219400 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1226679 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1227716 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1234897 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1236043 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1243283 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1244323 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1251461 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1252502 (systemd) with signal SIGKILL. Sep 9 02:03:47 myhost systemd[1]: user@1002.service: Killing process 1259776 (systemd) with signal SIGKILL. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Processes still around after final SIGKILL. Entering failed mode. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Failed with result 'timeout'. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1260824 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1267998 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1269039 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1276378 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1277423 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1284689 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1285732 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1293012 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1294056 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1301230 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1302362 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1309507 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1310546 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1317879 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1318918 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1326204 (systemd) remains running after unit stopped. Sep 9 02:03:53 myhost systemd[1]: user@1002.service: Unit process 1327242 (systemd) remains running after unit stopped. Do you have any questions or need other logs? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2034701 Title: unexpected system behaviour after kernel update Status in linux package in Ubuntu: Confirmed Bug description: Hello, since last kernel updates on ubuntu 20.04 and 22.04 we see lines like this in syslog after boot: Sep 7 13:10:53 myhost kernel: [ 1.202296] pci 0000:00:15.4: BAR 13: no space for [io size 0x1000] Sep 7 13:10:53 myhost kernel: [ 1.202387] pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000] We see this on Ubuntu 20.04 after installing kernel 5.4.0-162-generic and on ubuntu 22.04 after installing kernel 5.15.0-83-generic Since this time we notice some strange server behaviour. - unexpected reboots during workhours - systems hanging/freezing which requires a hardstop of the machine - systems with high load but no significant number of processes, even on non productive machines with usually zero load. We use most of our ubuntu servers as virtual machines in a VMWare Environment with VSphere and ESXi 7.0.3 There were no VMWare updates. I can say this with certainty because iam the responsible person for VMWare too and i did not install any ESXi Updates last days. Other OS not affected as i can see. Thank you, Hans p.s. i wanted to help and wanted to choose fitting package from dropdown " In what package did you find this bug?" above this Inputfield, but it seems that packages like linux-image-5.15.0-83-generic (or similiar i tried somethging...) are unknown and search respondes with improper suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2034701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
