Bug. XOA crash when adding IO counters in htop
-
Everytime I add IO counters in htop on XOA, it stalls and crashes. It also caused a VM being backuped to reboot.
XOA build: unknown - Current version: 5.43.2 - node: 8.16.2+4 - npm: 4.6.1 - xo-server: 5.56.2 - xo-server-auth-github-enterprise: 0.2.1 - xo-server-auth-google-enterprise: 0.2.1 - xo-server-auth-ldap-enterprise: 0.6.6 - xo-server-auth-saml-enterprise: 0.7.1 - xo-server-backup-reports-enterprise: 0.16.4 - xo-server-telemetry: 0.2.0 - xo-server-transport-email-enterprise: 0.5.0 - xo-server-transport-icinga2-enterprise: 0.1.0 - xo-server-transport-nagios-enterprise: 0.1.0 - xo-server-transport-slack-enterprise: 0.0.0 - xo-server-transport-xmpp-enterprise: 0.1.1 - xo-server-usage-report-enterprise: 0.7.3 - xo-server-xoa: 0.5.0 - xo-web-enterprise: 5.56.2 - xoa-cli: 0.18.2 - xoa-updater: 0.25.0
Linux xoa 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux
Feb 20 09:28:25 xoa kernel: [ 2055.132199] node D 0 2844 556 0x00000002 Feb 20 09:28:25 xoa kernel: [ 2055.132203] ffff95c378b02100 0000000000000000 ffff95c374a7d000 ffff95c379ed8980 Feb 20 09:28:25 xoa kernel: [ 2055.132205] ffff95c373968000 ffffb28a03acfa30 ffffffffb1214219 ffff95c2c593a118 Feb 20 09:28:25 xoa kernel: [ 2055.132207] 00ffffffc05c66da ffff95c379ed8980 ffff95c373c34400 ffff95c374a7d000 Feb 20 09:28:25 xoa kernel: [ 2055.132210] Call Trace: Feb 20 09:28:25 xoa kernel: [ 2055.132217] [<ffffffffb1214219>] ? __schedule+0x239/0x6f0 Feb 20 09:28:25 xoa kernel: [ 2055.132219] [<ffffffffb1214ec0>] ? bit_wait+0x50/0x50 Feb 20 09:28:25 xoa kernel: [ 2055.132221] [<ffffffffb1214702>] ? schedule+0x32/0x80 Feb 20 09:28:25 xoa kernel: [ 2055.132223] [<ffffffffb1217a8d>] ? schedule_timeout+0x1dd/0x380 Feb 20 09:28:25 xoa kernel: [ 2055.132225] [<ffffffffb0c1be01>] ? xen_clocksource_get_cycles+0x11/0x20 Feb 20 09:28:25 xoa kernel: [ 2055.132227] [<ffffffffb1214ec0>] ? bit_wait+0x50/0x50 Feb 20 09:28:25 xoa kernel: [ 2055.132229] [<ffffffffb1213f7d>] ? io_schedule_timeout+0x9d/0x100 Feb 20 09:28:25 xoa kernel: [ 2055.132231] [<ffffffffb0cbce47>] ? prepare_to_wait+0x57/0x80 Feb 20 09:28:25 xoa kernel: [ 2055.132233] [<ffffffffb1214ed7>] ? bit_wait_io+0x17/0x60 Feb 20 09:28:25 xoa kernel: [ 2055.132235] [<ffffffffb1214a95>] ? __wait_on_bit+0x55/0x80 Feb 20 09:28:25 xoa kernel: [ 2055.132238] [<ffffffffb0d82598>] ? find_get_pages_tag+0x158/0x2e0 Feb 20 09:28:25 xoa kernel: [ 2055.132240] [<ffffffffb0d817ff>] ? wait_on_page_bit+0x7f/0xa0 Feb 20 09:28:25 xoa kernel: [ 2055.132242] [<ffffffffb0cbd2b0>] ? wake_atomic_t_function+0x60/0x60 Feb 20 09:28:25 xoa kernel: [ 2055.132244] [<ffffffffb0d81900>] ? __filemap_fdatawait_range+0xe0/0x140 Feb 20 09:28:25 xoa kernel: [ 2055.132246] [<ffffffffb0d8196f>] ? filemap_fdatawait_range+0xf/0x30 Feb 20 09:28:25 xoa kernel: [ 2055.132248] [<ffffffffb0d843b9>] ? filemap_write_and_wait_range+0x49/0x70 Feb 20 09:28:25 xoa kernel: [ 2055.132264] [<ffffffffc08602b2>] ? nfs_file_fsync+0x32/0x1e0 [nfs] Feb 20 09:28:25 xoa kernel: [ 2055.132267] [<ffffffffb0e07a1d>] ? filp_close+0x2d/0x70 Feb 20 09:28:25 xoa kernel: [ 2055.132270] [<ffffffffb0e2ac35>] ? do_close_on_exec+0xc5/0x110 Feb 20 09:28:25 xoa kernel: [ 2055.132272] [<ffffffffb0e1259b>] ? flush_old_exec+0x5db/0x6b0 Feb 20 09:28:25 xoa kernel: [ 2055.132275] [<ffffffffb0e67be2>] ? load_elf_binary+0x3c2/0x1640 Feb 20 09:28:25 xoa kernel: [ 2055.132277] [<ffffffffb0e06f7a>] ? __check_object_size+0xfa/0x1d8 Feb 20 09:28:25 xoa kernel: [ 2055.132278] [<ffffffffb0e11c85>] ? copy_strings.isra.25+0x185/0x480 Feb 20 09:28:25 xoa kernel: [ 2055.132280] [<ffffffffb0e11766>] ? search_binary_handler+0xa6/0x1c0 Feb 20 09:28:25 xoa kernel: [ 2055.132282] [<ffffffffb0e12eaa>] ? do_execveat_common.isra.37+0x5aa/0x790 Feb 20 09:28:25 xoa kernel: [ 2055.132284] [<ffffffffb0e132b5>] ? SyS_execve+0x35/0x40 Feb 20 09:28:25 xoa kernel: [ 2055.132286] [<ffffffffb0c03b7d>] ? do_syscall_64+0x8d/0xf0 Feb 20 09:28:25 xoa kernel: [ 2055.132288] [<ffffffffb1218f8e>] ? entry_SYSCALL_64_after_swapgs+0x58/0xc6
What's more, the backups are listed as ongoing after a force-reboot of xoa, though I do not think they are actually running as there is no network or disk I/O.
-
A toolstack restart cleared the ongoing-but-failed tasks.